I have recently put packetfence into production using the vlan enforcement method. Despite having to push it into production quickly it has performance has been great. The documentation has been great and has solved all my issues except one.
I am using radius to register nodes and can do it with either username or domain\username without issues on wired or wireless. I have a secure wireless network so I modified proxy.conf and added my external radius servers in a new realm. I can now point the wireless controller secure wlan at Packetfence and have wpa2-enterprise working if I use username@domain format. However domain\username fails. In reading freeradius and packetfence groups I see that ntdomain is enabled so realm/username, username%realm, realm\username should also work but do not. I have checked the sites-available and site-enabled for ntdomain issues and it seems to match the documentation. If somebody might be able to point me in the right direction or the right freeradius incantation I would appreciate it. Thanks Sean ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
