We now have rolled out 3.6.0 RC4 to several client sites without any issues, all sites were done from within InControl2 and these sites are fully managed for the Wi-Fi from InControl2, most have multiple VLANs aligned to differing SSIDs and some have Captive Portals, we are not using any local AP controllers at these sites.
If we find any issues arising, we will let you know.
Happy to Help,
I upgraded my AP One Enterprise APs, pushing the firmware from a Balance One Core running 7.0.2. APs upgraded without issue and clients are starting to reconnect. I’ll post updates as I get a sense for how they are doing.
@Lewis_Kong can you confirm that AP Controller Firmware Pack (1153.fwb) is the correct one to use with AP one Rugged?
Any ideas why this did not work reliably for us?
Yes, 1153.fwb is the correct firmware pack for AP Controller. Could you please PM me your AP Controller serial number and turn on the RA? I will check the root cause.
The issue mentioned by @adeebag is caused by improper activation of SSID Access Control Setting.
RC5 is ready to fix this activation bug.
The firmware is here and the AP Controller firmware pack is 1154.fwb.
If no significant bug is reported in the coming week, RC5 will be G.A. soon.
I PM’ed some issues I still had with RC4. Reverted to RC2. Perhaps it’s just me and my setup if nobody else is seeing connectivity issues with IoT devices.
Thanks – I can confirm this worked.
Unfortunately, we have confirmed a firmware bug in RC4 and RC5 which causes AP running out of resource gradually. That bug could be the reason why Ryan reported his IoT devices suffered after running RC4 for several days.
I will download 1155 and apply it today.
My B1 Core is claiming that firmware pack is invalid.
Please try to remove an unused firmware pack from AP Controller Toolbox.
That should be the AP Controller front end bug which displays an incorrect error message when firmware pack exceed limit.
That did the trick. Thanks for the prompt response Lewis. 1155 is pushing out to my AP One Es now.
Unfortunately again… we found RC6 may get incorrect client IP addresses in some occasions. As incorrect client IP can affect captive portal functionality, we decide to release another RC7 before G.A.
Just applied RC7.
Running the latest RC, I see the 5GHz clients show up as all using 6Mb/sec Tx rate (from the client list). I am guessing this is a UI bug, not an accurate reading of the PHY rate?
3.6.0 RC7 1793 does not fix the problem. After 5 days of up time the APO-RUG units stop routing packets completely, but the performance is lost much sooner. A reboot fixes the problem temporarily. You have a memory leak. Seems to be a running theme in many of the bug reports. Suggest you find and fix it.
Installed AP Controller Firmware Pack is 1156 and now the VLAN’s are forced to 0: Untagged and getting pushed through the .0 DHCP which is for management stuff only.
Balance 305 HW1(single) and HW2(HA)
11 AC One Mini’s
@Lewis_Kong any updates? when do you expect the GA to be released?
Does the issue still happen? Could you please open a support ticket?
We cannot produce your issue in our lab which have been running for more than 2 weeks with 15 active Wi-Fi clients.
I am not sure about what problems you are facing.
Could you please open a support ticket or PM me more information?
We are prepare related document for 3.6.0GA. Please stay tuned.
No ticket is needed as we have reverted the firmware pack on the Routers for the time being.
We are having issues with the AP’s dropping users on the current release firmware.
However, this is what was happening for other users who might use the beta firmware.
When the beta firmware 3.6.0 RC7 (1156 Firmware Pack) was installed, all users that were handed DHCP under ANY SSID were handed out un-tagged IP addresses. e.g. 192.168.0.200 instead of 192.168.40.200
When we reverted to Firmware Pack 1145 and the DHCP started working correctly.
I will test on the one I have at the house later and if I can re-create the issue I will let you know.