What is RIP?

[GoodRevrnd]

What is RIP? From what I gather poking around in my router it looks like you use this instead of NAPT if you have DHCP enabled. Can someone clarify and explain?

 

[ScottMac]

RIP is a routing protocol.

With some exceptions, it's generally used by a router to announce which routes it "knows" about to all the other (RIP) routers that might be on the network (and perhaps listen for other RIP routers so it knows where the other routes are).

It's totally useless for virtually all one-router networks (including home networks with a little consumer-grade router/firewall boxes ...like the LinkSys, NetGear, etc). The exception would be some special applications running on a *NIX box.

There is no RIP routing on the Internet. If you activate RIP towards the ISP, best case, they filter it and nothing happens .....worse case, they get mad at you and shut down the connection. RIP is a fairly verbose protocol.

Make sure it's shut down, then ignore it forever.


FWIW

Scott

 

[GoodRevrnd]

So would this come into play when I set up a webserver that may have php and/or mysql on it? Or will that just be opening NAPT servers on the router?

 

[ScottMac]

It wouldn't come into play at all. It's for routers (and things that look like routers, but only if there's a bunch of 'em).

The application running on any box on the network would be totally irrelevant.

Make sure it's turned off, and forget about it.

Ignore the fact that you've seen it. Put it out of your mind. Off is good. Off is your friend. Off is a pleasent thing...On is evil; On wants to mess up your network and keep you awake allllll night; On is not your friend. On is BAD....


FWIW

Scott

 

[Woodchuck2000]

<< Ignore the fact that you've seen it. Put it out of your mind. Off is good. Off is your friend. Off is a pleasent thing...On is evil; On wants to mess up your network and keep you awake allllll night; On is not your friend. On is BAD.... >>


Haha, that's the funniest thing I've heard all morning.

RIP stands for Routing Information Protocol, and is very much as scottmac says (funnily enough, as scottmac is yet to be wrong ). It's very useful in multi-router environments and is basically a way for routers to automatically update their routing tables. (manually updating routing tables takes "^£$ ages and is a pain in the backside)

In single router environments, it is pointless and evil.

BTW, what does FWIW mean?

 

[Nutz]

<<

<< Ignore the fact that you've seen it. Put it out of your mind. Off is good. Off is your friend. Off is a pleasent thing...On is evil; On wants to mess up your network and keep you awake allllll night; On is not your friend. On is BAD.... >>


Haha, that's the funniest thing I've heard all morning.

RIP stands for Routing Information Protocol, and is very much as scottmac says (funnily enough, as scottmac is yet to be wrong ). It's very useful in multi-router environments and is basically a way for routers to automatically update their routing tables. (manually updating routing tables takes "^£$ ages and is a pain in the backside)

In single router environments, it is pointless and evil.

BTW, what does FWIW mean? >>



RIP is an old Distance-Vector routing protocol, which is very limited, hence being dredded by most net admins. RIPv2 isn't so bad in that it supports VLSM a la OSPF and EIGRP. In single router enviroments a simple default or static route will usually suffice. Given RIP's fundamental limit of a 15hop count metric, it is not a good routing protocol for large multi-router enviroments. In that case use OSPF or EIGRP (if its all Cisco).

RIP

RIPv2

FWIW=For What Its Worth