Another solution is to buy a public domain and to authenticate it in
clients.conf.
Can you perhaps ellaborate a little? I wasn't even aware that this would be
possible.
--
Chris.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Another solution is to buy a public domain and to authenticate it in clients.conf.
>From: "Alan DeKok" <[EMAIL PROTECTED]>
>Reply-To: freeradius-users@lists.freeradius.org
>To: freeradius-users@lists.freeradius.org
>Subject: Re: Using NAS-ID in clients.conf
>Date:
Andrew Frazer <[EMAIL PROTECTED]> wrote:
> I have a situation when some of my 'nas's will have dynamic ip address's.
That's always bad.
> However I have lots more than one 'nas', that I want to use. And I want each
> nas to use a different secrect. How can I identify the NAS without usin
I have a situation when some of my 'nas's will have dynamic ip address's.
So, I could use a generalized case to allow my radius server to listen..
something like this.
client 0.0.0.0/0 {
secret = test
-
I guess this would be ok, if I had lots of nas's.
4 matches
Mail list logo
