I have a small "expect" script to login in to the modem and reboot the
unit @ 08:00 and 00:00 hours. This was working fine up until a few
weeks ago. Now, after a reboot (thru the expect script) the unit is
unable to login to the MTNL network. The following log shows PPPoE
login failure:
<log-failure>
Jan 1 12:00:25> Connecting PPPoE socket: 00:90:1a:41:78:b6 6b0b nas0
0x1000d378
Jan 1 12:00:25> Connect: ppp0 {--} nas0
Jan 1 12:00:25> PAP authentication failed
Jan 1 12:00:25> Connection terminated.
Jan 1 12:00:25> Doing disconnect
Jan 1 12:00:29> pppd 2.4.1 started by root, uid 0
Jan 1 12:00:29> Unexpected packet: Ether addr: 00:90:1a:41:78:b6
(PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x07 sid=0x0000
length=0x002d (PADO) PPPoE tag: type=0102 length=0009 (AC Name) data
(UTF-8): BRAS-PRBD PPPoE tag: type=0103 length=000
Jan 1 12:00:29> Got connection: f10d
Jan 1 12:00:29> Saved Session ID: 0
Jan 1 12:00:29> Connecting PPPoE socket: 00:90:1a:41:77:c7 f10d nas0
0x1000d378
Jan 1 12:00:29> Connect: ppp0 {--} nas0
Jan 1 12:00:29> PAP authentication failed
Jan 1 12:00:29> Connection terminated.
Jan 1 12:00:29> Doing disconnect
... above repetition snipped ...
</log-failure>
However, if I **power cycle** the modem, most times it is able to login
(PPPoE) successfully in to the MTNL network. The log for a successful
login starts off a little differently (the first line of the log).
<log-success>
Jan 1 12:00:12> Valid Configuration Tree
Jan 1 12:00:12> DSL Polling Timer Started succesfully.
Jan 1 12:00:12> Firewall NAT service started
Jan 1 12:00:16> starting on port 80
Jan 1 12:00:16> Bridge Created: br0
Jan 1 12:00:16> No Module Description from Interface Below
Jan 1 12:00:17> Bridge Interface Added: eth0
Jan 1 12:00:18> Bridge Interface Added: usb0
Jan 1 12:00:18> Bridge Interface Added: nas1
Jan 1 12:00:18> Add Bridge Iface Error: 1
Jan 1 12:00:18> Duplicate Bridge Iface: nas1
Jan 1 12:00:22> DSL Carrier is up
Jan 1 12:00:23> pppd 2.4.1 started by root, uid 0
Jan 1 12:00:23> Unexpected packet: Ether addr: 00:90:1a:41:78:b6
(PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x07 sid=0x0000
length=0x002d (PADO) PPPoE tag: type=0102 length=0009 (AC Name) data
(UTF-8): BRAS-PRBD PPPoE tag: type=0103 length=000
Jan 1 12:00:23> Got connection: fb09
Jan 1 12:00:23> Saved Session ID: 0
Jan 1 12:00:23> Connecting PPPoE socket: 00:90:1a:41:77:c7 fb09 nas0
0x1000d378
Jan 1 12:00:23> Connect: ppp0 {--} nas0
Jan 1 12:00:24> WAN IP address 59.183.23.230
Jan 1 12:00:24> PPPoE Connect with IP Address 59.183.23.230
Jan 1 12:00:24> PPPoE Connection Successfully Established
Jan 1 12:00:24> PPPoE Connect with Gateway IP Address: 59.183.63.254
Jan 1 12:00:24> WAN gateway 59.183.63.254
Jan 1 12:00:24> primary DNS address 203.94.227.70
Jan 1 12:00:24> secondary DNS address 203.94.243.70
</log-success>
Occasionally, even power cycle does not work. I keep getting PPPoE
login failure. In such case, I have had to open a trouble ticket and
typically within 12-18 hours the unit is able to login successfully.
Not sure if MTNL really did something or the problem auto corrected
itself :(
In both scenarios, the web interface "Status>ADSL" does display the
"Line State" as connected.
I first reset the unit to factory settings and reprogrammed my custom
settings. That did not help. Then I reflashed the firmware on the unit
and reprogrammed my custom settings - no help. I am wondering if I
have a flaky modem and how to prove it.
Talking to MTNL is of no help. According to them, if all the LEDs are
on then my modem is good.
Any pointers as to what could be wrong would be highly appreciated.
TIA,
--
Arun Khan
Linux is like a wigwam - no gates, no windows, apache inside