can't access Tomato firmware webpage

Discussion in 'Tomato Firmware' started by MAJ, Aug 2, 2012.

  1. MAJ

    MAJ Serious Server Member


    I am very new to this so please excuse stupid questions.

    I attempted to install Toastman Tomato to my Linksys WRT160n. The installation appeared to work and I was on the Tomato firmware page. I cleared the NVRAM and then restarted everything (cable modem, router, and computer). Now, I can't get to the firmware page which I think is still supposed to be The router appears to still be working as all the correct lights come on in the correct order, and it broadcasts "wireless" when I turn it on (I hadn't changed any settings yet).

    Am I missing something obvious? What other information would be helpful? I have Comcast internet (which I'm connected to right now, directly plugged in to the modem) and have Windows 7 on my Dell laptop.

    Thank you very much for any help.
  2. Toastman

    Toastman Super Moderator Staff Member Member

  3. azdps

    azdps LI Guru Member

  4. MAJ

    MAJ Serious Server Member

    Wow, a reply from Toastman himself! :) Thank you to azdps as well!

    Yes, DHCP appears to have been the problem. I set a static IP and was able to get back to the GUI and have now successfully set up a wireless network at our new apartment, after a long week of frustration and tears. I've enabled the DHCP server through Tomato again, so do I go back into my computer's network settings and switch it back to how it was before? Sorry if I'm not using the right terminology, you have no idea how new I am to this stuff. Since I'm now working on a wireless connection I hate to go back in and change anything around that might "break" it.

    Thank you so much for all your help, both in answering my specific question and in the tons of useful information I've gathered from this forum over the past several days.
  5. azdps

    azdps LI Guru Member

    Yes you can now change your computer back to how it was before you set a static ip address. Since the dhcp server is on , the router will now be responsible for issuing out ip addresses to whatever device connects to it.
  6. MAJ

    MAJ Serious Server Member

    3 years later, I'm wondering if anyone can help. I'm afraid I did something really dumb that can't be fixed. After successfully setting up our wireless network with this forum's help in August 2012, it worked perfectly until we moved. We are now in a new house, using the same equipment, but I can't get the wireless connection to work. The internet connection works fine when I connect the ethernet cable directly to my laptop so I know the problem isn't there and I can't blame this on Comcast.

    I thought that the wireless issues might be the same problem I was having in 2012 with the static IP/DHCP settings. At that point I could still access the Tomato GUI page at and I changed some of the settings there. Unfortunately since I can't access the GUI anymore I cannot tell you exactly what I changed! I am pretty sure that under Basic -> Network I changed the Router IP address / Subnet Mask / Static DNS numbers to the ones in this article: I am also fairly sure I un-checked the boxes for DHCP server AND for wireless. I'm pretty sure these were all stupid things to do. After reading a bunch more and trying to figure out what I did wrong, I think those were numbers I was supposed to change on my laptop, not on the router.

    Is there any way to fix this? How can I figure out how to get access to the GUI again? I am afraid that I'm just going to have to buy a new router and start over.

    Thank you.
  7. fonos

    fonos Serious Server Member

    If it's simply a configuration problem, you won't need to buy a new router.

    1. If wireless is hosed, you can connect via a cable. Maybe DHCP will assign you an IP address. (Or maybe not...)
    2. If no joy with 1, Try to recall what address/subnet mask you used for the router. Give your client PC an address in the same subnet range and tell it what you think was the router's IP address.
    3. If you're pretty sure you are on the correct subnet you could try ping -b 192.168.x.255 where 'x' is the appropriate network number. (Apologies if this doesn't work in Windows but if not, I have a feeling you might need "-t" instead of "-b".) Let it run for a minute or so, then ctrl-C it. Then run arp -a to see all (pingable) devices on the local network. Of course, you might have disabled ping response in the router's firewall ;)
    4. Repeat 3 but cycle through possible network numbers.
    5. If all fails, you can reset your router.

    It's probably not comprehensive. Perhaps someone else can come up with some other cool methods.
  8. Monk E. Boy

    Monk E. Boy Network Guru Member

    Yeah, if you can't figure out what IP is assigned to the router, resetting your router is probably your best bet. You'll have to walk through setting it up again like it was a fresh router, but at least it'll work.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice