Yes indeed, I changed the default entries of the users.conf because freeradius wasn't replying with the attributes so I tried many tricks in order to improve this but I never managed to get those attributes in Access-Accept packets... I also modified the ldap section of radiusd.conf but this one is working fine so I guess I wont have to change this anymore. I really think the problem comes from this users.conf file but I really can't figure out why the modifications I bring to this file don't affect radius behavior. Are there options I'm missing in other conf files maybe ? tnt@kalik.co.yu wrote:
Default users file has DEFAULT entries for that Service-Type and protocol. Default radiusd.conf uses files. You have changed the defaults and it's not working anymore. In default configuration make changes only to the ldap section and leave the rest as it was.
Ivan Kalik Kalik Informatika ISP
Dana 10/12/2007, "Lucien RENAULT" <loupitour@gmail.com> piše:
Hi, I'm running a configuration where a Cisco 1600 router is running a PPPoE server and check user passwords against a freeRadius server running under FreeBSD. This Radius server checks passwords against a LDAP database running on another BSD server. The authentication is working great, the Radius replies with an "Access-Accept" reply to the Cisco router but it seems that the router needs two attributes to accept this reply :
Service-Type = Framed-User, Framed-Protocol = PPP,
So I did the following configuration in users.conf :
DEFAULT Framed-Protocol == PPP Service-Type = Framed-User, Framed-Protocol = PPP, Fall-Through = Yes
But freeradius still replies with no attributes in Access-Accept packet... I read a lot of documentation about this and I'm quite confused since I don't really see any other mean to add attributes to replies...
Any Ideas ?
Thanks - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html