Le 07/10/2014 18:40, Fabrice DURAND a écrit : > Ok so your rule is correct. > > Did you added custom code in the vlan/custom.pm file ? Yes, I was previously using autoregister, but I comment it on back and replaced it by vlan_filter, so now I'm using the original file.
> When the device connect on the secure SSID, what is the portal profile > it will hit and in this portal profile do you have your se3_utilisateurs > authentication source ? I haven't configured it, as with autoregistration for 802.1x Secure SSID, I guessed that 802.1x users would never be put on registration vlan and be caught by captive portal. Did I missed something ? Is portal configuration used for already registered devices and users too ? Denis ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
