1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Nothing but disconnects w WRT54GL and 1.19

Discussion in 'Tomato Firmware' started by pcguy, Apr 24, 2008.

  1. pcguy

    pcguy LI Guru Member

    I purchased a LinkSys WRT54GL and flashed it with Tomato 1.19 and have had nothing but problems with disconnects. Using PPoE for my DSL connection here and have Keep Alive set for 30 seconds. Have noticed the following in the logfile when the disconnect occurs:


    Code:
    Dec 31 18:00:08 unknown daemon.info dnsmasq[112]: read /etc/hosts - 0 addresses
    Dec 31 18:00:08 unknown daemon.info dnsmasq[112]: read /etc/hosts.dnsmasq - 1 addresses
    Apr 24 12:03:14 unknown cron.warn crond[94]: time disparity of 20150943 minutes detected 
    Apr 24 13:02:18 unknown syslog.info -- MARK --
    Apr 24 14:02:19 unknown syslog.info -- MARK --
    Apr 24 14:45:45 unknown daemon.info pppoe[83]: Received LCP Termination-Request
    Apr 24 14:45:45 unknown daemon.info pppoe[83]: Sending LCP Termination-Ack
    Apr 24 14:45:48 unknown daemon.info pppoe[83]: Connection terminated.
    Apr 24 14:45:48 unknown daemon.info pppoe[83]: Connect time 163.5 minutes.
    Apr 24 14:45:48 unknown daemon.info pppoe[83]: Sent 8609822 bytes, received 65626478 bytes.
    Apr 24 14:45:48 unknown daemon.info pppoe[83]: Sending PADT.
    Apr 24 14:45:58 unknown daemon.info pppoe[83]: Sending PADI.
    Apr 24 14:45:58 unknown daemon.info pppoe[83]: Received PADT for 0x2DBF, expecting 0x0000
    Apr 24 14:45:58 unknown daemon.info pppoe[83]: Received PADT for 0xFDF7, expecting 0x0000
    Apr 24 14:46:02 unknown user.info redial[75]: PPPoE reconnect in progress (4)
    Apr 24 14:46:08 unknown daemon.info pppoe[83]: Resending...
    Apr 24 14:46:13 unknown daemon.info pppoe[83]: Resending...
    Apr 24 14:46:19 unknown daemon.info pppoe[83]: Resending...
    Apr 24 14:46:26 unknown daemon.info pppoe[83]: Resending...
    Apr 24 14:46:32 unknown user.info redial[75]: WAN down. Reconnecting...
    Apr 24 14:46:32 unknown daemon.info dnsmasq[112]: exiting on receipt of SIGTERM
    Apr 24 14:46:34 unknown daemon.info dnsmasq[3334]: started, version 2.41 cachesize 150
    Apr 24 14:46:34 unknown daemon.info dnsmasq[3334]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
    Apr 24 14:46:34 unknown daemon.info dnsmasq[3334]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
    Apr 24 14:46:34 unknown daemon.warn dnsmasq[3334]: no servers found in /etc/resolv.dnsmasq, will retry
    Apr 24 14:46:34 unknown daemon.info dnsmasq[3334]: read /etc/hosts - 0 addresses
    Apr 24 14:46:34 unknown daemon.info dnsmasq[3334]: read /etc/hosts.dnsmasq - 1 addresses
    Apr 24 14:46:34 unknown daemon.info pppoe[3335]: Starting
    Apr 24 14:46:34 unknown daemon.info pppoe[3335]: Sending PADI.
    Apr 24 14:46:34 unknown user.info redial[3332]: Started. Time: 30
    Apr 24 14:46:44 unknown daemon.info pppoe[3335]: Resending...
    Apr 24 14:46:54 unknown daemon.info pppoe[3335]: Resending...
    Apr 24 14:46:58 unknown daemon.info pppoe[3335]: Resending...
    Apr 24 14:47:06 unknown daemon.info pppoe[3335]: Resending...
    Apr 24 14:47:14 unknown daemon.info pppoe[3335]: Sending PADI.
    Apr 24 14:47:14 unknown user.info redial[3332]: WAN down. Reconnecting...
    Apr 24 14:47:15 unknown daemon.info dnsmasq[3334]: exiting on receipt of SIGTERM
    Apr 24 14:47:15 unknown daemon.info dnsmasq[3366]: started, version 2.41 cachesize 150
    Apr 24 14:47:15 unknown daemon.info dnsmasq[3366]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
    Apr 24 14:47:15 unknown daemon.info dnsmasq[3366]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
    Apr 24 14:47:15 unknown daemon.warn dnsmasq[3366]: no servers found in /etc/resolv.dnsmasq, will retry
    Apr 24 14:47:15 unknown daemon.info dnsmasq[3366]: read /etc/hosts - 0 addresses
    Apr 24 14:47:15 unknown daemon.info dnsmasq[3366]: read /etc/hosts.dnsmasq - 1 addresses
    Apr 24 14:47:21 unknown daemon.info pppoe[3373]: Starting
    Apr 24 14:47:21 unknown daemon.info pppoe[3373]: Sending PADI.
    Apr 24 14:47:21 unknown user.info redial[3372]: Started. Time: 30
    Apr 24 14:47:31 unknown daemon.info pppoe[3373]: Resending...
    Apr 24 14:47:41 unknown daemon.info pppoe[3373]: Resending...
    Apr 24 14:47:46 unknown daemon.info pppoe[3373]: Resending...
    Apr 24 14:47:54 unknown daemon.info pppoe[3373]: Resending...
    Apr 24 14:48:01 unknown user.info redial[3372]: WAN down. Reconnecting...
    Apr 24 14:48:01 unknown daemon.info dnsmasq[3366]: exiting on receipt of SIGTERM
    Apr 24 14:48:01 unknown daemon.info dnsmasq[3404]: started, version 2.41 cachesize 150
    Apr 24 14:48:01 unknown daemon.info dnsmasq[3404]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
    Apr 24 14:48:01 unknown daemon.info dnsmasq[3404]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
    Apr 24 14:48:01 unknown daemon.warn dnsmasq[3404]: no servers found in /etc/resolv.dnsmasq, will retry
    Apr 24 14:48:01 unknown daemon.info dnsmasq[3404]: read /etc/hosts - 0 addresses
    Apr 24 14:48:01 unknown daemon.info dnsmasq[3404]: read /etc/hosts.dnsmasq - 1 addresses
    Apr 24 14:48:07 unknown user.info redial[3410]: Started. Time: 30
    Apr 24 14:48:07 unknown daemon.info pppoe[3411]: Starting
    Apr 24 14:48:07 unknown daemon.info pppoe[3411]: Sending PADI.
    Apr 24 14:48:17 unknown daemon.info pppoe[3411]: Resending...
    Apr 24 14:48:27 unknown daemon.info pppoe[3411]: Resending...
    Apr 24 14:48:31 unknown daemon.info pppoe[3411]: Resending...
    Apr 24 14:48:39 unknown daemon.info pppoe[3411]: Resending...
    Apr 24 14:48:47 unknown daemon.info pppoe[3411]: Sending PADI.
    Apr 24 14:48:47 unknown user.info redial[3410]: WAN down. Reconnecting...
    Apr 24 14:48:47 unknown daemon.info dnsmasq[3404]: exiting on receipt of SIGTERM
    Apr 24 14:48:47 unknown daemon.info dnsmasq[3444]: started, version 2.41 cachesize 150
    Apr 24 14:48:47 unknown daemon.info dnsmasq[3444]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
    Apr 24 14:48:47 unknown daemon.info dnsmasq[3444]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
    Apr 24 14:48:47 unknown daemon.warn dnsmasq[3444]: no servers found in /etc/resolv.dnsmasq, will retry
    Apr 24 14:48:47 unknown daemon.info dnsmasq[3444]: read /etc/hosts - 0 addresses
    Apr 24 14:48:47 unknown daemon.info dnsmasq[3444]: read /etc/hosts.dnsmasq - 1 addresses
    Apr 24 14:48:54 unknown daemon.info pppoe[3449]: Starting
    Apr 24 14:48:54 unknown daemon.info pppoe[3449]: Sending PADI.
    Apr 24 14:48:54 unknown user.info redial[3447]: Started. Time: 30
    Apr 24 14:48:59 unknown user.warn kernel: nvram_commit(): init
    Apr 24 14:49:00 unknown user.warn kernel: nvram_commit(): end
    Apr 24 14:49:03 unknown syslog.info System log daemon exiting.
    Apr 24 14:49:11 unknown syslog.info syslogd started: BusyBox v1.2.2
    Apr 24 14:49:11 unknown user.notice kernel: klogd started: BusyBox v1.2.2 (2008.04.20-18:57+0000)
    Apr 24 14:49:11 unknown user.info kernel: br0: port 2(eth1) entering disabled state
    Apr 24 14:49:11 unknown user.info kernel: br0: port 1(vlan0) entering disabled state
    Apr 24 14:49:11 unknown user.info kernel: br0: port 1(vlan0) entering disabled state
    Apr 24 14:49:11 unknown user.info kernel: device vlan0 left promiscuous mode
    Apr 24 14:49:11 unknown user.info kernel: br0: port 2(eth1) entering disabled state
    Apr 24 14:49:11 unknown user.info kernel: device eth1 left promiscuous mode
    Apr 24 14:49:11 unknown user.info kernel: device eth1 entered promiscuous mode
    Apr 24 14:49:11 unknown user.info kernel: br0: port 2(eth1) entering learning state
    Apr 24 14:49:11 unknown user.info kernel: br0: port 1(vlan0) entering learning state
    Apr 24 14:49:11 unknown user.info kernel: br0: port 2(eth1) entering forwarding state
    Apr 24 14:49:11 unknown daemon.info dnsmasq[3558]: started, version 2.41 cachesize 150
    Apr 24 14:49:11 unknown daemon.warn dnsmasq[3558]: overflow: 7 log entries lost
    Apr 24 14:49:11 unknown user.info kernel: br0: topology change detected, propagating
    Apr 24 14:49:12 unknown user.warn kernel: vlan1: Setting MAC address to  00 1e e5 44 0d 82<6>br0: port 1(vlan0) entering forwarding state
    Apr 24 14:49:12 unknown user.info kernel: br0: topology change detected, propagating
    Apr 24 14:49:12 unknown user.warn kernel: .
    Apr 24 14:49:12 unknown daemon.info dnsmasq[3586]: started, version 2.41 cachesize 150
    Apr 24 14:49:12 unknown daemon.info dnsmasq[3586]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
    Apr 24 14:49:12 unknown daemon.info dnsmasq[3586]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
    Apr 24 14:49:12 unknown daemon.info dnsmasq[3586]: reading /etc/resolv.dnsmasq
    Apr 24 14:49:12 unknown daemon.info dnsmasq[3586]: using nameserver 1.1.1.1#53
    Apr 24 14:49:12 unknown daemon.info dnsmasq[3586]: read /etc/hosts - 0 addresses
    Apr 24 14:49:12 unknown daemon.info dnsmasq[3586]: read /etc/hosts.dnsmasq - 1 addresses
    Apr 24 14:49:12 unknown user.info init[1]: Linksys WRT54G/GS/GL
    Apr 24 14:49:12 unknown cron.notice crond[3595]: crond 2.3.2 dillon, started, log level 9 
    Apr 24 14:49:18 unknown user.warn kernel: nvram_commit(): init
    Have tried a Dlink 1310 and it has no problem whatsoever keeping the connection for 26+ hours. I am lucky if the LinkSys keeps the connection for 3 hours or so. I notice that the LinkSys seems to be unable to connect on its own when the disconnect happens as there is no indication of being authenticated with the ISP (MTS ). I wind up having to click on the CONNECT button in the Web GUI.
     
  2. Toxic

    Toxic Administrator Staff Member

    have you reset the router since upgrading?
     
  3. pcguy

    pcguy LI Guru Member

    Well I installed the Tomato firmware and then cleared the VRAM before inputting my settings but that is all. Other than removing the LinkSys and using the DLink so that I could get a connection that stays up.
     
  4. pcguy

    pcguy LI Guru Member

    I have had to revert back to using the DLink router for now. This LinkSys is far to unstable as it stands. It disconnects and wont reconnect even if I click on the reconnect. Of course to determine whether the box is defective I have to revert back to the original LinkSys firmware.
     
  5. szfong

    szfong Network Guru Member

    Is there a reason why you couldn't let the dsl modem handle the pppoe connection?
     
  6. pcguy

    pcguy LI Guru Member

    Because here the modem does not do that. MTS (ISP) here uses software in XP (PPoE) to initiate the connection or in the case of the router it to initiate the connection. The modem in my case is part of a IP TV box from MTS that I have.
     
  7. szfong

    szfong Network Guru Member

    A great deal of what's under the hood comes from gpl source code from Linksys stock firmware. Were you able to re-produce this issue with the latest WRT54GL firmware from linksys? re-flashing back to linksys firmware and see if it's working. You may also try thibor15c and the firmware with two D's in its description.
     
  8. pcguy

    pcguy LI Guru Member

    Blood pressure and frustration rose

    Well after using LinkSys support Chat twice (totally useless) and talking to 3 other techs on the phone I find out that the Canadian LinkSys web site is screwed up. I does not show the current 4.30.12 for the WRT54GL but rather the .11 release. I have flashed the router with this firmware and it has been running for 15 hours so far. I will not know if this fixed the problem or not since the lenght between the disconnects were varied.

    It was very frustrating dealing with their support, especially after the first tech said that they would RMA it if his suggestions did not work only to discover that he made no mention of the RMA in the notes for the trouble ticket. I had to talk to 2 other techs and eventually got them to admit that if the flashing to 4.30.12 did not work then the unit will be RMA'd. I would prefer to do that since the whole point in buying this router was to install Tomato on it. However Tomato as my past experience indicated will not run on this particular WRT54GL.
     
  9. LLigetfa

    LLigetfa LI Guru Member

    Your log indicates your ISP is terminating the session. This does not usually point to your router as the problem. The fact the DLink works though is puzzling. Perhaps the DLink does a better job at keepalive. See the following thread:
    http://www.linksysinfo.org/forums/showthread.php?t=57273

    Have you tried replacing the CAT5 jumper between the router and the modem? If it has a bad crimp, it could work better plugged into the DLink than the Linksys.

    Just because it works well on one doesn't rule it out as a problem. I've seen it before, had to replace dozens of jumpers when we rolled out new computers because of differences in tolerance on the NIC jacks.

    The other possibility is a ground loop problem. Perhaps there is electrical noise interaction between the Linksys and the modem.
     
  10. pcguy

    pcguy LI Guru Member

    No since the cable goes to my IPTV box which also supplies the internet directly into the WAN port i.e. the IPTV box has a built in modem. This cable runs through the basement up through the floor and into the LinkSys. So it is not easily replaced. I can check the crimping though.


    It has been 24 hours since I flashed the LinkSys with 4.30.12 firmware. Seems that the Canadian Linksys site shows the 4.30.11 as the current version. Too bad 4 of ther 5 tech support people did not point the discrepancy out would of saved me a lot of wasted time. I have not had a disconnect since flashing to 4.30.12 will have to see if this has fixed the problem.

    However I am still concerned that Tomato can not run properly on this router since Tomato is the reason why I bought the router.
     
  11. sander815

    sander815 Network Guru Member

    same here
    i have 3 wrt54gs,1 with 1.17 and 2 with 1.19

    andf with my laptop with a intell 2200 bg i get constant disconnects
    i however did not erase vram, is that important?
     
  12. LLigetfa

    LLigetfa LI Guru Member

    Do you have the latest Intel 2200 drivers? Is this Windows? WZC or PROSet?
     
  13. pcguy

    pcguy LI Guru Member

    Well this problem occurs frequently due to power loss

    Still having this frustrating time with 2 WRT54GL v 1.1 routers which experience reconnection problems when the WAN looses the connection for some reason. Thought it was the dd-wrt firmware but after using the Linksys for a day I also got the problem when there was a power failure. The only way to reconnect is to power cycle the router.

    ISP support only support their own overpriced routers and say that there is nothing wrong with the connection.

    THe last time I had this problem I wound up cloing the MAC id of the computer which had no problem when hooked directly up the modem bypassing the router. That worked until I decided to try dd-wrt on the second WRT54GL. Had nothing but problems with WAN disconnects and unable to reconnect to PPoE DSL connection unless the router was power cycled. Stock Linksys firmware went fine until the power was lost and I had to revert back to Tomato firmware. Won't know for sure if its more stable for a couple of days. Was unable to determine what caused the disconnects with the stock linksys firmware since router does not allow logging to an external source.

    Router is on a surge bar.
     
  14. mrap

    mrap Addicted to LI Member

    I had a problem with both a DLink 524 and my current Tomato'ed router. Both of them connected to the Westell DSL modem via Homeplug/Ethernet over Power Line. Both couldn't connect when the modem returned after losing power/restarting. I resolved the issue by replacing the Westell with an Alcatel SpeedTouch. Now when the modem loses power and restarts, the Tomato'ed router can reconnect to the modem and initiate the PPPoE connection.

    Short story, try another modem if possible.
     
  15. pcguy

    pcguy LI Guru Member

    Well I am in Canada so the selection of routers is limited and the modem in this case is in a TVoIP box supplied by my ISP which is also supplying TV signals.
     
  16. mrap

    mrap Addicted to LI Member

    Previously, my solution was to use 2 routers. The first did PPPoE to the modem and was directly connected to the modem. Then the router connected to my tomato'ed router via homeplug. HTH.
     
  17. pcguy

    pcguy LI Guru Member

    Sorry but I do not see how that would help with disconnects on the WAN port on the one connected to the modem? All that would do is to isolate the LAN on the Tomatoed router from seeing traffic on any of the LAN ports on the 1st router.
     

Share This Page