Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Basic routing question - I hope.

I have a LAN that is running out of IP numbers. It is currently 192.168.1.x and I was going to add 192.168.5.x to the mix. I bought a 2621 and hooked FE0/0 to the existing network. I hung a switch off the FE0/1 and put a PC out there to test with the IP of 192.168.5.42. On the LAN I have a Number of Netware servers running IPX and a few NT servers running IP. IPX worked fine. IP is not playing nice however. From the router I can (standard)ping anything on either side. When I try to ping any hosts/servers on the 1.x side from the test PC or extended ping from the router's 5.2 interface, I get nothing. I have doen all kinds of NAT stuff in the past, but this is the first standard routing I've messed with. Any ideas why this won't work. Here is my current show run I have also tried router rip v2 to no avail and my static route I have tried setting the next hop for 1.x to FE0/0. The 0.0.0.0 route mentioned below is the firewall so that it sends unknown addresses out through the internet. Thanks for you help.

ip subnet-zero

!

!

!

!

!

!

interface FastEthernet0/0

ip address 192.168.1.39 255.255.255.0

duplex auto

speed auto

no cdp enable

!

interface FastEthernet0/1

ip address 192.168.5.2 255.255.255.0

duplex auto

speed auto

no cdp enable

!

ip classless

ip route 0.0.0.0 0.0.0.0 192.168.1.27 permanent

ip route 192.168.5.0 255.255.255.0 FastEthernet0/0

no ip http server

ip pim bidir-enable

!

no cdp run

!

5 REPLIES

Re: Basic routing question - I hope.

Hi,

In your config, try to remove the following line

ip route 192.168.5.0 255.255.255.0 FastEthernet0/0

or it should be changed to

ip route 192.168.5.0 255.255.255.0 FastEthernet0/1

Bronze

Re: Basic routing question - I hope.

sounds like you have added a second exit point from the 192.168.1.0 network. The servers probably have a gateway (default route) pointing to the firewall or nowhere if they were not using the firewall. They need to point to the .39 address so the router can route traffic destined for other ip networks.

New Member

Re: Basic routing question - I hope.

To add to the last post,

all your client workstations and servers should point to their local router lan interface as the default gateway. On your 192.168.1.0 segment, if those servers/workstations have 192.168.1.27 as the default gateway, when they try to reply to a ping from 192.168.5.0, they will send the reply to 172.168.1.27 and the ping will fail.

you should not need a static route to the connected networks, since they are connected, the router knows how to get to them.

the default route should be the only static route you need to exit your two lan segments toward the internet or other networks.

hope this is helpful

New Member

Re: Basic routing question - I hope.

As on the previous replies, change your clients default GW to the router and remove the static ip route for the 192.168.5.0/24 network. If you don't want to change your gateway address of your client machines then you should add routes on the servers pointing to 192.168.1.39 for the 192.168.5.0/24 network, or better still, put a route on your FW (Gateway) pointing to 192.168.1.39 for the network 192.168.5.0

New Member

Re: Basic routing question - I hope.

If you remove the ip route 192.168.5.0 255.255.255.0 FastEthernet0/0 it should work. Basically you are traying to route the traffic destined for 192.168.5.0/24 out of the interfaces that handles the 192.168.1.0/24 subnet.

Chris B.

150
Views
0
Helpful
5
Replies
CreatePlease login to create content