[Xorp-users] questions about IPv6 get_link_local_address

[XORP at sipxx.com]

I am not so sure it really should do this totally automatically just 
because OSPFv3 requires a particular kind of address. So may other 
modules and this can become very non-transparent if each module just 
goes about acquiring its own parameters.
This what the 'default-system-config' parameter really seems to be good for.
What I would like to suggest however, is to provide additional 
qualifiers to this parameter so one can differentiate what kind of 
system configuration gets imported.
so for example:
....
    default-system-config {
       address-link-local-ipv6: true
       address-link-local-ipv4: false
       address-ipv4: false
       address-ipv6: true
    }


Ben Greear wrote:
> On 10/07/2009 09:27 AM, XORP at sipxx.com wrote:
>> The only way I have been able to accomplish this (in 1.6 and 1.7) is by
>> using the explicit
>>     default-system-config
>> parameter in the interfaces { interface ...} definition.
>>
>>
>> David Balnaves wrote:
>>> Hi,
>>>
>>> I think last time I asked about this I was told that in recent version
>>> of XORP, ospfv3 should set the link local address automatically and
>>> shouldn't see the error:
>>> [ 2009/10/06 02:43:51  WARNING xorp_ospfv3:14690 OSPF +462
>>> peer_manager.cc enabled ] link-local address must be configured on
>>> eth0/eth0
>
> I'll put this on my list of things to look at, but my list is
> long!  Seems like we could probe this information easily enough
> if the user doesn't specify it, however...
>
> Ben
>