Note: re-adding the list, please keep conversations public for the benefit of others
On 06/05/2012 10:19 AM, Maxime Pioc wrote: > Hi, > > After reflection, > I have created an external dhcp server but it always have a problem. > it seems ( in 802.1X authentication mode) that the client was not placed > in the regular vlan (vlan 20). > because when I start FR in debug mode, the client is authorized > but i don't see this lines (like in MAB mode) : > - Tunnel-Type = VLAN > - Tunnel-Medium-Type = 802 > - Tunnel-Private-Group-ID = VLAN ID > > and if I configure the exernal DHCP server for give ip in an unused > vlan, it works. > > With MAB authentication, it works too with the external dhcp server. > > So, is there a way to force clients to be placed in the correct VLAN in > 802.1X mode ?? This is the way it works by default. It means there is something broken in the client configuration or the server configuration. What type of EAP is your client doing? EAP-TLS/PEAP-MSCHAPv2? What's in your /etc/raddb/eap.conf and /etc/raddb/sites-enabled/packetfence and packetfence-tunnel? Cheers! -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
