RIP help

[dbentley]

Hey,

So I'm sick to death of adding routes manually and have started to enable RIP on our staros routers.

The issue I'm having is when the ethernet interface is left with 192.168.1.1 and it's spreading that route over our network. I have many routers setup with that same address on ether1. The routers are only using wpci1 / wpci2 for actual traffic and ether1 is only used in case of emergency. How can I prevent this?

Thanks,

- Darren

[oscarBravo]

From memory, in RIP configuration: configure terminal; router rip; no network 0.0.0.0/0; network <a.b.c.d/e> - whatever your actual network is (or networks are).

[bairdc]

Also, make sure you turn off redistribution of connected and kernel routes. I suspect that's where your 192.168.1.1 is coming from. In fact I would turn off all redistribution (unless you have a real reason to leave it).

no redistribute kernel
no redistribute connected
no redistribute bgp
no redistribute ospf
no redistribute static

Craig

[dbentley]

Thanks for the replies. I've tried the suggestions to no avail.

Here you can see that I only have RIP enabled for the 2 wireless cards. I can't figure out why it's broadcasting the ethernet route. :(


ripd(config-router)# show running-config

Current configuration:
!
hostname ripd
password 1234
!
router rip
network wpci0
network wpci1
!
access-list vtylist permit 127.0.0.1/32
access-list vtylist deny any
!
line vty
access-class vtylist
!
end


Also, won't "no redistribute connected" basically disable RIP?

Thanks,

- Darren

[oscarBravo]

Also, won't "no redistribute connected" basically disable RIP? No. Do some reading on RIP.

In my (relatively recent) experience with RIP, it's a very slow protocol to converge. Wait a while before concluding that a configuration change hasn't worked.

[lonnie]

RIP converges quite rapidly when you add an IP but takes a long time to remove an IP. Most likely the route will disappear. My advice is to never use 192.168.1.x anywhere in your LAN since that is highly over used as a default.

Always assign a unique subnet to each device on each unit. It avoids troubles later and you could then leave the RIP defaults as they are and it would just work. Of course you could always enable mesh and see how it works.

No. Do some reading on RIP.

In my (relatively recent) experience with RIP, it's a very slow protocol to converge. Wait a while before concluding that a configuration change hasn't worked.

[tim]

Thanks for the replies. I've tried the suggestions to no avail.

Here you can see that I only have RIP enabled for the 2 wireless cards. I can't figure out why it's broadcasting the ethernet route. :(

- Darren

From reading the docs I'd say your config is correct, are you sure it is redistributing the 192 routes from an interface on this machine and not the interface on another machine, if you invoke the command "show ip rip" it will show you the routes being redistributed & their origins.