NAS-identifier instead of IP-identifier

[Rich Marriner]

I don't believe so. Not if you use the NAS-IP-Address attribute. 
Traditionally that was used for access servers on the coporate level and 
due to the nature of their work they had static IP addresses.  I for one 
would not want my APs (if I were deploying a wide area wireless network) 
to have dynamic IP addresses.  The administration of that would seem to 
become a nightmare unless you use a dynamic dns service, but that seems 
kind of corny for a service provider.

I may be talking out my butt, and I don't mean anything by it, I just 
wouldn't use dynamic ip addresses for any of my network infrastructure. 
Usually static IP address aren't that much more from your upstream provider.

On second thought, what if you created a VPN tunnel from the AP (using, 
say OpenWrt) and then you could assign static private IPs to the AP? 
Would this work?

I hope this was useful, but somebody else will probably come up with a 
lot more intelligent answer.

Richard




Rob Cleminson wrote:
> Hello, I am new to freeradius and need a little help....
> 
> We are going to be deploying a bunch of Wireless Routers all over the place and they may have DHCP addresses on them instead of static WAN addresses..When a client associates to our Wireless Router they are redirected to the Radius Server which then creates a secure session onto the internet(WPA etc) 
> 
> Is there a way of identifying the router to our FreeRadius server without having a static IP address on each Router?
> 
> Cheers
> 
> Rob
> 
> 
> - 
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html