On Wed, 24 Nov 1999, Stephen Amadei wrote:
On Wed, 24 Nov 1999, Mike Andrews wrote:
Route a /29 subnet to them, which is the smallest block that'll give them at least 3 usable addresses. (8 addresses, 6 usable.)
O.K... I guess I can do this through RADIUS, right?
Yeah. Where you'd normally have Framed-IP-Address = 255.255.255.254, Framed-IP-Netmask = 255.255.255.255, you'd put instead something like this: Framed-IP-Address = 192.168.1.0, Framed-IP-Netmask = 255.255.255.248,
First, lets say I give this dialup a network of 192.168.1.0/29 (assuming 192.168.1.0/24 is a normal, routable class C). The net number is .0 and the broadcast is .7. What I don't understand next is what to do with the rest of the addresses. Can I dump the rest of the addresses onto an existing segment of my network that currently has a class C on it? Would I do it like the following?
Internet----Router(200.200.200.1) | ____________ Main Network 200.200.200.0/24 192.168.1.8/29 192.168.1.16/28 192.168.1.32/27 192.168.1.64/26 192.168.1.128/25 ____________ | ____________ Total Control (normally gives out IPs from a pool in 200.200.200.0/24 Gives out a 192.168.1.0/29 ____________
Looks fairly reasonable. You don't *have* to shove all those extra blocks onto a single LAN though... you don't have to shove 'em anywhere if you aren't really using them yet. Just save them for when you get some dedicated T1 customers that need some smallish blocks of IP space.
Next, I don't quite understand where I need to apply static routes. I assume I would need to add a static route on the TC for the subnet I give the dialup, but would that subnet also require a routing entry on my router, except for the obvious need for a 192.168.1.0/24 route?
If you're running RIPv2 or OSPF, and have it set up right, you shouldn't need ANY static routes. If you've got 2 or 3 TC's handling the same dialup pool (say for example you had 20 PRI's at one POP)... then static routes on your TC or your upstream are kinda useless because you don't know which TC they're going to hit on any given day/hour/whatever... so you really can't use static routes there anyway. When your 192.168.0.9/29 user dials in, the route gets added to the TC's routing table automatically (when it's told the route by Radius, basically). So that part you don't have to worry about at all. Then it's up to RIPv2 or OSPF to advertise that route to the rest of your network, and to drop the announcement when they hang up. Your regular IP pools are supposed to be advertised the same way, but in practice I never really got it working with RIPv2. (To be honest I didn't really TRY very hard. :) With OSPF it works great though. Just add the pool and all the Ciscos see it automatically. Delete a pool and the Ciscos drop that too. Mike Andrews (MA12) * mandrews@dcr.net * http://www.bit0.com/ VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY Internet services for Frankfort, Lawrenceburg, Owenton, & Shelbyville "With sufficient thrust, pigs fly just fine." -- RFC 1925 - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.