[cisco-nas] common pool for many NAS
Tassos Chatzithomaoglou
achatz at forthnet.gr
Mon Nov 3 13:25:44 EST 2003
Aaron Leonard wrote:
>> >>We want to define all these small /30 networks as a /24 in a central
>> router/server and
>> >>those specific customers to get ips from this router/server.
>> >>The problem is that we want to use such a method through aaa/radius,
>> so we won't need to
>> >>create another group-async/dialer/vtemplate interface on the as5300.
>> >
>> >
>> >>Ofcourse, the central router/server should take care in order to not
>> give the same ip
>> >>concurrently on 2+ users (even on different as5300s), like in local
>> pool ip addressing.
>> >
>> >
>> > Sounds to me like one good answer is to have RADIUS assign
>> > the IP addresses.
>> >
>> But how can i have radius assign different ip address per user? How
>> will radius know which
>> ip address is being used?
>
>
> Many RADIUS servers have the capability of maintining their own
> (internal) address pool - so they take on the job of allocating
> addresses to the clients. You do have an issue when you have multiple
> RADIUS servers, making sure that they coordinate their
> address assignments.
>
ok....thx again for your valuable help aaron ;-)
It seems our radius platform (radiator) supports address allocation through dhcp or sql,
so we're going to test it.
>> >>Could dhcp be the solution in our problem?
>> >
>> >
>> > Yes, you could use DHCP for this too. That is,
>> > DHCP from the DHCP server to the 5300; the 5300
>> > would proxy the info from DHCP to IPCP for the
>> > clients.
>
>
>> So i just have to configure a dhcp server entry on each of the AS5300s
>> and then configure
>> the dhcp pools on the dhcp server?
>
>
> Also use "peer default ip address dhcp" on the interfaces.
>
>> Do the dhcp pools and the dhcp server have to be in the same ip range?
>
>
> No.
>
> Aaron
>
--
***********************************
Chatzithomaoglou Anastasios
Network Design & Operations Center
FORTHnet S.A.
<achatz at forthnet.gr>
***********************************
More information about the cisco-nas
mailing list