Rip and Password

[Equis]

Hello,

I use Star-os and rip for my network, it was very easy to get running (click the check box)

I was wondering how I put a password so no just any router connected to my network can update the routing table

Thanks

:)

[lonnie]

I am not sure. You will have to grab the manual from the zebra site and do some reading.

[tony]

The default security setting for the Zebra CLI is to only allow access from the StarOS system itself, so it is not possible for others on your network to update your routing table.

[bradg]

The default security setting for the Zebra CLI is to only allow access from the StarOS system itself, so it is not possible for others on your network to update your routing table.


I think the original poster is more concerned about another connected (possibly rogue) RIP-enabled device injecting routes into the network.

I've not had to do this myself, but it looks to be vaguely similar to OSPF authentication. If this was the issue in question, I'd begin by reading up on Zebra RIP here - http://www.zebra.org/zebra/RIP-Authentication.html#RIP%20Authentication

[bairdc]

Here is the config needed to do MD5 authentication using RIP. I think RIP V2 may be required for this, but I'm not 100% positive:

key chain group1
key 1
key-string <password>

interface wpcm0
ip rip authentication mode md5
ip rip authentication key-chain group1
!
interface wpcm1
ip rip authentication mode md5
ip rip authentication key-chain group1

Just put your password in place of <password>. You could also have multiple key chains with multiple passwords, and use them on different interfaces if you wanted to.

Craig

[Equis]

Thanks for all your replies!

Yes, it was the rogue router I was worried about, it this a concern or a bit over protective?

Thanks for the links also.

I am thinking about going to ospf but on searching the forum there seems to be others haveing problems, Also tony posted a quick how to but that link is now dead :-( does anyone have that link or another one?

Thanks Again

Rhys