Hello Eugene, The answer is in your logs.
grep MAC_ADDRESS /usr/local/pf/logs/packetfence.log 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 Oct 29, 2020, at 3:15 PM, ypefti--- via PacketFence-users > <[email protected]> wrote: > > Folks, > Can someone help me identify what I’m missing. > My authentication session goes through but the endpoint that connects to WAP > (Unifi) never gets an IP address. > I investigated it and see that RADIUS assigns the wrong VLAN to the > connection. > This is what I see in the live session log > > Oct 29 12:04:29 packetfence auth[1201]: [mac:18:81:0e:7c:3c:ed] Accepted > user: it.tech <http://it.tech/> and returned VLAN 2 > > But my authentication source has a rule with an action to set the Role Staff > which is defined with a specific VLAN 10 > VLAN 2 on the contrary is assigned to a registration role which I’m not using > at the moment. > My short term goal is dot1x WiFi authentication with RADIUS assigned VLAN. > > Eugene > > _______________________________________________ > PacketFence-users mailing list > [email protected] > <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/packetfence-users > <https://lists.sourceforge.net/lists/listinfo/packetfence-users>
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
