All, I am configuring packetfence 3.0.2 for the first time in a lab. So far I've managed to get "most" of it working with one exception. I have a windows 7 wireless client connecting via 802.1x authenticating to AD through the freeradius server that came with packetfence. My wireless controller is a MSM710 and my AP is a MSM422. I am proxying the radius request through the MSM710 and I am getting associated with the wireless network. Once in the registration vlan I can enter my AD credentials and get authenticated. One thing I am noticing is that after all this happens packetfence want to "talk" directly to the AP (MSM422) instead of the wirelesses controller (MSM710) to update the vlan from registration to normal. The NAS-IP that is being sent in the tunneled peap communications are that of the access point and not the controller (is this normal?). If I can get the controller's IP sent as the NAS-IP will this solve my issue? Thanks
------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
