Hi all,
I've installed a ZEN 7.2 VM to learn and investigate implementation at my
work and all is going pretty well expect for this issue I can't work out.
If I set the wireless client to connect as PEAP-MSCHAPv2 then it is
correctly showing as Wireless-802.11-EAP. Because of this the connection
profile I have set to do AutoReg on 802.1x doesn't work if using EAP-TTLS.
Obviously I can just use PEAP-MSCHAPv2 and disable EAP-TTLS but I'd like to
work out why this oddity is happening.
The Following is from packetfence.log
EAP-TTLS-PAP
Aug 22 08:37:24 PacketFence-ZEN packetfence_httpd.aaa: httpd.aaa(2823)
INFO: [mac:e4:42:a6:02:18:59] handling radius autz request: from switch_ip
=> (172.17.0.10), connection_type => Wireless-802.11-NoEAP,switch_mac =>
(34:db:fd:43:5d:70), mac => [e4:42:a6:02:18:59], port => 13, username =>
"mattmunro", ssid => shc-test-network (pf::radius::authorize)
PEAP-MSCHAPv2
Aug 22 08:42:01 PacketFence-ZEN packetfence_httpd.aaa: httpd.aaa(2823)
INFO: [mac:e4:42:a6:02:18:59] handling radius autz request: from switch_ip
=> (172.17.0.10), connection_type => Wireless-802.11-EAP,switch_mac =>
(34:db:fd:43:5d:70), mac => [e4:42:a6:02:18:59], port => 13, username =>
"mattmunro", ssid => shc-test-network (pf::radius::authorize)
Only changes I've made to the freeradius conf is adding the LDAP module
conf for eDirectory and uncommenting the ldap cache password example and
the authorize section in /usr/local/pf/conf/radiusd/packetfence-tunnel
Regards
Matt
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
