> On Jul 11, 2017, at 14:24, Jason 'XenoPhage' Frisvold via PacketFence-users
> <[email protected]> wrote:
>
> So, if I disable the autoregistration for the profile (config ->
> connection profiles -> default), I get a captive portal. But, that then
> "breaks" 802.1x in that even with 802.1x enabled, I still get the portal.
>
> So I'm still missing something. We're looking for the following order
> or preference :
>
> 802.1x
> MAB (manually added nodes)
> Captive Portal
>
> How do I accomplish this?
Create a different portal per connection type.
E.g. One dot1x profile for which autoregistration is enabled, one MAC
authentication for which it isn't.
That should do it.
I try to use the default portal as little as possible, and create more granular
profiles that allow a different set of authorization sources etc.
It's also easier to maintain over time, as when adding something new (a new
SSID for instance) you can define a separate profile for it and not have to
modify the default which is already handling production traffic for your
existing network.
Regards,
--
Louis Munro
[email protected] <mailto:[email protected]> :: www.inverse.ca
<http://www.inverse.ca/>
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu/>) and
PacketFence (www.packetfence.org <http://www.packetfence.org/>)
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
