Stop Accepting Routes

[syndicate47]

Hello

I am setting up a test network that sits on a live LAN/WAN environment.

I have a 2600 plugged into a switch on my live network subnet of 10.127.x.x. The ethernet port has been given a vaild IP for this network.

Then using a DTE/DCE cable I have another 2600 hooked up on the serial ports and on the second 2600 I have a laptop plugged directly into the ethernet port on a cross-over cable.

A test server on my live LAN has been given static routes in order to communicate down the test WAN to the laptop ( overwise traffic goes to my live Default Gateway )

I have configured staic routes on the 2600 to route traffic between the 2 LANS.

On the second 2600 I have a static route pointing to the 10.127.x.x LAN to get to my test server. The problem that I am getting is that a router on my LIVE LAN is broadcasting a 10.x.x.x subnet to my TEST routers so when I add the static for 10.127.x.x it thinks it is relavent to the 10.x.x.x subnet and traffic does not route as it shoul.

Is there a way I can stop my test routers picking up this information.

I hope this makes sense to somebody.

 

[thebruge]

What routing protocol is the test router running?

 

[syndicate47]

Oh yeah sorry

IP

 

[Nettekkie1010]

By default most configs have: no ip classless

Enter: ip classless

See what happens.

 

[Nettekkie1010]

Oh... also, if you're running RIP you will want to enter the following command uner ROUTER RIP:

no auto-summary

Haveagoodun!

 

[syndicate47]

Hi

Both are ip classless already i'm afraid.

and I don't think i'm running RIP?

 

[thebruge]

can you send the output of:

- sh ip protocol
- sh ip route

 

[syndicate47]

OK

ROUTER 1
SOUTH#show ip protocol
SOUTH#show ip route

Gateway of last resort is not set

C 144.44.0.0/16 is directly connected, Serial0/0
10.0.0.0/16 is subnetted, 1 subnets
S 10.127.0.0 [1/0] via 144.44.0.1
SOUTH#

ROUTER 2
NORTH#show ip protocol

NORTH#show ip route

Gateway of last resort is not set

S 172.16.0.0/16 [1/0] via 144.44.0.2
C 144.44.0.0/16 is directly connected, Serial0/0
10.0.0.0/16 is subnetted, 1 subnets
C 10.127.0.0 is directly connected, Ethernet0/0
NORTH#

Protocol returned no results for both?

 

[thebruge]

According to your description:

"LIVE LAN is broadcasting a 10.x.x.x subnet to my TEST routers so when I add the static for 10.127.x.x it thinks it is relavent to the 10.x.x.x subnet and traffic does not route as it should"

This does not appear to be the case, there are no dynamics routes learnt by either router.

What exactley happens when you add the static route you are talking about? Also which routers are you adding this to? What is the command you are adding?

 

[syndicate47]

Isn't the 10.0.0.0/16 being pickup from somewhere?

The thing that made me think something was going wrong was the way that the 10.127.0.0 static entry on SOUTH does not have the /16 subnet at the end as with the 172.16.0.0/16 on North.

Thats why I thought it was assoicating it with the 10.0.0.0

My command on SOUTH was

IP ROUTE 10.127.0.0 255.255.0.0 144.44.0.1

Here are the ping reaults I get, see if you can figure it out.

144.44.0.1 (NORTH serial ) pings 144.44.0.2 (SOUTH Serial) OK and Vice Verse

10.127.140.1 (NORTH ETHER) pings 172.16.0.1 (SOUTH ETHER) OK and Vice Verse

10.127.3.36 (CLIENT) pings 17.16.0.1 (SOUTH ETHER) OK and Vice Verse

172.16.0.2 (CLIENT) pings 10.127.140.1 (NORTH ETHER) FAILS and Vice Verse

10.127.3.36 (CLIENT) pings 172.16.0.2 (CLIENT) FAILS Vice Verse


The 10.127.3.36 client static routes to get to 144.44.x.x and 172.16.x.x so that is does not go down the LIVE LAN GW.

The 172.16.0.2 has no static routes.

This is getting messy but I hope if you maybe draw it out it makes sense????

 

[Nettekkie1010]

Do you have the ZERO subnet enabled in both routers?

 

[syndicate47]

No but I thought this wouldn't matter as I am only pinging routes that exist. Or do I have that wrong?

If so, from my configs what interfaces should the 0.0.0.0 routes use?

Thanks for all your by the way ( both of you )

 

[Nettekkie1010]

Well...

172.16.0.2(client) resides on the 172.16.0.0/16 subnet which is the zero subnet for that mask.

In config mode enter: ip subnet-zero

Everything else looks ok.