Hello Mickael, Put a production VLAN id in the registration role under Configuration > Policy and access control > Switches > Switch IP > Role > Registration.
So basically you are returning an access to anyone that is not registered in PF. It bypasses the captive portal for registration. You could alternatively do an auto reg on the connection portal as Enrique mentioned but the devices would have no role so no access on a particular VLAN dynamically. You could do it with a VLAN filter (If radius mac authentication from switch XX then Status = registered and Role = RoleXX). Thanks, Ludovic Zammit [email protected] <mailto:[email protected]> :: +1.514.447.4918 (x145) :: www.inverse.ca <http://www.inverse.ca/> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu <http://www.sogo.nu/>) and PacketFence (http://packetfence.org <http://packetfence.org/>) > On Nov 6, 2020, at 8:52 PM, Mickael BOUBALA via PacketFence-users > <[email protected]> wrote: > > Hi, > > I'm trying to do a Wireless 802.1X and MAC authentication without using > captive portal. > > By default we allow every query to be redirected and reach PacketFence for > the captive portal operation. > > So the captive portal is constantly launched on the registration VLAN. > How to tell Packetfence to not set the captive portal on a VLAN or a network > interface ? > > Network infrastructure: > PacketFence version: 10.1.0 > PacketFence has 2 network interfaces, > 2 VLAN: > Management VLAN, > Registration VLAN: where PacketFence provides DHCP services and DNS > black-holing services. There is no portal daemon running on registration VLAN. > Registration VLAN is directly connected on PacketFence. > > > Regards, > Mickael > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
