Mike- Thanks for your detailed explaination. At the first chance I get, I will give it a shot. -- Scot ----- Original Message ----- From: "Mike Greene" <mikeg@rockisland.com> To: <usr-tc@lists.xmission.com> Sent: Friday, May 11, 2001 9:42 PM Subject: Re: (usr-tc) Routing a subnet to an ISDN dialup customer
Hey Scott, I'll give you a hand.
I've successfully gotten both single static IP's and routed subnets working through the HARC using OSPF. Are you using OSPF? If you are only using the one NAS then this is very simple, if you have multiple NAS's then you will need OSPF (RIPv2 would work, but I haven't touched it).
For me getting the TCH to do what I wanted was a major PITA, mostly because 3com support was useless, and the documentation was very light in examples. So I fussed and fiddled, and gave up for a year, then dove back in and viola it started working! ;)
Why don't you send me your problem via email (sorry I don't have your original post) and I will give you the run down on what I have done here, it may not exactly apply but I believe it will help you none the less.
I'll give you what I have now and you can draw from that...
4) Lucent PM3 1) Lucent PM2 1) TotalControl
1) Cisco 3640 (DR for OSPF)
All sit on the same Ethernet segment, 199.217.72.0/24 The Lucent NAS uses 209.102.67.0 for their IP pools, the TCH is 207.149.168.0
I use OSPF/VLSM to divy up the IP pools among the PM3's, the TCH just gets the whole class c since it has a much higher port density, the dialup modem pools are announced via OSPF, why? Because static IP customers (single or subnet) will hit different NAS's and the hardware needs to know where to send the packets, static routes don't cut it in this situation.
We assign the static IP (single or subnet) via Radius, so you have to create an entry in your radius users file (this can vary depending on your Radius software) and for the TCH we have to add a "send policy" (this really had me stumped for a long time!) the PM3's just dealt with it.
If you just have one NAS, then you can use static routing and be done with it, you will have to create a route in your router (which connects you to the Internet) and one in your NAS, and then create the Radius entry and your pretty much done.
Here is a Livingston 2.0.1 Radius entry for a single static IP customer:
joeuser Password = "its-a-secret-man!", User-Service-Type = Framed-User, Framed-Protocol = PPP, Framed-Address = 209.102.67.1, Framed-Netmask = 255.255.255.240, Framed-Routing = None, Framed-Compression = Van-Jacobsen-TCP-IP, Framed-MTU = 1500, Session-Timeout = 28800
Here is an entry for a static subnet:
joeuser2 Password = "its-another-secret!", User-Service-Type = Framed-User, Framed-Protocol = PPP, Framed-Address = 209.102.66.9, Framed-Route = "209.102.66.8/29 209.102.66.9 1", Framed-Routing = None, Framed-Compression = Van-Jacobsen-TCP-IP, Framed-MTU = 1500
So there you go, if you ARE running OSPF let me know and I'll go into a little more detail on that end of things.
Disclaimer, I'm not an expert! I look up to guys like Mike Andrews and Jeff Mcadams, they have a LOT more experience with the 3com gear than I, but I did manage to figure it out over time, by reading examples and blowing up a few things along the way (well not that bad)... :-)
- 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.
- 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.