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!

Route issue 1

Status
Not open for further replies.

hereigns

MIS
Joined
Sep 17, 2002
Messages
172
Location
US
Hello,
Got a Cisco 1601 running IOS 12.0(3)T. It's been running fine for 2 years until today. It's connected directly to the Internet. Below are the ip addresses:

s0 1.1.1.1/24
e0 2.2.2.1/24

Problem is - it's missing routes for the private network sitting behind it connected via firewall.

I noticed that I'm unable to add static route entries. BUT prior to today the routes were listed and available.
router# sh ip route (shows only default gateway route)

Command used to add static route for private network.
config# ip route 192.168.8.0 255.255.255.0 192.168.8.1

Oddly enough traffic from behind firewall is flowing to and from the Internet - so it's passing traffic. But like I stated earlier - when I add the static route and do sh ip route the route is not listed.

Any ideas on what may cause this? Hardware + software issue? IOS issue? Anyone else experience a problem such as this one?



 
rlivermore,
Your route statement "ip route 192.168.8.0 255.255.255.0 192.168.8.1" is ambigous, so the router is probably refusing to add it to its route table.

You have two interfaces on the router, s0 and e0. The ip route for 192.168.8.0 can only go via s0 (1.1.1.x) or e0 (2.2.2.x).

Where is 192.168.8.1?? Is this a directly connect interface on your router? If so, directly connect networks will automatically appear in the route table and do not need a static route to be added.

Or is this the IP of the firewall? If so, this is not going to work. You need a common network between the firewall and 1601, which would be 2.2.2.x, with the router being .1 and the fw being .2

Your route statement should be:
ip route 192.168.8.0 255.255.255.0 2.2.2.2

JimmyZ

 
Jimmyz,
Thank you for your response! Thank you for enlightening my oversightedness. 192.168.8.1 is the private interface on the fw. I realize now it can't talk to the interface it's not aware exists. Thank you. I added the route as you suggested and all is well.

Thanks again Jimmyz!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top