Changing The Subnet....subnet
Posted 23 January 2012 - 06:27 PM
I feel a little bit lied to by the help desk on this one, so I'm appealing to the masses.
I attempted to change the subnet on one of my hotspots to the 181 instead of the 182. I found all instances of the 182 in the config files under /etc/chilli, and even downloaded a fresh setup.sh which I edited and saved.
Everything went fine until I attempted to log into the hotspot, and well, if you are someone who has the answer to this you already know what happened.
How do I get the hotspot to QUIT looking at 192.168.182.1:3990 from the "Login Here with Valid Access" link? I was told that changing the subnet, while "not recommended", would not impact my NAS's interaction with the radius servers.
Or have I missed something? I'm willing to be embarrassed. I'm not willing to give up on this.
Posted 23 January 2012 - 06:43 PM
This is a useful procedure I found and pasted into here for any of you who have found yourself in a situation where you can't talk to your OpenWRT router because of a situation you've created (like I did):
Unbelievably, OpenWRT WILL NOT go to default settings using a 30-30-30 reset, so you're going to place the router into "Failsafe" mode. This will not destroy your settings, it simply starts the router up on the 192.168.1.0 subnet without the hotspot running.
Set your landline ethernet connection to a static address on the 192.168.1.0 subnet (obviously, anything but '1').
Plug it into your Linksys running OpenWRT.
Plug in the router and wait for the DMZ LED to light up. Then immediately press and hold the
reset button for 2 seconds. If done right the DMZ LED will quickly flash 3 times every second.
/!\ Holding the reset button before the DMZ LED turns on (i.e. when the bootloader is still running)
can reset the NVRAM. Resetting the NVRAM will brick some models.
- Telnet (NOT ssh) to 192.168.1.1
- Set NVRAM variable for hs_type
nvram set hs_type=""
Now reboot your router and connect to it using a dhcp ethernet connection. You should get a root prompt using ssh just like normal and can fix whatever problem you need to.
Posted 23 January 2012 - 09:42 PM
Unbelievably, OpenWRT WILL NOT go to default settings using a 30-30-30 reset, so you're going to place the router into "Failsafe" mode.
Why unbelievably? a 30-30-30 reset is a DD-WRT specific invention/program. Why would you have expected it to work on OpenWRT. Indeed, OpenWRT has the failsave mode. "Unbelievably" DD-WRT has no failsave mode.....
nvram set hs_type=""
Unless if I am very mistaken, nvram is old "White-Russian" OpenWRT. Versions past that (Kamikaze and higher) use the uci tool.
So I suspect this failsafe procedure is only for White-Russian and derivates like HotSpotWRT or CoovaAP. Use newer failsafe for newer versions.
Posted 24 January 2012 - 12:29 AM
Any words of wisdom on the original topic, ie, changing the subnet?
Posted 24 January 2012 - 06:01 AM
Edit: One hint though: Since your are running on something based on a very old OpenWRT, maybe it also has an old coovachilli? Maybe you want to try to install the latest 10.03.1 Backfire OpenWRT? Careful though. you'll have to configure it manually, HSS does not (yet) have an automatic install script ready.
Edited by cybermaus, 24 January 2012 - 08:45 AM.
Posted 24 January 2012 - 01:24 PM
you can update the login and logout URLS in the Control Center under Manage > Locations > click on name > Splash Page Settings > Internal Login/Logout URL Set: Custom,
Internal Login URL: http://192.168.181.1:3990/prelogin
Internal Logout URL: http://192.168.181.1:3990/logoff
Posted 24 January 2012 - 04:13 PM
Thanks Roland. I am duly embarrassed but also grateful for the information. I should have looked closer at the settings on HHS.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users