Hi Colin,
Thanks for the info. This is pretty good news, so I went ahead and upgraded the clusters to 8.4.0.0.
The RAP could connect successfully before the upgrade, but now I get some new issues. It comes up, stays online for a couple of minutes and I see my SSIDs.
But after a couple of minutes, the RAP is shown to be down on the controller, and the WLAN LEDs change from green to amber. Similar to what you get when you dont add any vaps to the AP group. And it just sits there like that, not rebooting or anything.
The page you linked to is interesting, as I believe NAT may have something do do with it.
The incoming connection from the rap through the firewall is actually SNATted to the interface IP towards the controllers on the firewall. The reason is that the default route does not go back to the firewall, and this is a bit of a workaround. But the consequence is that the outer IP of the RAP changes to the interface IP of the firewall.
Would this cause an issue? And if so, is there a workaround?