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

Help! Cannot Access Web GUI

Discussion in 'Tomato Firmware' started by atonz13, Jul 22, 2012.

  1. atonz13

    atonz13 Serious Server Member

    Hello, I am new and flashed my Linksys E3000 with toastman (/tomato-E3000-NVRAM60K-12875002). Everything was working fine until my devices were rebooted and now the device does not connect to the internet. Wireless and even wired connection to the router do not enable me to access the web UI via 192.168.1.1. I have tried :80 etc to no avail. I can view the wireless network 'wireless' but cannot connect to the internet. I have attempted to reset the router as well. Help?
     
  2. gfunkdave

    gfunkdave LI Guru Member

    Did you reactivate DHCP on the router?
     
  3. atonz13

    atonz13 Serious Server Member

    Thanks for the quick reply. I understand that toastman has DHCP disabled by default. I edited some value under DHCP to '0.0.0.1' since apparently '0.0.0.0' disabled it. Forgive my noobness :p
     
  4. atonz13

    atonz13 Serious Server Member

    I used ipconfig and here is what I get
    Wireless LAN adapter Wireless Network Connection 2:
    Connection-specific DNS Suffix . :
    Link-local IPv6 Address … . . : fe80::5569:e0a0:84e6:d910%19
    Autoconfiguration IPv4 Address. . : 169.254.217.16
    Subnet Mask … … … . . : 255.255.0.0
    Default Gateway … … … :
     
  5. Dark_Shadow

    Dark_Shadow Addicted to LI Member

    Set static IP on PC then access router make configuration, turn on DHCP, then set PC back to auto DHCP
     
  6. atonz13

    atonz13 Serious Server Member

    I'm learning how to do these things as they are suggested. Set static IP to what exactly? Does it have to correspond to the IPv4 address?
     
  7. Dark_Shadow

    Dark_Shadow Addicted to LI Member

    Set static ip on the device trying to access the router to 192.168.1.7
     
  8. atonz13

    atonz13 Serious Server Member

    Set it to 192.168.1.1 and now was able to access web UI.

    How should I set up DHCP? I see options under WAN/Internet and LAN. What should I set Route Modem IP to? Should I click the box under LAN that says DHCP Server?

    Thanks for your help!
     
  9. Dark_Shadow

    Dark_Shadow Addicted to LI Member

    Yes,check the box, other than that I don't know your physical network.
     
  10. atonz13

    atonz13 Serious Server Member

  11. Toastman

    Toastman Super Moderator Staff Member Member

    I had some emails asking "why".

    Just for everyone's information, this is WHY the DHCP is disabled by default.

    When a router or AP loses power, for example, during a power cut/brownout, on restoration of power it is vulnerable to another "cut", if the timing of the next power glitch is just right, it will result in NVRAM corruption and the router will lose it's NVRAM settings.

    When an AP or a gateway router does this, it will of course then reappear on the network as 19.168.1.1 and begin issuing the wrong IP's to anyone who asks for them! There is no longer any access restriction or security. This totally screws up your network and it can takes several hours to sort out. And if you already have another machine on your network using 192.168.1.1 - then you also have an additional problem of 2 machines now using the same IP. So you probably can't even reach the failed machine to reconfigure it!

    Of course the more AP's you have the more chance there is of this happening, and it is very important for large installations that this be prevented, as the problems it causes have serious implications. Commonly I use up to 30 AP's in a building. You can reduce the chances of this happening to almost zero by running everything off a UPS.

    The best method to combat this is:

    1) Don't use 192.168.1.1 on your network.
    2) Disable DHCP by default.

    Now if a router or AP loses configuration, it will reappear on the network as 192.168.1.1 without causing any problems to anyone by issuing the wrong IP's - it no longer issues IP's at all, and it doesn't conflict with any other router using 192.168.1.1.

    Also, since you KNOW that any failed AP will be on 192.168.1.1, it is easily noticed and then reconfigured, either locally or by remote access using port forwarding.

    i.e. if you even suspect that an nvram corruption has occurred, just look for a machine using 192.168.1.1.

    useful links:

    Remote Access to AP's
    http://www.linksysinfo.org/index.ph...orial-and-discussion.28349/page-4#post-138522

    Easy Backup and Restore
    http://www.linksysinfo.org/forums/showpost.php?p=362345&postcount=221
     

Share This Page