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

tomato cannot login

Discussion in 'Tomato Firmware' started by lvmm, Oct 5, 2007.

  1. lvmm

    lvmm Guest

    A couple of days ago my WRT54GL with Tomato has developed a problem. It all started on October 2d with some sort of DSL trouble. My ISP promptly fixed it, after that I noticed that my WRT took some time to connect but I didn't pay much attention at that time. Next day I noticed that WAN link is down and my router cannot obtain WAN address. I called ISP tech support again and while on hold tried to plug a computer directly into a modem - it promptly connected. Hmmm. I hung up and started investigating. Well, to cut it short I found out that WRT connects successfully and then immediately disconnects or is disconnected - here are my ISP's logs

    Code:
    Login	Logout	Address	In	Out
    04.10.2007 07:19:36   	 04.10.2007 20:56:16   	 91.76.16.158   	 2727.0940   	 1419.7529 
     04.10.2007 07:18:47  	 04.10.2007 07:18:48  	 91.76.16.144  	 0.0000  	 0.0000 
     04.10.2007 00:18:54  	 04.10.2007 00:18:56  	 91.76.19.225  	 0.0001  	 0.0000 
     04.10.2007 00:17:52  	 04.10.2007 00:17:54  	 91.76.19.68  	 0.0000  	 0.0000 
     04.10.2007 00:16:50  	 04.10.2007 00:16:52  	 91.76.19.2  	 0.0000  	 0.0000 
     03.10.2007 23:59:52  	 03.10.2007 23:59:53  	 91.76.16.177  	 0.0000  	 0.0000 
     03.10.2007 23:59:27  	 03.10.2007 23:59:29  	 91.76.19.203  	 0.0000  	 0.0000 
     03.10.2007 23:56:14  	 03.10.2007 23:56:16  	 91.76.18.103  	 0.0000  	 0.0000 
     03.10.2007 23:53:11  	 03.10.2007 23:53:13  	 91.76.19.57  	 0.0001  	 0.0000 
     03.10.2007 23:45:45  	 03.10.2007 23:45:47  	 85.140.85.143  	 0.0000  	 0.0000 
     03.10.2007 23:42:41  	 03.10.2007 23:42:43  	 91.76.18.32  	 0.0000  	 0.0000 
     03.10.2007 23:34:06  	 03.10.2007 23:34:08  	 85.140.85.137  	 0.0000  	 0.0000 
     03.10.2007 23:33:16  	 03.10.2007 23:33:17  	 91.76.18.12  	 0.0000  	 0.0000 
     03.10.2007 23:23:53  	 03.10.2007 23:23:54  	 91.76.17.130  	 0.0000  	 0.0000 
    
    and my /var/log/messages

    Code:
    Jan  1 00:00:07 wrt54 syslog.info syslogd started: BusyBox v1.2.2
    Jan  1 00:00:07 wrt54 user.notice kernel: klogd started: BusyBox v1.2.2 (2007.09.30-10:41+0000)
    Jan  1 00:00:07 wrt54 user.warn kernel: CPU revision is: 00029008
    Jan  1 00:00:07 wrt54 user.warn kernel: Primary instruction cache 16kb, linesize 16 bytes (2 ways)
    Jan  1 00:00:07 wrt54 user.warn kernel: Primary data cache 8kb, linesize 16 bytes (2 ways)
    Jan  1 00:00:07 wrt54 user.warn kernel: Linux version 2.4.20 (root@etch) (gcc version 3.2.3 with Broadcom modifications) #2 Sun Sep 30 04:00:14 PDT 2007
    Jan  1 00:00:07 wrt54 user.warn kernel: Setting the PFC value as 0x15
    Jan  1 00:00:07 wrt54 user.warn kernel: Determined physical RAM map:
    Jan  1 00:00:07 wrt54 user.warn kernel:  memory: 01000000 @ 00000000 (usable)
    Jan  1 00:00:07 wrt54 user.warn kernel: On node 0 totalpages: 4096
    Jan  1 00:00:07 wrt54 user.warn kernel: zone(0): 4096 pages.
    Jan  1 00:00:07 wrt54 user.warn kernel: zone(1): 0 pages.
    Jan  1 00:00:07 wrt54 user.warn kernel: zone(2): 0 pages.
    Jan  1 00:00:07 wrt54 user.warn kernel: Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
    Jan  1 00:00:07 wrt54 user.warn kernel: CPU: BCM5352 rev 0 at 200 MHz
    Jan  1 00:00:07 wrt54 user.warn kernel: Calibrating delay loop... 199.47 BogoMIPS
    Jan  1 00:00:07 wrt54 user.info kernel: Memory: 14476k/16384k available (1321k kernel code, 1908k reserved, 108k data, 64k init, 0k highmem)
    Jan  1 00:00:07 wrt54 user.info kernel: Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
    Jan  1 00:00:07 wrt54 user.info kernel: Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
    Jan  1 00:00:07 wrt54 user.warn kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    Jan  1 00:00:07 wrt54 user.warn kernel: Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
    Jan  1 00:00:07 wrt54 user.warn kernel: Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
    Jan  1 00:00:07 wrt54 user.warn kernel: Checking for 'wait' instruction...  unavailable.
    Jan  1 00:00:07 wrt54 user.warn kernel: POSIX conformance testing by UNIFIX
    Jan  1 00:00:07 wrt54 user.warn kernel: PCI: no core
    Jan  1 00:00:07 wrt54 user.warn kernel: PCI: Fixing up bus 0
    Jan  1 00:00:07 wrt54 user.info kernel: Linux NET4.0 for Linux 2.4
    Jan  1 00:00:07 wrt54 user.info kernel: Based upon Swansea University Computer Society NET3.039
    Jan  1 00:00:07 wrt54 user.warn kernel: Initializing RT netlink socket
    Jan  1 00:00:08 wrt54 user.warn kernel: Starting kswapd
    Jan  1 00:00:08 wrt54 user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
    Jan  1 00:00:08 wrt54 user.info kernel: devfs: boot_options: 0x1
    Jan  1 00:00:08 wrt54 user.info kernel: Squashfs 2.2-r2 (released 2005/09/08) (C) 2002-2005 Phillip Lougher
    Jan  1 00:00:08 wrt54 user.warn kernel: pty: 256 Unix98 ptys configured
    Jan  1 00:00:08 wrt54 user.info kernel: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
    Jan  1 00:00:08 wrt54 user.info kernel: ttyS00 at 0xb8000300 (irq = 3) is a 16550A
    Jan  1 00:00:08 wrt54 user.info kernel: ttyS01 at 0xb8000400 (irq = 0) is a 16550A
    Jan  1 00:00:08 wrt54 user.warn kernel: HDLC line discipline: version $Revision: 1.1.1.4 $, maxframe=4096
    Jan  1 00:00:08 wrt54 user.info kernel: N_HDLC line discipline registered.
    Jan  1 00:00:08 wrt54 user.info kernel: PPP generic driver version 2.4.2
    Jan  1 00:00:08 wrt54 user.debug kernel: Physically mapped flash: Found an alias at 0x400000 for the chip at 0x0
    Jan  1 00:00:08 wrt54 user.debug kernel: Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
    Jan  1 00:00:08 wrt54 user.debug kernel: Physically mapped flash: Found an alias at 0xc00000 for the chip at 0x0
    Jan  1 00:00:08 wrt54 user.debug kernel: Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0
    Jan  1 00:00:08 wrt54 user.debug kernel: Physically mapped flash: Found an alias at 0x1400000 for the chip at 0x0
    Jan  1 00:00:08 wrt54 user.debug kernel: Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0
    Jan  1 00:00:08 wrt54 user.debug kernel: Physically mapped flash: Found an alias at 0x1c00000 for the chip at 0x0
    Jan  1 00:00:08 wrt54 user.notice kernel:  Amd/Fujitsu Extended Query Table v3.3 at 0x0040
    Jan  1 00:00:08 wrt54 user.notice kernel: number of CFI chips: 1
    Jan  1 00:00:08 wrt54 user.notice kernel: Flash device: 0x400000 at 0x1c000000
    Jan  1 00:00:08 wrt54 user.notice kernel: Creating 5 MTD partitions on "Physically mapped flash":
    Jan  1 00:00:08 wrt54 user.notice kernel: 0x00000000-0x00040000 : "pmon"
    Jan  1 00:00:08 wrt54 user.notice kernel: 0x00040000-0x003f0000 : "linux"
    Jan  1 00:00:08 wrt54 user.notice kernel: 0x000e1a28-0x002f0000 : "rootfs"
    Jan  1 00:00:08 wrt54 user.notice kernel: 0x002f0000-0x003f0000 : "jffs2"
    Jan  1 00:00:08 wrt54 user.notice kernel: 0x003f0000-0x00400000 : "nvram"
    Jan  1 00:00:08 wrt54 user.err kernel: sflash: found no supported devices
    Jan  1 00:00:08 wrt54 user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
    Jan  1 00:00:08 wrt54 user.info kernel: IP Protocols: ICMP, UDP, TCP, IGMP
    Jan  1 00:00:08 wrt54 user.info kernel: IP: routing cache hash table of 512 buckets, 4Kbytes
    Jan  1 00:00:08 wrt54 user.info kernel: TCP: Hash tables configured (established 1024 bind 2048)
    Jan  1 00:00:08 wrt54 user.info kernel: Linux IP multicast router 0.06 plus PIM-SM
    Jan  1 00:00:08 wrt54 user.warn kernel: ip_conntrack version 2.1 (4099 buckets, 2048 max) - 368 bytes per conntrack
    Jan  1 00:00:08 wrt54 user.warn kernel: ip_tables: (C) 2000-2002 Netfilter core team
    Jan  1 00:00:08 wrt54 user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
    Jan  1 00:00:08 wrt54 user.info kernel: NET4: Ethernet Bridge 008 for NET4.0
    Jan  1 00:00:08 wrt54 user.alert kernel: 802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>
    Jan  1 00:00:08 wrt54 user.alert kernel: All bugs added by David S. Miller <davem@redhat.com>
    Jan  1 00:00:08 wrt54 user.warn kernel: VFS: Mounted root (squashfs filesystem) readonly.
    Jan  1 00:00:08 wrt54 user.info kernel: Mounted devfs on /dev
    Jan  1 00:00:08 wrt54 user.info kernel: Freeing unused kernel memory: 64k freed
    Jan  1 00:00:08 wrt54 user.warn kernel: Algorithmics/MIPS FPU Emulator v1.5
    Jan  1 00:00:08 wrt54 user.warn kernel: ip_conntrack_pptp version 1.9 loaded
    Jan  1 00:00:08 wrt54 user.warn kernel: ip_nat_pptp version 1.5 loaded
    Jan  1 00:00:08 wrt54 user.warn kernel: ip_conntrack_rtsp v0.01 loading
    Jan  1 00:00:08 wrt54 user.warn kernel: ip_nat_rtsp v0.01 loading
    Jan  1 00:00:08 wrt54 user.warn kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.38.0
    Jan  1 00:00:08 wrt54 user.warn kernel: eth1: Broadcom BCM4320 802.11 Wireless Controller 3.90.38.0
    Jan  1 00:00:08 wrt54 user.warn kernel: tomato_ct.c [Sep 30 2007 03:58:26]
    Jan  1 00:00:08 wrt54 user.info kernel: vlan0: dev_set_promiscuity(master, 1)
    Jan  1 00:00:08 wrt54 user.info kernel: device eth0 entered promiscuous mode
    Jan  1 00:00:08 wrt54 user.info kernel: device vlan0 entered promiscuous mode
    Jan  1 00:00:08 wrt54 user.info kernel: device eth1 entered promiscuous mode
    Jan  1 00:00:08 wrt54 user.info kernel: br0: port 2(eth1) entering learning state
    Jan  1 00:00:08 wrt54 user.info kernel: br0: port 1(vlan0) entering learning state
    Jan  1 00:00:08 wrt54 user.warn kernel:  4e 65.
    Jan  1 00:00:08 wrt54 user.info kernel: br0: port 2(eth1) entering forwarding state
    Jan  1 00:00:08 wrt54 user.info kernel: br0: topology change detected, propagating
    Jan  1 00:00:08 wrt54 user.info kernel: br0: port 1(vlan0) entering forwarding state
    Jan  1 00:00:08 wrt54 user.info kernel: br0: topology change detected, propagating
    Jan  1 00:00:08 wrt54 cron.notice crond[94]: crond 2.3.2 dillon, started, log level 9 
    Jan  1 00:00:09 wrt54 authpriv.warn dropbear[75]: Failed reading '/etc/dropbear/dropbear_dss_host_key', disabling DSS
    Jan  1 00:00:09 wrt54 authpriv.info dropbear[104]: Running in background
    Jan  1 00:00:09 wrt54 daemon.info httpd[106]: Generating SSL certificate...
    Jan  1 00:00:09 wrt54 user.info kernel: vlan1: add 01:00:5e:00:00:01 mcast address to master interface
    Jan  1 00:00:09 wrt54 daemon.info dnsmasq[105]: started, version 2.40 cachesize 150
    Jan  1 00:00:09 wrt54 daemon.info dnsmasq[105]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
    Jan  1 00:00:09 wrt54 daemon.info dnsmasq[105]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 2d12h
    Jan  1 00:00:09 wrt54 daemon.warn dnsmasq[105]: failed to access /etc/resolv.dnsmasq: No such file or directory
    Jan  1 00:00:09 wrt54 daemon.info dnsmasq[105]: read /etc/hosts - 0 addresses
    Jan  1 00:00:09 wrt54 daemon.info dnsmasq[105]: read /etc/hosts.dnsmasq - 3 addresses
    Jan  1 00:01:01 wrt54 daemon.info dnsmasq[105]: DHCPDISCOVER(br0) 00:18:de:56:68:e4 
    Jan  1 00:01:01 wrt54 daemon.info dnsmasq[105]: DHCPOFFER(br0) 192.168.1.102 00:18:de:56:68:e4 
    Jan  1 00:01:01 wrt54 daemon.info dnsmasq[105]: DHCPREQUEST(br0) 192.168.1.102 00:18:de:56:68:e4 
    Jan  1 00:01:01 wrt54 daemon.info dnsmasq[105]: DHCPACK(br0) 192.168.1.102 00:18:de:56:68:e4 lvm-note
    Jan  1 00:01:31 wrt54 daemon.info dnsmasq[105]: exiting on receipt of SIGTERM
    Jan  1 00:01:31 wrt54 daemon.info dnsmasq[148]: started, version 2.40 cachesize 150
    Jan  1 00:01:31 wrt54 daemon.info dnsmasq[148]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
    Jan  1 00:01:31 wrt54 daemon.info dnsmasq[148]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 2d12h
    Jan  1 00:01:31 wrt54 daemon.info dnsmasq[148]: reading /etc/resolv.dnsmasq
    Jan  1 00:01:31 wrt54 daemon.info dnsmasq[148]: using nameserver 195.34.32.116#53
    Jan  1 00:01:31 wrt54 daemon.info dnsmasq[148]: using nameserver 212.188.4.10#53
    Jan  1 00:01:31 wrt54 daemon.info dnsmasq[148]: read /etc/hosts - 0 addresses
    Jan  1 00:01:31 wrt54 daemon.info dnsmasq[148]: read /etc/hosts.dnsmasq - 3 addresses
    Jan  1 03:02:08 wrt54 daemon.info dnsmasq[148]: exiting on receipt of SIGTERM
    Jan  1 03:02:08 wrt54 daemon.info dnsmasq[209]: started, version 2.40 cachesize 150
    Jan  1 03:02:08 wrt54 daemon.info dnsmasq[209]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
    Jan  1 03:02:08 wrt54 daemon.info dnsmasq[209]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 2d12h
    Jan  1 03:02:08 wrt54 daemon.info dnsmasq[209]: reading /etc/resolv.dnsmasq
    Jan  1 03:02:08 wrt54 daemon.info dnsmasq[209]: using nameserver 195.34.32.116#53
    Jan  1 03:02:08 wrt54 daemon.info dnsmasq[209]: using nameserver 212.188.4.10#53
    Jan  1 03:02:08 wrt54 daemon.info dnsmasq[209]: read /etc/hosts - 0 addresses
    Jan  1 03:02:08 wrt54 daemon.info dnsmasq[209]: read /etc/hosts.dnsmasq - 3 addresses
    Jan  1 03:03:07 wrt54 user.info redial[73]: WAN down, redialing...
    Jan  1 03:03:07 wrt54 daemon.info dnsmasq[209]: exiting on receipt of SIGTERM
    Jan  1 03:03:07 wrt54 daemon.info pppd[77]: Exit.
    Jan  1 03:03:07 wrt54 daemon.info dnsmasq[278]: started, version 2.40 cachesize 150
    Jan  1 03:03:07 wrt54 daemon.info dnsmasq[278]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
    Jan  1 03:03:07 wrt54 daemon.info dnsmasq[278]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 2d12h
    Jan  1 03:03:07 wrt54 daemon.warn dnsmasq[278]: no servers found in /etc/resolv.dnsmasq, will retry
    Jan  1 03:03:07 wrt54 daemon.info dnsmasq[278]: read /etc/hosts - 0 addresses
    Jan  1 03:03:07 wrt54 daemon.notice pppd[277]: pppd 2.4.1 started by root, uid 0
    Jan  1 03:03:07 wrt54 daemon.info dnsmasq[278]: read /etc/hosts.dnsmasq - 3 addresses
    Jan  1 03:06:07 wrt54 user.info redial[275]: WAN down, redialing...
    Jan  1 03:06:07 wrt54 daemon.info dnsmasq[278]: exiting on receipt of SIGTERM
    Jan  1 03:06:07 wrt54 daemon.info pppd[277]: Exit.
    Jan  1 03:06:07 wrt54 daemon.info dnsmasq[359]: started, version 2.40 cachesize 150
    Jan  1 03:06:07 wrt54 daemon.info dnsmasq[359]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
    Jan  1 03:06:07 wrt54 daemon.info dnsmasq[359]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 2d12h
    Jan  1 03:06:07 wrt54 daemon.warn dnsmasq[359]: no servers found in /etc/resolv.dnsmasq, will retry
    Jan  1 03:06:07 wrt54 daemon.info dnsmasq[359]: read /etc/hosts - 0 addresses
    Jan  1 03:06:07 wrt54 daemon.info dnsmasq[359]: read /etc/hosts.dnsmasq - 3 addresses
    Jan  1 03:06:07 wrt54 daemon.notice pppd[360]: pppd 2.4.1 started by root, uid 0
    Jan  1 03:09:07 wrt54 user.info redial[358]: WAN down, redialing...
    Jan  1 03:09:07 wrt54 daemon.info dnsmasq[359]: exiting on receipt of SIGTERM
    Jan  1 03:09:07 wrt54 daemon.info pppd[360]: Exit.
    Jan  1 03:09:08 wrt54 daemon.info dnsmasq[441]: started, version 2.40 cachesize 150
    Jan  1 03:09:08 wrt54 daemon.info dnsmasq[441]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
    Jan  1 03:09:08 wrt54 daemon.info dnsmasq[441]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 2d12h
    Jan  1 03:09:08 wrt54 daemon.warn dnsmasq[441]: no servers found in /etc/resolv.dnsmasq, will retry
    Jan  1 03:09:08 wrt54 daemon.info dnsmasq[441]: read /etc/hosts - 0 addresses
    Jan  1 03:09:08 wrt54 daemon.info dnsmasq[441]: read /etc/hosts.dnsmasq - 3 addresses
    Jan  1 03:09:08 wrt54 daemon.notice pppd[442]: pppd 2.4.1 started by root, uid 0
    
    Not much info I am afraid but it is all I have, if pppoecd leaves any logs I was not able to locate them. Sometimes I can even notice it on the status-overview web screen - several seconds after I press 'connect' button valid WAN IP addresses flash for a short moment, then revert back to 0.0.0.0 and status returns to 'disconnected'. After several attempts it will connect but as on its own Tomato retries every three minutes it may take quite a while - hours at worst. Actually this problem is quite bad - for some unknown reason my ISP forces IP address change every 24 hours so every day I can loose connection for up to several hours. I've checked older logs and found that I had this sort of problem (i.e. connect and immediate disconnect) several times before but not even nearly as bad as now - in September there were just 2 unsuccessful login attepmts of this kind, now I am having dozens every day. If my IPS changed some settings they won't tell me what they did and as I said I can connect easily from a windows or OS/2 (sic!) machine, only Tomato has this problem. So what can the problem be? I haven't got a lot of statistics yet, but I tried to power up my gear early in the morning once and it connected at the first attempt while in the evenings when I did most of the tests it may take as much as 20, so could it be some sort of timeout problem caused by heavy load of ISP's equipment, congestion and that kind of stuff, and for some reason Tomato is less tolerant to it than others? - just a wild guess.

    While investigating I tried erasing nvram and restoring configuration from a backup and upgraded Tomato from 1.07 to 1.09 with no effect at all. My modem is D-link 504G. Actually it is more than a modem but I am using it just as a dumb modem, pppoe authentication and all network stuff is done by the WRT. I have two computers connected by LAN and up to two by wi-fi.
     
  2. mstombs

    mstombs Network Guru Member

    No solution, but I've seen quite a few posts recently re similar problems with specific devices and PPPOE. I believe the issue is down to default values on pppd options such as MRU/MTU (initial value used for negotiation) or LCP_ timeouts.

    Code:
    lcp-echo-failure n
    
        Tells system to terminate the connection if no reply is received to n LCP echo-requests. Normally echo-requests are not used for this purpose because "link down" conditions are determined by the modem hardware.
    lcp-echo-interval n
    
        Tells system to wait n seconds before sending another LCP echo-request when the remote system fails to reply.
    lcp-max-configure n
    
        Tells system to send the LCP configure-request packet a maximum of n times. The default is 10.
    lcp-max-failure n
    
        Tells system to accept up to n LCP configure-NAKs before sending a configure-reject. The default is 10.
    lcp-max-terminate n
    
        Tells system to send no more than n LCP terminate-request transmissions without receiving an acknowledgment. The default is 3.
    lcp-restart n
    
        Tells system to wait n seconds before resending a LCP configure-request packet. The default is 3.
    Not sure if /etc/ppp/options is linked to an editable file in Tomato or whether all options are hardcoded.
     

Share This Page