[nsp] Dynamic users and routes

Oliver Boehmer (oboehmer) oboehmer at cisco.com
Fri Mar 28 13:11:51 EST 2003


without taking a look at your current config I can't recommend too much.

In general: If your user base is small (you only mentioned a couple of peers) I would use a dialer profile configuration, see http://www.cisco.com/warp/public/793/access_dial/ddr_dialer_profile.html for an example.. Then your multilink bundle will be the individual "Dialer<n>" interface, and you can happily point your statics to those interface. 
For a larger user base you want to go with a Radius server which makes the config much easier and more flexible..


> -----Original Message-----
> From: Arie J. Gerszt [mailto:arie at gerszt.ch] 
> Sent: Freitag, 28. März 2003 07:27
> To: cisco-nsp at puck.nether.net
> Subject: [nsp] Dynamic users and routes
> Hello,
> I've got a little Cisco problem. There is a 2600 router with two
> BRI interfaces and there are a couple of other routers out there
> periodically connecting to it. I'm using virtual-templates to allow
> for mppp channel bundling. So the interface is alway changing.
> Sometimes this user has got vi2, the other time vi3 and so on.
> Putting a static route route with "ip route blabla" is not an
> option.
> Now the problem is how can I associate a separate static route (ie.
> 192.168.40/24 and so on) to the "users" that connect to the 2600?
> I've been searching the Cisco website for documentation all night
> and can't find a useful solution other than putting a RADIUS or
> TACACS server in place to handle the routes.
> Is there any way to bond a static route to a given user thats
> connects to the machine in a way that can be done entirely local
> on the router? The IOS I have on it is 12.2.T13(3).
> Arie
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list