Re: dyndns.org domain in Clients.conf
Yes i have enabled hostname_lookups but nothing. For VPN...can be an idea but without vpn it's possibile to realize what i need?? ----- Original Message ----- From: "Milan Holub" <holub@thenet.ch> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Friday, May 04, 2007 11:29 AM Subject: Re: dyndns.org domain in Clients.conf
Hi,
just a guess:
Ensure that you have following line radiusd.conf: hostname_lookups = yes
Milan Holub holub (at) thenet (dot) ch
-------------------------------------- TheNet-Internet Services AG, im Bernertechnopark, Morgenstr. 129 CH-3018, Bern, Switzerland 031 998 4333, Fax 031 998 4330 http://www.thenet.ch http://wlan.thenet.ch --------------------------------------
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
AS Alex wrote:
Yes i have enabled hostname_lookups but nothing.
For VPN...can be an idea but without vpn it's possibile to realize what i need??
No. RADIUS clients are identified by IP addresses, not host names. If the IP address changes while the server is running, you must HUP or re-start the server for it to discover that. Configuring clients by hostname is possible, but it's almost always a bad idea. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
On 5/4/07, AS Alex <asblackdevils@gmail.com> wrote:
Yes i have enabled hostname_lookups but nothing.
Hostname lookups are only done at FR startup, so as soon as the ip changes you have a problem :-) Use the Nas identifier attribute. Kind regards, Yves
How i can use nas identifier attribute?? client.conf needs an ip however ?? i'm very confused. ----- Original Message ----- From: YvesDM To: FreeRadius users mailing list Sent: Friday, May 04, 2007 1:21 PM Subject: Re: dyndns.org domain in Clients.conf On 5/4/07, AS Alex <asblackdevils@gmail.com> wrote: Yes i have enabled hostname_lookups but nothing. Hostname lookups are only done at FR startup, so as soon as the ip changes you have a problem :-) Use the Nas identifier attribute. Kind regards, Yves ------------------------------------------------------------------------------ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 5/8/07, alessio <asblackdevils@gmail.com> wrote:
How i can use nas identifier attribute?? client.conf needs an ip however ?? i'm very confused.
In clients.conf use 0.0.0.0/0 and make sure your shared secret is long and strong. Use mysql and add a field 'NASIdentifier' in radacct. In your nas you can specify the nas id normally.(at least in chillispot you can) If you use dialupadmin, specify the nasXX_id: blah to see online users for each nas in dialupadmin. Kind Regards, Yves
Hi! YvesDM wrote:
How i can use nas identifier attribute?? client.conf needs an ip however ?? i'm very confused.
In clients.conf use 0.0.0.0/0 and make sure your shared secret is long and strong.
A small note if you really want to do this: in 2.0, this will only match for the exact address 0.0.0.0, and not for all IP addresses anymore, like it does in 1.x. You can work around this by using two entries, one for 0.0.0.0/1 and one for 128.0.0.0/1. I don't think this is a very good idea anyway (Yes, I do use it myself, but that is for a very nonstandard and non-production setup on an isolated network, not for an internet-connected server.) Gtnx Marcel
On 5/8/07, Marcel.De_Boer@alcatel-lucent.be < Marcel.De_Boer@alcatel-lucent.be> wrote:
Hi!
YvesDM wrote:
How i can use nas identifier attribute?? client.conf needs an ip however ?? i'm very confused.
In clients.conf use 0.0.0.0/0 and make sure your shared secret is long and strong.
A small note if you really want to do this: in 2.0, this will only match for the exact address 0.0.0.0, and not for all IP addresses anymore, like it does in 1.x. You can work around this by using two entries, one for 0.0.0.0/1 and one for 128.0.0.0/1.
I don't think this is a very good idea anyway (Yes, I do use it myself, but that is for a very nonstandard and non-production setup on an isolated network, not for an internet-connected server.)
Gtnx Marcel
Hi Marcel, Tnx for the note about 2.0, I didn't know that. I also didn't look into 2.0so far, maybe it's time to do so. I know 0.0.0.0/0 in clients.conf is not a preferable setup, but many public hotspot setups have nas's with dynamic ip's and as far as I know there is no other solution for this, unless you really go for some advanced scripting like somebody else proposed in this topic. If you have a better solution for this, I will be happy to learn! Kind Regards, Yves
participants (5)
-
Alan DeKok -
alessio -
AS Alex
-
Marcel.De_Boer＠alcatel-lucent.be -
YvesDM