Getting RIP Working

[Equis]

Hello,

To get rip working do I just turn the checkbox on and that's it?

I done that and it seems to work, I have a linux box that when I start 'routed' it gets it's updated from the Star-os unit, but after 30 seconds the linux box deletes the routes it gets from the Star-os unit.

I'm not sure If its a config fault on the star-os or the linux box.

Do I have to tell the star-os to keep talking to the linux box? do I have to put the IP's of each other somehwhere so it knows what to talk to?

I did this but no luck (I changed the interface names but did the rest word for word)

http://forums.star-os.com/showthread.php?t=2814&highlight=rip

Thanks

Rhys

[redhat66]

I use the same example from Lonnie on all my RIP enabled boxes and it works fine. I did see the same problem with the entry being removed from the surronding routers in one of my sites because I was using a layer 3 switch and it was not allowing the RIP broadcast's to function right. I suspect that is because my subnet is 192.168.x.x and RIP broadcast take place by default to 224.0.0.9. The layer 3 switch would stop this behavor with out intervention from me.

I could be wrong but by taking the L3 switch out and replacing it with a standard switch the problem went away instantly.

Best regards
redhat66

[bairdc]

It does sound like you're suffering from a multicast issue. I had this happen on an Atheros link. The route would come up initially, but would expire after a little bit. I ended up having to set RIP to use unicast on that link. Basically, just specifiy.

neighbor x.x.x.x

Where x.x.x.x is the IP of the router that needs to talk to it. I would do this on both sides of the link.

As a general rule, I've found that if you're dealing with wireless links, set them up to use unicast. Multicasts seem to have trouble over wireless links.

Craig