On Jun 27, 2009, at 12:08 PM, James Carlson <[email protected]>
wrote:
Dan McDonald wrote:
On Sat, Jun 27, 2009 at 12:23:19AM -0700, Ben Rockwood wrote:
<SNIP!>
So my question is... given that it seems switch vendors such as
Force10
aren't supporting IRDP any more, and RIPv2 is generally considered
taboo by
network administrators, what options do I have for router discovery?
I'm pretty sure the latest version of in.routed performs all of the
tasks
in.rdiscd used to do...
<snip>
I guess the real question is: if you wanted router discovery,
but you don't want ICMP Router Discovery or RIP-2, then what
exactly do you want?
For what it's worth, I'd recommend RIP-2 over router discovery.
The complexity is essentially the same, and the capability and
reliability is higher. I think the fear of RIP comes from a
number of factors:
<snip>
I have to second this recommendation too, there is nothing wrong with
RIP-2 as an edge routing protocol. It is far more secure then people
make it out to be. Besides what was mentioned earlier you can limit it
to only support a set group of unicast neighbors, filter routes
received and sent, and setup authentication with md5 passwords.
We use OSPF in our core, but redistribute certain routes learned on
the edge by RIP and send out some of the routes learned in the core to
the edge by RIP. Works well and most edge and endpoint systems have
good support for RIP-2.
-Ross
_______________________________________________
networking-discuss mailing list
[email protected]
