bird ospf and ipv6

[Mathias Wolkert]

Hi

I have similar issues running bird 1.2.5 on vanilla debian lenny.

IPv4 wise I assign /32s to individual lo:x instances as service addresses.

These are showing up in bird.

IPv6 wise I cannot assign /128s to individual lo:x but to the "real" 
loopback lo.

This works fine in quagga.

These are not showing up in bird.

If I look at the kernel table from shell with ip -6 route, the /128s are 
shown as "unreachable" with error -101 but working fine with ping and so on.

How would I do this "right"?
Assigning /128s to loopbacks is standard on ciscos and alike for setting 
up iBGP peering and I believe most people will try to configure it like 
that.

Any advice or help is much appreciated.


/Tias


On 3/20/11 16:22 , Ondrej Zajicek wrote:
> On Sun, Mar 06, 2011 at 04:34:52PM +0100, fredrik danerklint wrote:
>> There is one thing tough and that is that the ip addresses of the loopback
>> interface lo1 is not announced to the others within the ospd area in ip6.
>
> The reason for that is probably that loopback does not have a link-local
> address and BIRD skips that interfaces. BTW, the fact that it works in
> IPv4 is unexpected, it was supposed that loopback and its addresses
> would be completely ignored by OSPF. I thought that (at least in Linux)
> it is a common trick to use dummy interface for such purposes (which
> looks in many ways like a common interface, unlike the loopback
> interface) instead of loobpack but i don't know a good rationale for
> that.
>
>> Is there some way to have it announced and that it follows the state of the
>> interface (ie UP and DOWN), just like the ospf for ip4 does allready.
>
> If you add that prefix using 'stubnet' then it is completely unrelated
> to any interface and will be announced always.
>