Hello,
I've patched ripd so it now takes care of the administrative distance of
his own routes to update them.
This bug is described better at
http://bugzilla.quagga.net/show_bug.cgi?id=81
proposed patch at
http://bugzilla.quagga.net/attachment.cgi?id=30&action=view
But this making me dig a lot more into RIP, brought some other thing to
my mind:
ripd apparently only build a table of the used routes, shouldn't he,
like ospfd, grab all the possible routes into the table instead, and
then make his decision on that table on which one he will use?
Why? Let's say we have 2 routes for 1 destination, if 1 route fails, it
will take the time to detect the link is failing (can be immediate, or
can take XX minutes), then all the traffic will be replied with an "Icmp
unreachable", until a new message of another interface comes in saying
"hey, i know that route too" (can take as long as ~30 seconds)
This is only an idea, but i think this will force big internal changes
in ripd
Don't know if it's really worth the trouble
--
Jean-Yves Simon <lethalwp@tiscali.be>
I've patched ripd so it now takes care of the administrative distance of
his own routes to update them.
This bug is described better at
http://bugzilla.quagga.net/show_bug.cgi?id=81
proposed patch at
http://bugzilla.quagga.net/attachment.cgi?id=30&action=view
But this making me dig a lot more into RIP, brought some other thing to
my mind:
ripd apparently only build a table of the used routes, shouldn't he,
like ospfd, grab all the possible routes into the table instead, and
then make his decision on that table on which one he will use?
Why? Let's say we have 2 routes for 1 destination, if 1 route fails, it
will take the time to detect the link is failing (can be immediate, or
can take XX minutes), then all the traffic will be replied with an "Icmp
unreachable", until a new message of another interface comes in saying
"hey, i know that route too" (can take as long as ~30 seconds)
This is only an idea, but i think this will force big internal changes
in ripd
Don't know if it's really worth the trouble
--
Jean-Yves Simon <lethalwp@tiscali.be>