On May 27, 2015, at 12:08 , Sohaib Afourid <[email protected]> wrote:
> but right now I can't even get/ don't clearly understand how packetfence
> works with 802.1x and a captive portal, i've been asking for an explanation
> scenario but no one has provided it yet.
> thank you.
To be honest, a captive portal is mostly redundant if you are using 802.1x.
I mean, you already authenticated and provided credentials during the RADIUS
auth.
But still, you can have your cake and eat it if you must.
Your users will authenticate using 802.1x, be sent to a registration VLAN where
dns will redirect to the captive portal.
Once they authenticate to the portal they can be redirected to another VLAN.
As I said, it’s redundant. Some people actually use the captive portal just to
force people to accept terms of service.
--
Louis Munro
[email protected] :: www.inverse.ca
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
