09-05-2017 01:50 PM
So I had 2 AF5 luckily not an active link, i upgraded to 4.0 then went from DHCP to a static ip i knew was available on this network and now they are both no where to be found. Has this happened to anyone else yet?
09-05-2017 02:11 PM
So... the 4.0 upgrade worked and the units dhcp-ed an address. You then logging into v4.0 and changed the IP, subnet mask, and default router to known good values and now you can't contact the units?
09-05-2017 03:11 PM
Also, what did you upgrade from? If it was one of the early beta releases (beta1,2,3,4,5) you will likely need to factory default your radio. See the beta channel for more info...
10-27-2017 07:09 PM
I had the same issue. I was on 3.2.3 and upgraded to 4.01. Then changed the units from DHCP to Static. The IP address stays in the unit but it is loosing the gateway. If i ssh into the unit and do an Ip r a default via statement i am able to access the units again. But updating and saving the config still prevents me from saving the actual static entry. Any suggestions other than going back to older firmware?
10-28-2017 06:12 AM
This is an issue with v4.0 and v4.0.1. I hope to release a v4.0.2 to fix this and an issue with Carrier Drop pulse mode in the next two weeks. Until then, your options are:
- Downgrade to 3.2.3 and reconfigure your static IP
- Live with DHCP
- #1 and then upgrade to 4.0.1, and, don't change the IP addressing after the upgrade
I know this is less than ideal, but, this was missed both in our testing and in the very long v4.0 beta cycle.