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 K. Khan wrote:
<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.
This had happened to me when I changed the passwd on the site and did not update it in the modem. I got the same log as above. However, since you are able to login under power reset, could you check if you are properly logging out, before you re-login using the script? I could be wrong about this but just cross check.
Regards,
Rony.
___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
On Fri, 2006-01-20 at 20:57 +0530, Rony Bill wrote:
This had happened to me when I changed the passwd on the site and did not update it in the modem. I got the same log as above. However, since
Userid/passwd on modem and MTNL's site are the same.
you are able to login under power reset, could you check if you are properly logging out, before you re-login using the script? I could be wrong about this but just cross check.
When the script reboots the modem, the telnet session is terminated.
Looked at some of the postings at "broadbandforum.in" under MTNL TriBand and saw a few postings of similar nature but no clue as to why the problem is occurring.
Thanks for helpful suggestion.
Arun K. Khan wrote:
When the script reboots the modem, the telnet session is terminated.
Which telnet session? Just a few times though, when I tinkered with my modem settings and rebooted it using the modem's web interface, it would not open any sites. I did not bother to check the logs, but a power reboot set everything right. So this may be a problem with the modem or its embedded software, if you have not made any changes in your own script.
Regards,
Rony.
___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com
On Sat, 2006-01-21 at 17:58 +0530, Rony Bill wrote:
Which telnet session? Just a few times though, when I tinkered with my modem settings and rebooted it using the modem's web interface, it would
You can telnet <modem ip address> into the modem using admin/password. At the shell prompt the "reboot" command does the same thing as the Web "Tools>System>Save and Reboot" interface. The telnet session can be automated via a script using "expect" language.
Arun K. Khan wrote:
You can telnet <modem ip address> into the modem using admin/password. At the shell prompt the "reboot" command does the same thing as the Web "Tools>System>Save and Reboot" interface. The telnet session can be automated via a script using "expect" language.
In both cases the problem is that the modem is not rebooting properly to re-login correctly. Is there any way we can find out how the modem tells the mtnl server that its alive? That could give some clue on how to break 'that' session and re-login.
Regards,
Rony.
___________________________________________________________ Yahoo! Photos NEW, now offering a quality print service from just 8p a photo http://uk.photos.yahoo.com
On Sun, 2006-01-22 at 14:36 +0530, Rony Bill wrote:
In both cases the problem is that the modem is not rebooting properly to re-login correctly. Is there any way we can find out how the modem tells the mtnl server that its alive? That could give some clue on how to break 'that' session and re-login.
I'll take a leap of faith and believe that the ADSL "physical layer" is OK if the modem reports it is connected. IMO, the problem is in the link layer of the stack - either the userid/passwd is getting mangled or the authentication server @ MTNL is hiccuping. Need a MTNL engineer to capture the frames and determine what the problem is.
On Friday 20 January 2006 18:39, Arun K. Khan wrote:
On Fri, 2006-01-20 at 20:57 +0530, Rony Bill wrote:
This had happened to me when I changed the passwd on the site and did not update it in the modem. I got the same log as above. However, since
Userid/passwd on modem and MTNL's site are the same.
you are able to login under power reset, could you check if you are properly logging out, before you re-login using the script? I could be wrong about this but just cross check.
When the script reboots the modem, the telnet session is terminated.
Looked at some of the postings at "broadbandforum.in" under MTNL TriBand and saw a few postings of similar nature but no clue as to why the problem is occurring.
May be the expect script isn't at fault. Due to some mysterious problem most poeple are unable to login for the first two or three tries... May be thats the problem??
On Sat, 2006-01-21 at 16:17 +0000, Dinesh Joshi wrote:
May be the expect script isn't at fault. Due to some mysterious problem most poeple are unable to login for the first two or three tries... May be thats the problem??
The script worked fine till mid Dec/05. I have not made any changes to it after posting it on this list.
From the postings @ broadbandforum.in it is unlikely so many DLink
modems could be flaky. Seems like the problem is @ the MTNL end. It is interesting however that a soft reboot ends up in a login failure whereas a hard reboot succeeds (most times) - maybe it is just a coincidence.
On Saturday 21 January 2006 5:59 pm, Arun K. Khan wrote:
On Sat, 2006-01-21 at 16:17 +0000, Dinesh Joshi wrote:
May be the expect script isn't at fault. Due to some mysterious problem most poeple are unable to login for the first two or three tries... May be thats the problem??
The script worked fine till mid Dec/05. I have not made any changes to it after posting it on this list.
From the postings @ broadbandforum.in it is unlikely so many DLink
modems could be flaky. Seems like the problem is @ the MTNL end. It is interesting however that a soft reboot ends up in a login failure whereas a hard reboot succeeds (most times) - maybe it is just a coincidence.
Does hardboot (with the black reset button) restore factory defaults?
There was a problem at one clients place on friday. The mtnl guys came and did a hard reset (not sure if they restored factory settings) to get the connection up again. I had to reload my saved config.
Also has any one used BSNL. The modem is a Huwaei MT882 (Axistech). It simply refuses to work with a gnu browser (lynx, mozilla, firefox, konqueror) but ieexploder renders pages dished out by the modem. I ofcourse refuses to login with pppoe, bombing out with recieved "PADR" and connection reset by peer. The BSNL guys know nothing about the authentication or ethernet connection. They had it working on a xp box with usb. Will have to wait until monday to know what exactly they are upto.
On Sun, 2006-01-22 at 10:30 +0530, JTD wrote:
Does hardboot (with the black reset button) restore factory defaults?
Yes, it resets to factory defaults. Need to program userid/passwd and any other settings.
There was a problem at one clients place on friday. The mtnl guys came and did a hard reset (not sure if they restored factory settings) to get the connection up again. I had to reload my saved config.
You can save your custom settings in a file and apply them back.
Also has any one used BSNL. The modem is a Huwaei MT882 (Axistech). It simply refuses to work with a gnu browser (lynx, mozilla, firefox, konqueror) but ieexploder renders pages dished out by the modem.
I experienced the same with firmware v1.0 in the Dlink 502t. Ironic, since the unit uses embedded Linux. It is even more ironic that they will not accept any feedback and insist "Sir, but it works with IE!" Wonder where these companies pick up these developers who manage to screw up browser interoperability - for an interface that is quite simple.
-
Arun K. Khan -
Dinesh Joshi -
JTD -
Rony Bill