Marshall, I read your original post. And in my subsequent posts, it should have been a little obvious that I was having a little trouble following your example based on my follow-up questions. I do not doubt your past contributions to the list. I do appreciate you taking the time to answer my original question, and will try to implement your answer to my routing question when I am at the customer site this week, having Mike Green's example as a backup (or vice-versa, depending...). Thanks again, -- Scot ----- Original Message ----- From: "Marshall Morgan" <marshall@netdoor.com> To: <usr-tc@lists.xmission.com> Sent: Sunday, May 13, 2001 1:49 AM Subject: Re: (usr-tc) Routing a subnet to an ISDN dialup customer
Scott,
Please read my original post - it contains all the necessary elements to get the job done. I have tried to be more clean in this email.
You said: "What configuration steps do I need to take on the TC to allow it to assign this block to this dialup customer?"
Answer is a Radius Entry (only as nothing is needed on the TC but you can if you wish do what Mike Greene stated):
username Auth-Type = System Service-Type = Framed-User, Framed-Protocol = PPP, Framed-IP-Address = 192.168.1.200, Framed-IP-Netmask = 255.255.255.255, Framed-Routing = None, Framed-Compression = Van-Jacobson-TCP-IP, Port-Limit = 2, Idle-Timeout = 1200, Session-Timeout = 28800, Framed-MTU = 1500
As well, you stated: "Note that I am not running RIP. This customer will ALWAYS hit this particular TC, so there is no need to announce the route. I will manually route the block to the TC."
Answer is: So that means you do not want to announce the route via any routing method and you will be manually routing (via the Cisco I assume) the block to it (in this case) the static the customer gets from the Radius profile.
Since you will be routing them a network, not using a routing protocol to announce it, and only have a single TC, just give them a static IP on the TC Lan and let proxy arp do it's thing.
TC GW 192.168.1.1 TC IP 192.168.1.2 TC POOL whatever
on user's machine :
User Static IP 192.168.1.200 (PPP WAN DEVICE IP) - I would ask them to set their software to dynamic as you will give it to them via Radius anyway - make their setup simplier. User Ethernet IP 192.168.20.1 (LAN DEVICE IP)
on GW router (assume a Cisco):
ip route 192.168.20.0 255.255.255.224 192.168.1.200
(so net is 192.168.20.0/27)
I hope this better explains what works in the field and how easy your setup can be.
PS: I have probably been on this list as long as other active members - I even have some of David Bolen's old email marked. I would like to think I have been very helpful to many people as well both now and in the past ;-)
Marshall Morgan
Internet Doorway, Inc (aka NETDOOR) http://www.netdoor.com
601.969.1434 x28 | 800.952.1570 x28 | 601.969.3629 x28 | Fax 601.969.3838 ----- Original Message ----- From: "Scot Desort" <scot@njaccess.net> To: <usr-tc@lists.xmission.com> Sent: Friday, May 11, 2001 7:17 PM Subject: Re: (usr-tc) Routing a subnet to an ISDN dialup customer
Marshall-
I know basic routing on a Cisco, and if I were were using a Cisco in this case, there would be no question. But I stated in my original post that I am new to the TC when it comes to how it handles routing. Reading a Cisco book is not going to help me enter commands at a HARC prompt. We run very basic single user dialup out of our TC, and now have the need to route a small network to a customer. I was hoping to get a little hand-holding from the folks on this list.
I appreciate you taking the time to answer my questions. But I honestly don't think a Cisco book is going to help me here. A little more than '"No" might have been a little more helpful to me than the Amazon link. If there is some inherent feature in IP that handles the routing of the network to the dialup customer that I do not understand, I will certainly take the opportunity to read about it and try to comprehend it. Unfortunately, time is of the essence in this situation.
Since your example illustrates that no commands need to be entered on the HARC, and that proxy arp will handle everything, I will try your suggestion.
Thanks again for the help.
-- Scot
- 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.