Re: Help to differenciate type of service in a authentication request

	Sergey,

	My problem is that I don't have the NAS list. The telephone company
doesn't give me that. They only send me the IP address from their
proxy-radius. So, I have the list of proxies but I don't have the list
of NASes.

	I can't distinguish between broadband and dialup clients based on
REALM, they all use the same realm for my domain.

	State that, I would say that running two copies of radius on the same
machine would solve my problem, since I have boadband clients
authenticating on port 1645 and dialup clients authenticating on port
1812. Is there any problem that I will face doing that? I've tested
radiusd, and I know that this is possible. Other programs like radwho,
radlast and radzap will work?

	Can you give me the direction on how implement the parameter to check
on wich port of the radius server the request has arrived?

	Thanks in advance,

		Conrado
	
Em Qua, 2007-12-05 às 18:28 +0200, Sergey Poznyakoff escreveu:
> =?ISO-8859-1?Q?Lu=EDs?= Conrado Andrade <[email protected]> ha escrit:
> 
> > 	I've configured gnu-radius to use mysql authentication and used thean
> > NAS-ip-address distinguish between broadband and dialup. This is a
> > problem to me since I have to create a list of all NASes that each
> > resource have.
> 
> It is not necessary, there are at least two ways to avoid it:
> 
> 1. Both raddb/naslist and raddb/clients files allow to specify hosts
> using CIDR notation, e.g.:
> 
> 10.10.0.0/24                    nas-1   as5600  community=public
> 10.10.10.1/255.255.255.224      nas-2   true
> 
> 2. Both files allow to use DEFAULT keyword, which will match any NAS not
> otherwise specified in the file.
> 
> > 	1- Is there a authentication parameter that indicates from wich proxy
> > IP the request arrived?
> 
> The Realm-Name attribute is added to each request *sent* to a remote
> proxy. Proxy replies carry the Proxy-Replied=1 A/V pair. Proxy requests,
> however, are not marked with any special attribute.
>  
> > 	2- From historic reasons, DialUP radius request arrives at port 1812
> > and broadband at port 1645, is ther an attibute to identify the port
> > where the request arrived?
> 
> No, there's no such attribute either.  However, both are easy to
> implement.
> 
> Regards,
> Sergey