"John Mylchreest" <[EMAIL PROTECTED]> wrote:
> 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
I'm not
the wrong phase to do this.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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" <[EMAIL PROTECTED]> 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.
18:14
To: FreeRadius users mailing list
Subject: Re: Different user attributes based on NAS-IP-Address?
AlsoSuffixwildcards available?
"John Mylchreest" <[EMAIL PROTECTED]> wrote:
> When you mean key off the NAS-IP-Address, do you mean like I
> suggested in my previous
> The NAS-IP-Address can be used as a check item, just like anything
> else.
>
> DEFAULT NAS-IP-Address == 1.2.3.4
> Reply-Message = "Hello you guy from 1.2.3.4"
>
> The same config can be applied to SQL.
But not with the current dialup_admin IIRC you have to put it in
manually not?
J
How would they work in this case?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan De
Graeve
Sent: 27 March 2006 19:28
To: FreeRadius users mailing list
Subject: RE: Different user attributes based on
NAS-IP-Address?AlsoSuffixwildcards available
: Different user attributes based on NAS-IP-Address?
> AlsoSuffixwildcards available?
>
> Funnily enough, I asked the very same thing recently. We do it quite
> crudely at the moment, but it works.
>
> We add an nshortname field to radreply/anything else necessary, and i
7 matches
Mail list logo