I think you missed the question then. This is a single username, but the return being selective based on NAS. For example: Radreply will reply with an IP of 1.2.0.1 if NAS=1 else it will respond with IP of 1.1.0.1 if NAS=2, else it will respond with an IP of 1.3.0.1 The radcheck would be at the wrong phase to do this. -----Original Message----- From: freeradius-users-bounces+john.mylchreest=ioko.com@lists.freeradius.org [mailto:freeradius-users-bounces+john.mylchreest=ioko.com@lists.freeradius.org] On Behalf Of Alan DeKok Sent: 29 March 2006 18:56 To: FreeRadius users mailing list Subject: Re: Different user attributes based on NAS-IP-Address?AlsoSuffixwildcards available? "John Mylchreest" <John.Mylchreest@ioko.com> wrote:

Can you give me an example in SQL please of how I might implement it using this fashion?

You put the attribute name, operator, and value into SQL.

Is it not just a case of if it passes radcheck, then it will respond with radreply?

Yes. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html Communications on or through ioko's computer systems may be monitored or recorded to secure effective system operation and for other lawful purposes. Unless otherwise agreed expressly in writing, this communication is to be treated as confidential and the information in it may not be used or disclosed except for the purpose for which it has been sent. If you have reason to believe that you are not the intended recipient of this communication, please contact the sender immediately. No employee is authorised to conclude any binding agreement on behalf of ioko with another party by e-mail without prior express written confirmation. ioko365 Ltd. VAT reg 656 2443 31. Reg no 3048367. All rights reserved.