Re: Conditionally passing custom attributes
Chad Lensert wrote: This is the version that is supplied with SuSE and needs to be managed via their patch channel, so I am required to use this version. No, you're not. You can upgrade. The server comes with files that lets you build a Suse RPM. There is *no technical reason* why you can't upgrade. The only reasons are politics, and personal choice. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Conditionally passing custom attributes
On 17/05/12 15:25, Jeremy Guthrie wrote: At this point we have got this one product we need to see if we can get working. If you are looking for more information or other things you'd ask we do before posting to the list, we'd be happy to comply but I cannot afford self-packaging freeradius at this point. :( Perhaps you could try reproducing the problem on a development system running 2.1.12? OpenSUSE 12 has FreeRADIUS 2.1.12 IIRC. If the problem isn't there, you know that 2.1.1 is the culprit. If the problem persists, you are probably doing something wrong, and you can ask for help here without people ignoring you. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Conditionally passing custom attributes
Why? 2.1.1 was released almost 4 years ago. This is the version that is supplied with SuSE and needs to be managed via their patch channel, so I am required to use this version. Well, it should work. It works for me in my testing. I'll continue to troubleshoot. I wasn't sure if there was some global config option or something obvious I might be missing or a bug in this version. smime.p7s Description: S/MIME cryptographic signature - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Conditionally passing custom attributes
Chad Lensert wrote: freeradius-server-utils-2.1.1-7.7.19.77 freeradius-server-libs-2.1.1-7.7.19.77 freeradius-server-2.1.1-7.10.1 Why? 2.1.1 was released almost 4 years ago. Greetings all. I am trying to pass a list of custom attributes based on the information in the radius request. Originally, I tried matching on NAS-IP-Address as noted below, but it looks like I can also match on Client-IP-Address, which I would prefer. The issue I am having is that I don't see radius matching the right entry in the users file and returning specific custom attributes. I can't determine why it is choosing the last user entry in the users file. Here is an example of the users file. I expect the information from the request to match the first entry for user chad. Well, it should work. It works for me in my testing. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
