"Echo FreeRadius" <[EMAIL PROTECTED]> wrote: > For example we are in the process of putting in 4 Nortel CVX 1800's with > 1288 lines each all in one large roll over (5152 lines) in the GTA (Greater > Toronto Area) > > >From those 4 CVX's we are going to provide wholesale dialup port for 4 - 10 > different ISP's ... > Anyway we wouldn't want each ISP to have to assign 1288 IP's to each NAS as > this would be a large waste of IP addresses. If we can have radius assign > IP's then this greatly reduces the number of IP's allocated.
This means that a particular IP address can be assigned on the fly to any one of 4 NAS boxes. In order to route the packet to the correct NAS, you've got to add a new route for that IP. This means (as Miquel said) thousands of routes, and hundreds of route flaps. I'm not sure how else to do it. Bridging and a smart switch may help, but then you've got to forcibly expire arp entries in the switch, and add new ones, when an IP address moves from NAS to NAS. That may be hard. > Again for redundancy and performance we will likely have 2-4 radius > servers per company depending on the redundancy level they > require. The sharing of IP's between radius server IPpools is a > great asset. It's also hard. You get into consistency issues, where the "sharing" may only done every so often, but customers may switch IP's and re-dial more often than that. I would think about the issues VERY carefully before implementing such a large and complicated network. Be very sure that you can do everything needed to make it work. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
