[Babel-users] Buggy routes exported by babeld

[Baptiste Jonglez]

On Mon, Apr 22, 2013 at 10:29:22PM +0200, Gioacchino Mazzurco wrote:
> I can reproduce a similar but not identical bug because my filter are defferent
> 
> gioacchino at G10h4ckLab ~ $ ip -6 route show
> ...
> ...
> 2001:470:c8f7:ee:ee:15:6d7b:4d21 via fe80::7825:ddff:fe9d:4643 dev isole  proto 
> 42  metric 1024 
> 2001:470:c8f7:ee:ee:15:6d7d:9e9 via fe80::7825:ddff:fe9d:4643 dev isole  proto 
> 42  metric 1024 
> 2001:470:c8f7:ee:7058:edab:5584:25b8 via fe80::7825:ddff:fe9d:4643 dev isole  
> proto 42  metric 1024 
> 2001:470:c8f7:ee:f4e4:47dd:ac3a:f52d via fe80::7825:ddff:fe9d:4643 dev isole  
> proto 42  metric 1024 
> ...
> ...
> 
> those 3  /128 route shouldn't appear ( they aren't babel node but a babel node 
> can see them ( but doesn't have a specifical 128 route for them ) )

All right, it looks similar enough.

The /128 routes I was talking about are the routes that babeld
reportedly exports. Other babel nodes simply grab these exported buggy
routes and install them in their routing table (as in your case).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/babel-users/attachments/20130423/cd6d0ab4/attachment.pgp>