One of our other software vendors is sending out weekly nag emails about this
Microsoft change, because it will break their Active Directory integration:
https://support.microsoft.com/en-us/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirement-for-windows
Is this something that PF
With a disclaimer that our PacketFence install is bordering on grossly
obsolete, I'm sending a heads-up for anyone still using Meru/Fortinet wireless
equipment.
Their controller firmware version 8.4.3 has either a bug or feature where they
are no longer sending the RADIUS Calling-Station-ID to
Considering that Meru as a company is 404 and the brain-drain following
the Fortinet acquisition essentially put the whole product line into
life support mode in terms of customer support, I would not hold my
breath waiting for someone to fix any Meru problems in PF.
We are running PF 5.x with
It sounds like you may want to use a simple inline deployment on a
dedicated guest SSID, and any AP that you can buy should work in this
configuration...
-Arthur
-
Arthur Emerson III Email:
What we do with PF 5.x is have a limit (N) on the number of devices that
guest users can register...and then make sure that there are N+1 bogus
MAC addresses registered/active for that user account. Anyone who tries
to register another device is told that they already have too many
devices