> However when I try to use the radius for the > captive portal auth I get an error on the client that says invalid login > or password. However I see that the user is accepted in the radius debug: >
authentication::radius is meant to authenticate a user on another RADIUS server (an existing source for authentication). It makes little sense to use it locally you should use authentication::local instead which would be way lighter. Now, lets say that you do have a use case for a locally hosted authentication source in FreeRADIUS then you should create a separate "site" (FreeRADIUS' virtual-servers) for it without the PacketFence perl module and trying to avoid the PacketFence's /etc/raddb/users entry. Why? Because PacketFence always accepts non-EAP connections by design so it's able to re-direct to the captive portal (you need _some_ network to reach a captive portal). But if you intend to use the FreeRADIUS site for authentication then it should be a proper CHAP (or is it PAP?) FreeRADIUS server. I hope I made things clearer. Cheers! -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
