Internet stopped working after I tried to change MTU...

  • Thread starter Thread starter pr0m3th3u5
  • Start date Start date
  • Replies Replies 2
  • Views Views 1,031
Messages
70
Location
NA
ISP
BSNL
I had issues with NETFLIX and I read in this forum that lowering the MTU to 1462 might make it work better. So on my Alphion Modem I change the MTU on WAN/PON WAN/pp0 page and restarted but then the internet just stopped working... Even when I restored the modem configuration from when it's working the internet right now is still not working...

PON Status

Vendor NameALPHION
Temperature49.507812 C
Voltage3.260400 V
Tx Power2.384988 dBm
Rx Power-22.076083 dBm
Bias Current22.500000 mA



Logs:
Date/Time​
Facility​
Level​
Message​
Jan 1 00:00:13daemonnoticesystemd: wlan0-vap1 down
Jan 1 00:00:13daemonnoticesystemd: wlan0-vap2 down
Jan 1 00:00:13daemonnoticesystemd: wlan0-vap3 down
Jan 1 00:00:13daemonnoticesystemd: wlan1 down
Jan 1 00:00:13daemonnoticesystemd: wlan1-vap0 down
Jan 1 00:00:13daemonnoticesystemd: wlan1-vap1 down
Jan 1 00:00:13daemonnoticesystemd: wlan1-vap2 down
Jan 1 00:00:13daemonnoticesystemd: wlan1-vap3 down
Jan 1 00:00:13daemonnoticesystemd: eth0 up
Jan 1 00:00:13daemonnoticesystemd: eth0.2 down
Jan 1 00:00:13daemonnoticesystemd: eth0.2.0 down
Jan 1 00:00:13daemonnoticesystemd: eth0.2 down
Jan 1 00:00:13daemonnoticesystemd: eth0.2 down
Jan 1 00:00:13daemonnoticesystemd: eth0.3 down
Jan 1 00:00:13daemonnoticesystemd: eth0.3.0 down
Jan 1 00:00:13daemonnoticesystemd: eth0.3 down
Jan 1 00:00:13daemonnoticesystemd: eth0.3 down
Jan 1 00:00:13daemonnoticesystemd: br0 down
Jan 1 00:00:13daemonnoticesystemd: br0 down
Jan 1 00:00:13daemonnoticesystemd: eth0.2.0 down
Jan 1 00:00:13daemonnoticesystemd: eth0.2.0 down
Jan 1 00:00:13daemonnoticesystemd: eth0.2.0 down
Jan 1 00:00:13daemonnoticesystemd: br0 down
Jan 1 00:00:13daemonnoticesystemd: eth0.2 down
Jan 1 00:00:13daemonnoticesystemd: eth0.2.0 down
Jan 1 00:00:13daemonnoticesystemd: eth0.2 down
Jan 1 00:00:13daemonnoticesystemd: eth0.3.0 down
Jan 1 00:00:13daemonnoticesystemd: eth0.3.0 down
Jan 1 00:00:14daemonnoticesystemd: eth0.3.0 down
Jan 1 00:00:14daemonnoticesystemd: eth0.3 down
Jan 1 00:00:14daemonnoticesystemd: eth0.3.0 down
Jan 1 00:00:14daemonnoticesystemd: eth0.3 down
Jan 1 05:30:14usernoticeboa[573]: Enabling SSL security system
Jan 1 05:30:15usernoticeboa[573]: SSL security system enabled
Jan 1 00:00:15daemonnoticesystemd: br0 up
Jan 1 00:00:15daemonnoticesystemd: ppp0 down
Jan 1 00:00:15daemonnoticesystemd: ppp1 down
Jan 1 00:00:15daemonnoticesystemd: ppp2 down
Jan 1 00:00:15daemonnoticesystemd: ppp3 down
Jan 1 00:00:15daemonnoticesystemd: ppp4 down
Jan 1 00:00:15daemonnoticesystemd: ppp5 down
Jan 1 00:00:15daemonnoticesystemd: ppp6 down
Jan 1 00:00:15daemonnoticesystemd: ppp7 down
Jan 1 00:00:15daemonnoticesystemd: eth0.3.0 down
Jan 1 00:00:15daemonnoticesystemd: br0 down
Jan 1 00:00:16daemonnoticesystemd: Ethernet WAN(nas0) down
Jan 1 00:00:16daemonnoticesystemd: Ethernet WAN(nas0) down
Jan 1 00:00:17daemonnoticesystemd: Ethernet WAN(nas0) down
Jan 1 00:00:17daemonnoticesystemd: Ethernet WAN(nas0) down
Jan 1 00:00:17daemonnoticesystemd: Ethernet WAN(nas0) down
Jan 1 00:00:17daemonnoticesystemd: Ethernet WAN(nas0) down
Jan 1 05:30:17daemonnoticeminiupnpd[1011]: HTTP listening on port 49152
Jan 1 00:00:18daemonnoticesystemd: wlan0 down
Jan 1 00:00:18daemonnoticesystemd: wlan0 down
Jan 1 00:00:18daemonnoticesystemd: wlan0 down
Jan 1 00:00:19daemonnoticesystemd: wlan0 up
Jan 1 00:00:20daemonnoticesystemd: br0 up
Jan 1 00:00:21daemonnoticesystemd: wlan1 down
Jan 1 00:00:21daemonnoticesystemd: wlan1 down
Jan 1 00:00:21daemonnoticesystemd: wlan1 down
Jan 1 00:00:22daemonnoticesystemd: wlan1 up
Jan 1 05:30:28usererrudhcpd: unable to parse 'opt ntpsrv pool.ntp.org'
Jan 1 05:30:28usererrudhcpd: unable to parse 'opt tzstring '
Jan 1 05:30:30daemonnoticeminiupnpd[1816]: HTTP listening on port 49152
Jan 1 05:30:31daemonerrdhcpd:
Jan 1 05:30:31daemonerrdhcpd: No subnet6 declaration for br0 (fe80::9267:17ff:fe48:44d7).
Jan 1 05:30:31daemonerrdhcpd: ** Ignoring requests on br0. If this is not what
Jan 1 05:30:31daemonerrdhcpd: you want, please write a subnet6 declaration
Jan 1 05:30:31daemonerrdhcpd: in your dhcpd.conf file for the network segment
Jan 1 05:30:31daemonerrdhcpd: to which interface br0 is attached. **
Jan 1 05:30:31daemonerrdhcpd:
Jan 1 05:30:31daemonerrdhcpd: Not configured to listen on any interfaces!
Jan 1 05:30:31daemonerrdhcpd:
Jan 1 05:30:31daemonerrdhcpd: If you think you have received this message due to a bug rather
Jan 1 05:30:31daemonerrdhcpd: than a configuration issue please read the section on submitting
Jan 1 05:30:31daemonerrdhcpd: bugs on either our web page at www.isc.org or in the README file
Jan 1 05:30:31daemonerrdhcpd: before submitting a bug. These pages explain the proper
Jan 1 05:30:31daemonerrdhcpd: process and the information we find helpful for debugging.
Jan 1 05:30:31daemonerrdhcpd:
Jan 1 05:30:31daemonerrdhcpd: exiting.
Jan 1 00:00:32daemonnoticesystemd: Ethernet WAN(nas0) up
Jan 1 00:00:33daemonnoticesystemd: eth0.2 up
Jan 1 00:00:33daemonnoticesystemd: eth0.2.0 up

Did the internet stop working because of a bad setting in my Alphion Modem? Or is it an issue with the BSNL?
 
is your internet working now ?
 

Back