Our latest Control release combines new functionality with targeted refinements to give you a smarter, smoother, and more reliable management experience.
(Cloud only) Add Floor Planner.
AP6W: Enable IGMP snooping if any VLANS have it enabled.
Add DHCP-only and VLAN filter to Device List.
Add DHCP lease table to VLAN Window.
VLAN/WAN Windows: Allow expansion.
Resolve issue where Router config may potentially be lost when being re-added to a site.
Persistent Logs: Resolve minor UI issues.
Switch Ports: Show correct manual link speed options.
Map: Show WAN-side devices to the left of Route10.
SSID: Resolve issue where PMF could not be disabled
Add site type.
Various statistics improvements.
This update is being rolled out now. You can manually initiate the upgrade if you’d like, or it will automatically update overnight. Here is the full running changelog:
If you have any questions let us know, and as usual if you notice anything please feel free to reply here, or create a new topic, including the details of the issue encountered. Thanks!
Thanks for the update @Alta-MikeD ! A quick note on the map; appreciate it that it now shows WAN side devices on the left, although on one site I have WAN2 configured as a LAN port and the map is showing those devices to the left of the Route10 as well:
Seaching around the forum I spotted a couple of references to “dirty” being used for development versions of firmware. If it seems to be working and running properly, I’d guess that tag didn’t get removed before the firmware was released. Or maybe the last development version was accidentally released instead of the “final” version. I suspect @Alta-Jeff might be able to shed some light on that further
Full explanation: “Dirty” typically means that the code-base was not in pristine shape when the package was released. In this case, it was code checked into the repository that actually changed the checked out code during the build, and we did miss that, but we will correct this in an upcoming release.
The APs will track IP addresses of each station associated, and in this case, you have a single station that is using more than 5 IP address. This is definitely a corner-case, but it just means that the AP isn’t tracking more than the original 5 it saw.
Ok. Who do I need to speak to so that I can revert both the Control and AP’s back to their previous revisions? I’m through with being the only one here consistently experiencing “corner cases” for such a simplified configuration.
Reach out to support and they will be happy to help you downgrade. The IP address tracking feature you reference above has been in the AP firmware since the beginning, however. We are definitely curious what WiFi device you have that claims over 5 IP addresses to see if there is something we are missing…
We aren’t seeing anything like that anywhere - from what we can see, those devices are using several different IP addresses over the course of a short period of time which is indicative of a larger problem. Please invite me if you want me to take a look.
I assure you it’s not wiping any user accounts. I can guide you through connecting to the postgres database via ssh if you want to confirm.
However, you are very likely misconfiguring your controller by changing the allowed ports to something that does not match the environment you are connecting with. This is certainly an advanced topic, and I’m happy to take a look at your specific installation to see what ports should and shouldn’t be configured.
