Re: (RADIATOR) NAS Identitier as domain
Hugh Irvine [EMAIL PROTECTED] recently suggested: It might be simpler to set up your Client clauses with DNS names, then use Client-Id in your accounting records. # Configure Client clause with DNS name, something like this: Client NAS.city.indo.net.id /Client I've often considered doing this, but I'm not sure that I like the idea of performing a DNS lookup on each packet. Does Radiator cache DNS info? If so, does it 1) Do any lookups when reading the config file? 2) Time out DNS caches as appropriate? 3) Flush DNS caches on a kill -HUP? Thanks. --phil "All my life, I always wanted to be somebody. Now I see that I should have been more specific." === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) NAS Identitier as domain
Hi Phil - On Sat, 20 Nov 1999, Phil Freed wrote: Hugh Irvine [EMAIL PROTECTED] recently suggested: It might be simpler to set up your Client clauses with DNS names, then use Client-Id in your accounting records. # Configure Client clause with DNS name, something like this: Client NAS.city.indo.net.id /Client I've often considered doing this, but I'm not sure that I like the idea of performing a DNS lookup on each packet. Does Radiator cache DNS info? Not exactly. The Clients that are listed in the configuration file are instantiated at run time, and the lookups are done then. If so, does it 1) Do any lookups when reading the config file? Yes. 2) Time out DNS caches as appropriate? No. 3) Flush DNS caches on a kill -HUP? Yes - see above, the existing Clients are purged, the configuration file is re-read and the Clients are re-instantiated. hth Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, NT, Rhapsody === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) NAS Identitier as domain
Hello Arif -
On Thu, 18 Nov 1999, Yang Tercepat wrote:
Hi,
On accounting table, there is nasidentifier fields which is
default contain IP address of the client port. But since all
user can see all their connection log coming from, we like
to represent NAS Identifier as domainname because our port
is distributed in many city. Is it possible to add a little
source or add configuration on Radiator Server to resolve from
IP to domainname?
Subsequent to my mail of a moment ago, there is a slight problem with my
suggestion, and that is the Client-Id attribute is not actually in the packet.
Therefore you will also need to add a PreHandlerHook to add it.
# Configure Client clause with DNS name, something like this:
Client NAS.city.indo.net.id
PreHandlerHook sub { my $p = ${$_[0]}; \
$p-add_attr('ClientName', $p-{Client}-{Name});}
/Client
Handler ...
AuthBy SQL
AccountingTable
AcctColumnDef NASIDENTIFIER, ClientName
/AuthBy
/Handler
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
