Did the proxy_arp command fix your routing issues or not? When you are unable to ping customers, where does the traceroute die? Todd ----- Original Message ----- From: "Mike Cisar" <mcisar@iul.net> To: "'Discussion relating to the 3Com/US Robotics Total Controlmodemsystems.'" <usr-tc@mailman.xmission.com> Sent: Thursday, November 13, 2003 12:07 PM Subject: RE: [USR-TC] Hiper ARC setup assistance please
I didn't see a response to your ? so I thought I'd try to help a little.
Thanks :-)
First...I don't see why you have your NMC and arc on different subnets? Not really related to your customers not routing but seems to me could be a problem for you down the road.
I could easily move the ARC to (for example 1.1.1.135), our old setup always had the Netserver on the same subnet as the dialup pool so I was just trying to mirror that setup (don't ask me why I did it that way 10 years ago :-). If I move the ARC to be in the same subnet as the NMC... where would I tell the ARC that the gateway for the IP pool is at .225 (whereas the gateway for the ARC would then be at .129).
There are some other unusual choices of subnets but hey...run with it.
We have 3 separate subnets coming in from our upstream, one of 64 IP's and 2 of 32. All come in over the same ethernet, and each have a separate gateway IP). The block of 64 houses our lan (workstations, servers, etc), 32 for a block of virtual web servers and the other 32 is for the dialup pool.
What's the upstream router from the arc tell you when you issue a route statement for the dialup pool? If it's a cisco....show ip route 1.1.1.228 255.255.255.227
That I couldn't tell you :-) We are on an ethernet over fiber connection and don't have access to the ISP's router. All we got at our end for equipment is one pretty red cable coming out of the wall :-) For what it's worth, with the Netserver at .226 and the IP pool starting at .228 everything works just peachy... so unless the ARC is sending something upstream to screw up the routing (or not sending something upstream that the Netserver is) that part should be remaining the same (the IP pool is the one thing in this changeover that remains constant :-)
Are you going to setup a routing protocol on the box? I'm not a big fan of setting up ip pools in the same subnet as the ethernet. I'd consider ospf instead of rip but it's really your choice. I'm thinking (but can't remember fully) that there's a statement like enable ip proxy_arp_all_dialin to get your ip pools routing when they're in the same subnet as the ether.
To be quite honest I don't know. I never had to set anything up routing-wise on the Netserver (for better or worse), but it's entirely possible that I'll need to do that on the ARC if "out of the box" it doesn't treat things the same.
Hope that helps.
Time will tell HEHE. Thanks!
Cheers,
Mike <<<<<
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc