Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

routing issue. i think

Status
Not open for further replies.

utahbob

Technical User
Joined
Aug 21, 2002
Messages
1
Location
US
I have a cisco 675 that nats my address into a 10.network. (10.0.0.1) From there it goes into a linux box with two nics (10.0.0.2-eth0, and 192.168.0.2-eth1)that acts as my web, ftp and firewall server (or hopefully will someday).
(the linux machine has ip_forwarding turned on).

The problem is that I cant seem to ping my router, 10.0.0.1, from any of my workstations. (192.168.0.5).

192.168.0.5 can ping all the way up to 10.0.0.2 on the linux box but when i try to get to the router, nothing, just a timed out message.

The linux box has full internet access and can ping all 192. addresses.

Someone mentioned that it may just be as simple as adding a static route on my cisco. they said that it may not know how to respond to a 192 address. I tried to look up how to do this but have either failed or this is not my problem. I have posted my routing table from my cisco below just in case somebody see's an obvious error and can help.

Im open to suggestions if anybody has had this problem before.

Thanks
[target] [mask] [gateway][m][p] [type] [if] [age]
0.0.0.0 0.0.0.0 0.0.0.0 1 sa wan0-0 0
10.0.0.0 255.255.255.0 0.0.0.0 1 la eth0 0
192.168.0.0 255.255.255.0 10.0.0.1 1 sar eth0 0
166.70.0.0 255.255.0.0 0.0.0.0 1 a wan0-0 0
 
u need to ensure that your Linux is properly setup to masquerade, so that it knows to pass all internal connection on to the external interface, and then to the internet/router...

second, your linux's default route should be the router.. and your router's default route should be your ISP's router... your router shouldn't really know about your internal LAN.. masquerading means all external networks see your Linux external IP as the originating source... so u don't need to enter a route for your internal 192 network... u only need to ensure that your router and Linux can talk to each other.. once u ping from an internal box, the router will think the ping is coming from your Linux box, and respond to it, that way, u will see a reply on your internal box....

also, check to see that your firewall is not dropping ICMP packets..

good luck..
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top