IPv6 rip-only routing - no exchange of routes

Goesta Smekal goesta at smekal.at
Tue Nov 1 20:08:29 CET 2011


Am 2011-11-01 17:57, schrieb Ondrej Filip:

> If must sadly confirm, the RIP implementation is quite poor. The
> reason we are not working on it was that nobody really uses this
> protocol. Should somebody demand it, we could look at it. But
> currently we are concentrated on other issues. Do you need it for
> some production environment?

Yes, I do intend to use RIPng for dynamic routing on embedded devices.
Limitations in terms of very little memory (both RAM and flash) and the
short range of expected routes make RIP the ideal protocol for this
project. IPv6 is mandatory, since the nodes will interconnect 6LoWPAN
segments.

As I already stated, I am willing to help as much as I can. I will try
to find the lines in the source, where modifications have to be made,
but I am sure, there are lots of people, who can do this faster and more
reliable ;-)

I don't think there are too many changes to be made. The most obvious
should be quite easily implemented:

*) change UDP port to 521

*) change RIP version to 1

*) omit the empty RTE (since the default next hop is the sending host
anyway)

*) when writing the route to the local table, use the senders link local
address instead of some tailored global unicast.

If this is done, I can do extended tests to see if it works. Maybe I get
some other RIPng implementation to test against (hopefully not the
striped one, which I find pretty hard to configure ;-) )

  cheers

  Goesta


-- 
#!/usr/bin/perl
foreach $c (split(/ /,"47 6f 65 73 74 61 20 53 6d 65 6b 61 6c 0d 0a")) {
print pack("C", hex($c));}

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20111101/a83bbe94/attachment-0001.asc>


More information about the Bird-users mailing list