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

Linksys WRT54GL v1.1 won't obtain WAN IP. Help me please?

Discussion in 'Networking Issues' started by Luddrigo, Aug 3, 2011.

  1. Luddrigo

    Luddrigo Networkin' Nut Member

    Hello everybody!

    Disclaimer: My native language is swedish, I might have some grammar issues when writing in english. :)

    I have run in to some problem with my good old Linksys WRT54GL. Suddenly it can not obtain a WAN IP from my ISP. I haven't done anything in particular - it just stopped working when I was on a short vacation and I don't know how to fix it. Maybe there was som thunderstorm or something that fried it.

    My setup is as follows.
    ADSL

    Modem: Zyxel P-660H-D1 running in bridged mode. -->
    Linksys WRT54GL running tomato-ND-1.28.7617-Toastman-K24-Std setup to use DHCP on the WAN side -->
    My PC / My wife's PC / Boxee Box / Some iPhones running on the wireless every now and then.

    Nothing fancy I believe and I can't figure out whats happening.

    Apparently my ISP (Telia) gives out IP's using DHCP and they claim to use som sort of MAC lock out timer of 20 minutes but that does not seem to work. I can connect my computer directly into the modem and get internet connectivity and 10 seconds later connect my replacement router and that too will get acces to the internet.

    I have used the factory reset button thing on both the modem and the Linksys numerous times, I have power cycled all the equipment connected more times than I can count. I have flashed the Linksys with the stock firmware but to no avail. It wont get a ip.

    I can not live whitout internet so I ran out and bought a replacement router (Netgear WNDR3700) and connected that. Boom! I got internet. I fooled around with it for a while and noticed that the QoS function is utter crap compared to the one in Tomato. The gigabit lan was nice though so my plan is to use the netgear as a switch and wireless AP and the Linksys as DHCP-server and for the amazing QoS-stuff.

    But how can I get my Linksys router to work? The little green "internet" LED is flashing when I connect my TP-cable and the modem LED indicates that something is connected but thats it. No IP. My ISP won't help me with my home network so now I turn to you. Please help? :)

    If I connect my computer directly to the modem and configure my computer to use 192.168.1.2 I can reach the modem config GUI with 192.168.1.1. But before this router thing happened I could use 192.168.1.1 when connected to the router to reach the Linksys GUI. That leads me to believe that the Zyxel modem is transparent and just a bridge.

    I have tried to set the LAN IP's via DHCP to the 172.16.0.X range instead. When that didn't work I tried the 192.168.2.X range and when that didn't work I tried the 10.0.0.X range. When the router worked and could get an IP it had the 192.168.1.1 IP though so I don't think it should matter.

    I have tried the 30/30/30 reset thing with both the modem and the Linksys numerous times. Should I just accept the fact that it's broken and try to find another one or is it fixable?
     
  2. Toink

    Toink Network Guru Member

    Just curious, is your ADSL modem set to bridge mode and your router is doing the DHCP function? You should be able to confirm this by logging into your ADSL modem... Did you also try to reset your PC's IP address during the process each time you were changing the range IP's?

    BTW Toastman's latest build K24 build for the WRT54GL is 7624, why don't you try it? Be warned that DHCP in this build is set to desabled by default. You need to set a static IP address on your computer first before you flash your router and tinker the settings....
     
  3. Luddrigo

    Luddrigo Networkin' Nut Member

    Yes, the ADSL modem is set to bridged mode. According to my ISP that is the default behaviour but they use some sort of custom firmware for their triple play stuff but I only have the internet service. When logging in to the ADSL modem I can confirm the bridge mode. The Linksys is doing the DHCP and doing it well. I did the ipconfig /release and /renew on my PC when trying the different ranges and my PC was the only thing connected to it and the wireless function is turned off.
     
  4. Toink

    Toink Network Guru Member

    Please try using the updated firmware (take note of the DHCP, disabled by default). Perhaps the latest one could fix your setup...

    You may also try changing the IP address of your ADSL modem to 192.168.0.1 and the WRT54GL to 192.168.1.1...

    Please try setting each device one at a time. After setting up a static IP to your computer, connect your PC directly to your modem to change the IP address. Then connect to you router, to set up.
     
  5. Luddrigo

    Luddrigo Networkin' Nut Member

    I will try this and report back when finished.
     
  6. Luddrigo

    Luddrigo Networkin' Nut Member

    The new firmware did not work either. I flashed it and then turned off all the connected devices and then started to power them up one by one starting with the modem and ending with my PC. No go. I poked around a little in the GUI of the modem and took som screenshots.

    LAN settings
    1.png

    WAN settings
    2.png

    I did not found any logs in the modem but I found it in the Linksys. I can't make anything of the content but someone might.

    Code:
    Jan  1 01:00:03 unknown syslog.info syslogd started: BusyBox v1.18.4
    Jan  1 01:00:03 unknown user.notice kernel: klogd started: BusyBox v1.18.4 (2011-07-02 18:18:46 ICT)
    Jan  1 01:00:03 unknown user.warn kernel: CPU revision is: 00029008
    Jan  1 01:00:03 unknown user.warn kernel: Primary instruction cache 16kB, physically tagged, 2-way, linesize 16 bytes.
    Jan  1 01:00:03 unknown user.warn kernel: Primary data cache 8kB, 2-way, linesize 16 bytes.
    Jan  1 01:00:03 unknown user.warn kernel: Linux version 2.4.37.11 (root@tomato) (gcc version 3.4.6) #9 2011-07-02 18:21:19 ICT
    Jan  1 01:00:03 unknown user.warn kernel: Setting the PFC to its default value
    Jan  1 01:00:03 unknown user.warn kernel: Determined physical RAM map:
    Jan  1 01:00:03 unknown user.warn kernel:  memory: 01000000 @ 00000000 (usable)
    Jan  1 01:00:03 unknown user.warn kernel: On node 0 totalpages: 4096
    Jan  1 01:00:03 unknown user.warn kernel: zone(0): 4096 pages.
    Jan  1 01:00:03 unknown user.warn kernel: zone(1): 0 pages.
    Jan  1 01:00:03 unknown user.warn kernel: zone(2): 0 pages.
    Jan  1 01:00:03 unknown user.warn kernel: Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
    Jan  1 01:00:03 unknown user.warn kernel: CPU: BCM5352 rev 0 pkg 2 at 250 MHz
    Jan  1 01:00:03 unknown user.warn kernel: Using 125.000 MHz high precision timer.
    Jan  1 01:00:03 unknown user.warn kernel: Calibrating delay loop... 249.03 BogoMIPS
    Jan  1 01:00:03 unknown user.info kernel: Memory: 14296k/16384k available (1463k kernel code, 2088k reserved, 100k data, 84k init, 0k highmem)
    Jan  1 01:00:03 unknown user.info kernel: Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
    Jan  1 01:00:03 unknown user.info kernel: Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
    Jan  1 01:00:03 unknown user.info kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
    Jan  1 01:00:03 unknown user.info kernel: Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
    Jan  1 01:00:03 unknown user.warn kernel: Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
    Jan  1 01:00:03 unknown user.warn kernel: Checking for 'wait' instruction...  unavailable.
    Jan  1 01:00:03 unknown user.warn kernel: POSIX conformance testing by UNIFIX
    Jan  1 01:00:03 unknown user.warn kernel: PCI: no core
    Jan  1 01:00:03 unknown user.warn kernel: PCI: Fixing up bus 0
    Jan  1 01:00:03 unknown user.info kernel: Linux NET4.0 for Linux 2.4
    Jan  1 01:00:03 unknown user.info kernel: Based upon Swansea University Computer Society NET3.039
    Jan  1 01:00:03 unknown user.warn kernel: Initializing RT netlink socket
    Jan  1 01:00:03 unknown user.warn kernel: Starting kswapd
    Jan  1 01:00:03 unknown user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
    Jan  1 01:00:03 unknown user.info kernel: devfs: boot_options: 0x1
    Jan  1 01:00:03 unknown user.info kernel: squashfs: version 3.0 (2006/03/15) Phillip Lougher
    Jan  1 01:00:03 unknown user.warn kernel: pty: 256 Unix98 ptys configured
    Jan  1 01:00:03 unknown user.info kernel: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
    Jan  1 01:00:03 unknown user.info kernel: ttyS00 at 0xb8000300 (irq = 3) is a 16550A
    Jan  1 01:00:03 unknown user.info kernel: ttyS01 at 0xb8000400 (irq = 3) is a 16550A
    Jan  1 01:00:03 unknown user.warn kernel: HDLC line discipline: version $Revision: 3.7 $, maxframe=4096
    Jan  1 01:00:03 unknown user.info kernel: N_HDLC line discipline registered.
    Jan  1 01:00:03 unknown user.info kernel: PPP generic driver version 2.4.2
    Jan  1 01:00:03 unknown user.info kernel: MPPE/MPPC encryption/compression module registered
    Jan  1 01:00:03 unknown user.info kernel: PPPoL2TP kernel driver, V0.15.1
    Jan  1 01:00:03 unknown user.info kernel: PPTP driver version 0.8.5
    Jan  1 01:00:03 unknown user.debug kernel: Physically mapped flash: Found an alias at 0x400000 for the chip at 0x0
    Jan  1 01:00:03 unknown user.debug kernel: Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
    Jan  1 01:00:03 unknown user.debug kernel: Physically mapped flash: Found an alias at 0xc00000 for the chip at 0x0
    Jan  1 01:00:03 unknown user.debug kernel: Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0
    Jan  1 01:00:03 unknown user.debug kernel: Physically mapped flash: Found an alias at 0x1400000 for the chip at 0x0
    Jan  1 01:00:03 unknown user.debug kernel: Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0
    Jan  1 01:00:03 unknown user.debug kernel: Physically mapped flash: Found an alias at 0x1c00000 for the chip at 0x0
    Jan  1 01:00:03 unknown user.notice kernel:  Amd/Fujitsu Extended Query Table v3.3 at 0x0040
    Jan  1 01:00:03 unknown user.notice kernel:  Flash Id: Vendor: 0x00ec Device: 0x00a2
    Jan  1 01:00:03 unknown user.notice kernel: number of CFI chips: 1
    Jan  1 01:00:03 unknown user.notice kernel: cfi_cmdset_0002: Disabling fast programming due to code brokenness.
    Jan  1 01:00:03 unknown user.notice kernel: Flash device: 0x400000 at 0x1c000000
    Jan  1 01:00:03 unknown user.notice kernel: Creating 5 MTD partitions on "Physically mapped flash":
    Jan  1 01:00:03 unknown user.notice kernel: 0x00000000-0x00040000 : "pmon"
    Jan  1 01:00:03 unknown user.notice kernel: 0x00040000-0x003f0000 : "linux"
    Jan  1 01:00:03 unknown user.notice kernel: 0x000bec00-0x003a0000 : "rootfs"
    Jan  1 01:00:03 unknown user.notice kernel: 0x003a0000-0x003f0000 : "jffs2"
    Jan  1 01:00:03 unknown user.notice kernel: 0x003f0000-0x00400000 : "nvram"
    Jan  1 01:00:03 unknown user.err kernel: sflash: found no supported devices
    Jan  1 01:00:03 unknown user.info kernel: Initializing Cryptographic API
    Jan  1 01:00:03 unknown user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
    Jan  1 01:00:03 unknown user.info kernel: IP Protocols: ICMP, UDP, TCP, IGMP
    Jan  1 01:00:03 unknown user.info kernel: IP: routing cache hash table of 16384 buckets, 128Kbytes
    Jan  1 01:00:03 unknown user.info kernel: TCP: Hash tables configured (established 1024 bind 2048)
    Jan  1 01:00:03 unknown user.info kernel: Linux IP multicast router 0.06 plus PIM-SM
    Jan  1 01:00:03 unknown user.warn kernel: ip_conntrack version 2.1 (16384 buckets, 8192 max) - 352 bytes per conntrack
    Jan  1 01:00:03 unknown user.warn kernel: ip_tables: (C) 2000-2002 Netfilter core team
    Jan  1 01:00:03 unknown user.warn kernel: tomato_ct.c [Jul  2 2011 18:02:05]
    Jan  1 01:00:03 unknown user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
    Jan  1 01:00:03 unknown user.info kernel: NET4: Ethernet Bridge 008 for NET4.0
    Jan  1 01:00:03 unknown user.info kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
    Jan  1 01:00:03 unknown user.info kernel: All bugs added by David S. Miller <davem@redhat.com>
    Jan  1 01:00:03 unknown user.warn kernel: VFS: Mounted root (squashfs filesystem) readonly.
    Jan  1 01:00:03 unknown user.info kernel: Mounted devfs on /dev
    Jan  1 01:00:03 unknown user.info kernel: Freeing unused kernel memory: 84k freed
    Jan  1 01:00:03 unknown user.debug kernel: PCI: Setting latency timer of device 00:01.0 to 64
    Jan  1 01:00:03 unknown user.warn kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 4.150.10.29
    Jan  1 01:00:03 unknown user.debug kernel: PCI: Setting latency timer of device 00:05.0 to 64
    Jan  1 01:00:03 unknown user.warn kernel: eth1: Broadcom BCM4320 802.11 Wireless Controller 4.150.10.29
    Jan  1 01:00:03 unknown user.warn kernel: ip_conntrack_rtsp v0.01 loading
    Jan  1 01:00:03 unknown user.warn kernel: ip_nat_rtsp v0.01 loading
    Jan  1 01:00:03 unknown user.warn kernel: ip_conntrack_pptp version 1.9 loaded
    Jan  1 01:00:03 unknown user.warn kernel: ip_nat_pptp version 1.5 loaded
    Jan  1 01:00:03 unknown user.warn kernel: Algorithmics/MIPS FPU Emulator v1.5
    Jan  1 01:00:03 unknown user.debug kernel: vlan0: dev_set_allmulti(master, 1)
    Jan  1 01:00:03 unknown user.debug kernel: vlan0: dev_set_promiscuity(master, 1)
    Jan  1 01:00:03 unknown user.info kernel: device eth0 entered promiscuous mode
    Jan  1 01:00:03 unknown user.info kernel: device vlan0 entered promiscuous mode
    Jan  1 01:00:03 unknown user.info kernel: device eth1 entered promiscuous mode
    Jan  1 01:00:03 unknown user.info kernel: br0: port 2(eth1) entering learning state
    Jan  1 01:00:03 unknown user.info kernel: br0: port 1(vlan0) entering learning state
    Jan  1 01:00:03 unknown user.info kernel: br0: port 2(eth1) entering forwarding state
    Jan  1 01:00:03 unknown user.info kernel: br0: topology change detected, propagating
    Jan  1 01:00:03 unknown user.info kernel: br0: port 1(vlan0) entering forwarding state
    Jan  1 01:00:03 unknown user.info kernel: br0: topology change detected, propagating
    Jan  1 01:00:03 unknown user.warn kernel: vlan1: Setting MAC address to  00 18 39 bc 69 d9.
    Jan  1 01:00:04 unknown user.info kernel: IMQ driver loaded.
    Jan  1 01:00:04 unknown user.info kernel:    Hooking IMQ before NAT on PREROUTING.
    Jan  1 01:00:04 unknown user.info kernel:    Hooking IMQ after NAT on POSTROUTING.
    Jan  1 01:00:04 unknown user.debug kernel: vlan1: add 01:00:5e:00:00:01 mcast address to master interface
    Jan  1 01:00:05 unknown daemon.info dnsmasq[121]: started, version 2.57 cachesize 1500
    Jan  1 01:00:05 unknown daemon.info dnsmasq[121]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP TFTP no-IDN
    Jan  1 01:00:05 unknown daemon.info dnsmasq[121]: asynchronous logging enabled, queue limit is 5 messages
    Jan  1 01:00:05 unknown daemon.warn dnsmasq[121]: failed to access /etc/resolv.dnsmasq: No such file or directory
    Jan  1 01:00:05 unknown daemon.info dnsmasq[121]: read /etc/hosts - 2 addresses
    Jan  1 01:00:05 unknown daemon.info dnsmasq[121]: read /etc/dnsmasq/hosts/hosts - 3 addresses
    Jan  1 01:00:05 unknown user.info init[1]: Linksys WRT54G/GS/GL: Tomato 1.28.7624 -Toastman-ND ND VPN
    To be able to connect to the modem I had to set a static IP on the PC. When changing this to automatic I got a IP address and was able to surf. When I was done I did a ipconfig /release just in case before plugging in the Netgear again so I can type this.

    Setting the modem IP to 192.168.0.1 and the Linksys to 192.168.1.1 did not change anything.
     
  7. Toink

    Toink Network Guru Member

    Did you also enable DHCP in Tomato? Then release/renew WAN in Tomato webgui?

    Were you able to reset your PC's static IP to "auto obtain"?

    BTW here's a tip if you want to access your modem without the need of directly connecting your PC to the modem:

    1. Paste this in your Tomato's 'Firewall' script tab, make sure you paste it on the top most of the script field:

    iptables -I POSTROUTING -t nat -o vlan1 -d 192.168.0.0/30 -j MASQUERADE
    ip addr add 192.168.0.2/30 dev vlan1 brd +

    2. Save.

    3. Connect your modem to your router and reboot your router.

    Wait a couple or so minutes for your router to fully reboot. You should be able to access your modem while connected to the router.
     
  8. Luddrigo

    Luddrigo Networkin' Nut Member

    Yes and yes. When I press release it waits a second or two and then stays "Disconnected", when pressing renew it just stays "Renewing" forever.

    A1.png

    Yes, the PC is getting a LAN IP from the DHCP range.

    nic.png

    That sounds like a neat and time saving trick, unfortunately it did not work. When trying to go to 192.168.0.1 I get an ERR_CONNECTION_TIMED_OUT error in my browser. I cannot ping 192.168.0.1 either.

    A2.png

    Could it be possible that the WAN port is partly broken somehow? If so, could I use the VLAN stuff to use a LAN port as WAN instead?
     
  9. Toink

    Toink Network Guru Member

    Hmm... I'm actually at a loss with your issue....

    Stupid question: have you tried using another LAN cable to connect the WAN port of your router to your modem? :D

    It could be a WAN port issue... I honestly haven't tinkered with the VLAN GUI...

    Calling everyone out there who's willing to chime-in! Let's try to help Luddrigo here if you can... Thanks!
     
  10. Luddrigo

    Luddrigo Networkin' Nut Member

    Yup, I turned the house and garage upside down and tried every single cable I could find. The one that is connected now gives internet access to the netgear router and "should" be working ok.

    I will research the VLAN stuff and see if I can understand it. Thank you for you efforts so far. :)
     
  11. Toink

    Toink Network Guru Member

    I'm sorry I wasn't much of any help. I hope someone else would be able to chime in... I got a feeling your WRT54GL's WAN port may have gave in...

    Can't you not return the WNDR3700 and replace it with an E3000 or E2000? :)
     
  12. Luddrigo

    Luddrigo Networkin' Nut Member

    I have the possibility to return the router for 30 days if I am not satisfied, and I am not. :p But the company where I bought the Netgear does not seem to have ANY Linksys routers for sale and that just sucks. The WRT54GL is the best router I ever had (with the Tomato firmware) and I would really like to use one again. I could hopefully return it and get my money back and find a Linksys somewhere else.

    It has to be on the same day though because my wife would kill me if she won't be able to play WoW for a few days. :p
     
  13. Luddrigo

    Luddrigo Networkin' Nut Member

    Well, the situation have sort of resolved itself. I went back to the store and returned the WNDR3700 and according to the sales person I was not the first one. They did not have a E3000 or anything Linksys at all so I got the next best thing (I hope), the WNR3500L. After installing Tomato firmware on that I was up and running.

    The old WRT54GL now serves as a WDS on the second floor and doing it well so I did not have to use it as a paper weight. I still haven't found out whats wrong with it and that bugs me a little. My best guess is the WAN port.

    Thanks again. :)
     
  14. Toink

    Toink Network Guru Member

    The WNR3500L is definitely better than the WNDR3700 :) The WRT54GL surely served you well and it running as WDS renders it still usable....

    Cheers! :)
     
  15. budoushi

    budoushi Networkin' Nut Member

    I have the possibility to return the router for 30 days if I am not satisfied, and I am not. :p But the company where I bought the Netgear does not seem to have ANY Linksys routers for sale and that just sucks. The WRT54GL is the best router I ever had (with the Tomato firmware) and I would really like to use one again. I could hopefully return it and get my money back and find a Linksys somewhere else.
     
  16. sdx

    sdx Networkin' Nut Member

    Hi Luddrigo,
    I ended up here googling around for my linksys issue. It looks exactly the same, I also tried all the options listed in this threat. It just will no obtain any ip on the WAN interface. BTW: I'm also using tomato.
    There is one difference. My ISP changed the modem to a voip enabled one. I had an Internet connection on it, so the combination worked. But renewing the IP waits now like forever.
    Getting an ip from my isp with any other device works directly. I tried spoofing a MAC but without success.
    I'm now also at a phase that I think the the router has given up on me.
    I hope maybe someone will pick up this threat and enlighten us with a solution. :)
     

Share This Page