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

Bug with IP on HyperWRT with Tofu12

Discussion in 'HyperWRT Firmware' started by Nimdae, Jan 13, 2006.

  1. Nimdae

    Nimdae Network Guru Member

    I installed this firmware to attempt to resolve an issue I have with dd-wrt, but it appears I've only run into another issue. My network is on the 192.168.2.0/24 subnet, and has been this way for over a year, so my network is pretty much set this way. When I try to set my router running this firmware to 192.168.2.1, all forms cease to function, as I am given a "Document contains no data" error. I can work around this, but it's either to change my entire network to 192.168.1.0/24, or configure everythign I need on this router, then change its IP and pray I never have to configure it again, else I have to reset.

    I have reproduced this problem and verified that it is this configuration that appears to cause it.

    Time to try another firmware.
     
  2. Thibor

    Thibor Super Moderator Staff Member Member

    i hate to ask this, as it's pretty obvious but, did you change your ip address from the 1.x range to the 2.x range?
     
  3. Nimdae

    Nimdae Network Guru Member

    Bah, bricked my router, had to reset to linksys firmware. This is when I discovered this bug appears in the latest linksys firmware as well. I guess I'm gonna just have to go with dd-wrt v22 for now just to have a stable network.
     
  4. Nimdae

    Nimdae Network Guru Member

    You know, I totally missed your reply, you posted while I was on the edit screen, heh.

    Yes, I'm changing it to the 192.168.2.x subnet. I got my router stable by switching back to dd-wrt v22, and it has always worked fine on that subnet.

    One thing I've noticed in all the firmwares I've used is you can't do anything beyond a /24 (255.255.255.0) subnet. While it may seem absurd, I think it'd be kinda nice if I could use any subnet mask of my choice, since for troubleshooting, while being on 192.168.2.x, I can temporarily change to /23 (255.255.254.0) to reach the 192.168.1.x subnet on a remote reset (yes, I'm crazy enough to do that, but not on the router :p, I have another linksys device acting up now).

    There's a method to my madness...that's pretty much how I'll explain my network config :p
     

Share This Page