Hello Tom,
launch radius in debug mode to see what happen.
Regards
Fabrice
Le 2013-06-27 14:25, Tom Fischer a écrit :
802.1x device identifier
I have PFZEN 4.0.1 running in a test environment. I have PF
authenticating Windows wireless workstations via 802.1x with VLAN
enforcement. The connections are working fine, but the
identifier/owner is always logged as admin. Radius appears to be
sending the username, but I don't see PF picking it up. Is there
something I need to change?
Radius log
Thu Jun 27 12:09:41 2013 : Auth: Login OK: [DD\\myname] (from client
a.b.c.dport 8551 cli 0090.4b78.ffffvia TLS tunnel)
Thu Jun 27 12:09:43 2013 : Auth: rlm_perl: Returning vlan 1 to request
from 00:90:4b:78:92:70 port 8551
Thu Jun 27 12:09:43 2013 : Auth: Login OK: [DD\\myname] (from client
a.b.c.dport 8551 cli 0090.4b78.ffff)
Packetfence log
Jun 27 12:09:42 pf::WebAPI(7869) INFO: handling radius autz request:
from switch_ip => a.b.c.d, connection_type => Wireless-802.11-EAP mac
=> 00:90:4b:78:ff:ff, port => 8551, username => (pf::radius::authorize)
Jun 27 12:09:42 pf::WebAPI(7869) INFO: node 00:90:4b:78:ff:ffdoes not
yet exist in database. Adding it now (pf::radius::authorize)
Jun 27 12:09:43 pf::WebAPI(7869) INFO: MAC: 00:90:4b:78:ff:ff, PID:
admin, Status: reg. Returned VLAN: 1 (pf::vlan::fetchVlanForNode)
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
