You could run ospf on the terminal servers, and redistribute connected
into ospf. That way each /32 as it connects gets redistributed. Make sure
your dialer interfaces are either passive or not running ospf.
"sh ip ospf int" will show you which interfaces are running vs not running
ospf.
I'd assign my dialup blocks out of different subnets than the backbone so
there are no arp issues.
Example:
192.168.1.0/24 is the terminal server backbone - the uplink routers and
each terminal server has an ip on this subnet, and they all speak ospf.
192.168.8.0/21 might be the pool of dialup ips you allocate from.
ripv2 should support this as well, but if you are an ISP you should
probably not be running rip.
On Sun, 17 Feb 2002, Ken Reiss wrote:
> If I may ask a quick questions of the group...
>
> I have 3 access servers with 48 IPs each for modem pool and one IP for
> the unit, all in the same class C. Most users get an IP from the pool
> for each AS, but some users want static IPs so we have radius assign
> them (in the same class c) and all is well.
>
> However, we had to assign static IPs for a new user in a difference
> class C. When the client connects they are authenticated fine and given
> the IPs and the AS can talk to them. If they come into the same AS
> every time, all is fine. However, our gateway router into which all the
> AS's go doesn't route to this user, if they come into a different AS.
>
> I have the ARP timeout on that interface of the GW router set to 900, so
> within 15 minutes it starts working. Without shortening the arp timeout
> to something ridiculous like 30, Is there a way for the AS to update the
> GW router with the new route, when the client comes into a different AS?
>
> Is this RIPv2? Or is there another/better way to do it?
>
> Thank you for your time and help,
> Ken Reiss.
>
>
--C. Jon Larsen Chief Technology Officer, Richweb.com (804.307.6939) SMTP: jlarsen@richweb.com (http://richweb.com/cjl_pgp_pub_key.txt)
Richweb.com: Designing Open Source Internet Business Solutions since 1995 Building Safe, Secure, Reliable Cisco-Powered Networks since 1995
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:05 EDT