IPv6 address classification

lex lex at lynx.vanet.org
Fri Jun 10 03:39:16 CEST 2011


On 10/06/2011 01:23, Ondrej Zajicek wrote:
> On Thu, Jun 09, 2011 at 02:14:46PM +0100, lex wrote:
>> I am interested to hear whether the strictness of the
>> ipv6_classify(ip_addr *a) function would be considered a "bug" or a
>> "feature", but from what I can tell, quagga and openbgpd do not classify
>> addresses in such a strict fashion, and this can produce problems in
>> mixed environments where quagga/openbgpd peers may try and send such
>> routes to bird6.
>
>> Perhaps any address that is not link-scoped should be implicitly
>> classified as global? At the very least, receiving a "bogus route"
>> should not result in all existing routes from that peer being dropped.
>
> I am not sure about the classification of such strange routes, but
> it definitely shouldn't affect other routes from that peer. I will
> check that.
>

Thanks.

I am thinking that anything that does not fit link/site scope should be 
classed as global scope, even if just for compatibility with other 
software. There is a whole load of free address space out there; it 
should probably be routable by bird. That is just my opinion though.

-- 
lex at lynx.vanet.org




More information about the Bird-users mailing list