I’ve been running my Alta Labs setup now for a couple of weeks and it’s been great so far. Setup at the moment consists of a Route10, AP6, and a local controller running via a Docker container in Ubuntu. When the AP6 first came online it grabbed a DHCP address which I then changed to a static IP (outside of the DHCP range) but when I look at the configured static IP it’s the same IP that it first received from the DHCP range, not the one I had configured. Whenever I try and change it to the preferred static IP it seems to accept the change but it doesn’t update on the Network page and if I refresh the page the old static IP config comes back up. It’s as if it’s not taking the new static IP configuration. Controller is on 1.3r and the AP is on 2.2e. Is this a bug or just something that I’m missing to get the change to stick. Thanks!
I just checked mine, still has the static IP I set on it last night. AP6 Pro.
Welcome to the community @trinamer!
Have you confirmed that the AP is still available via ping at the old static IP, and not on the new one? Typically this is a browser caching issue. Ping probably is the quickest and most absolute test, but you can also try refreshing without cache, or private/incognito mode to verify that.
Thanks for the welcome 
. I did verify via ping that the AP still is on the old static address and not the new one. I ran a continuous ping also to see if perhaps it at first changed and then reverted back to the previous IP but I didn’t see any lost packets when I attempted to change the IP. But now that you mention it, I’m going to try a different browser to change the IP.
No problem!
Cool, thanks for confirming. I don’t like assuming those types of things. We officially support Chrome, but most major browsers should work just fine. Only current known issue is that a current/recent build of Vivaldi on Linux (not macOS and Windows), seems to exhibit some odd/unexpected behaviour so I can’t recommend it at this time, like broken configs, etc.
Sounds good, please let us know the outcome either way.
Ah good to know. I haven’t used Vivaldi in good while and mainly use Firefox.
So using a different browser (Edge) didn’t make a difference but when I attempted to change the IP I noticed that the load icon changed color a bit so it looked as if the AP was trying to do something. I then thought to use a different IP outside of the DHCP range and that worked! After that I was curious so attempted to change the IP to my originally preferred IP and now that worked too. It’s so odd but I’m happy now to have the preferred IP assigned to the AP. So in summary:
x.x.x.113 > x.x.x.25 = didn’t work in either Firefox or Edge
x.x.x.113 > x.x.x.35 = worked
x.x.x.35 > x.x.x.25 = worked
Thanks for the quick responses!
The only actual known issue is it was generating broken WireGuard user configs on export. But I mentioned it in the very slight chance you were using it as it was the only known browser with a known issue off-hand.
Agreed that is both odd and unexpected. Glad to hear it’s sorted.
No problem!