[quagga-dev 3868] Re: Configure rtadv from another software

Paul Jakma Paul.Jakma at Sun.COM
Mon Dec 5 19:52:08 GMT 2005

On Thu, 1 Dec 2005, Romain KUNTZ wrote:

> Maybe someone will be interested in such feature, so here is patch 
> against quagga-0.99.2 that allows dynamic advertisement of new 
> prefixes: 
> http://software.nautilus6.org/packages/quagga/quagga-0.99.2-netlink-rtadv.tar.bz2

Could you supply a diff of your changes against CVS? Bonus points if 
your diff also patches relevant ChangeLog files (the more complete your 
patch is, the easier it is for lazy maintainers to apply it ;) ).

> Basically, a new Interface Command is available for neighbor 
> discovery. When activated, rtadv listens to rtnetlink. When an address 
> is added to an interface, the prefix the address is configured from is 
> automatically advertised on the link. When the address is deleted, the 
> prefix is not advertised anymore.
> The motivation is for example when you use prefix delegation for IPv6, 
> you do not need to configure rtadv once you received your prefixes and 
> configured your interface's address.

Good idea.

Another neat idea would be to key RAs according to the present of a 
route in the table. Eg imagine:

            \    /
             \  /
           <internal IGP cloud>
           <several internal>
           < hops away..   >
            | /    \ |   |
            R1      R2---R3   <etc>
            |       |    |
          ----    ---------   <end host networks>

Imagine this site gets two /48 prefixes from its ISPs. The site is an 
enterprise site, not just a simple, flat end-user. It's end-user 
networks, on which RAs are desireable and the routers servicing them, 
are at least one hop away from the "border" routers.

How are R1, R2, R3, etc. to know which prefixes to advertise?

One way might be to key advertisement based on whether prefixes are 
available in IGP.

Interested? :)

> Regards,
> Romain


More information about the Quagga-dev mailing list