I have found a potentia issue with 2.6.2 that I haven been able to repeat on 3 virgin Force 180s.
Steps to reproduce the issue:
- Take brand new Force 180 out of box
- Log in and upgrade to 2.6.2
- Change radio settings and system settings (with a reboot after each save)
- Change network settings to Static IP in my private range: 10.10.10.x
- Radio reboots and webpage redirects me to 10.10.10.x (I change my computer subnet to match)
- Radio login fails to load
I can clean cache, try different browsers, reboot the radio, reboot my comptuer. I can never get a login page. I can ping the new IP address of the radio but no WWW. If I try the 169.254.1.2 address, it gets me the login page and when I enter admin/admin (which I never changed), it hangs forever.
Next step is to factory reset the radio with the reset button. This allows me to access it via 192.168.0.2 and all seems to work fine up until I put the network in 10.10.10.x. Then this problem repeats. I have had it happen on all three brand new Force 180's.
To prove I am not loosing my mind, I factory reset one of these failed Force 180s and took it back to 2.6.1 and repeated the above programming steps. It works perfectly.
If I put 2.6.2 on a brand new radio and then upload a known good configuration file (with the 10.10.10.x network assigned), I get the same behavior of not being able to access the web interface of the radio after it reboots.
I can't get a radio to prgram from a factory state with 2.6.2. Maybe there is an issue with the software not liking my private subnet since I'm sure others out there have been successful in using 2.6.2 on a new radio...
Also, not nearly as big of an issue but 2.6.2 on an un-configured radio does not auto populate the cnMaestro URL (cloud.cambiumnetworks.com). Not a big deal but it used to auto fill that.