[Babel-users] Erroneous assignment breaks v4mapped routes, leads to extremly high cpu usage and unstable routes

[Fabian Bläse]

Hi there,

this is just a quick reminder, as there seems to be some activity on this mailing list lately.
The current babeld version has two bugs that make routing unstable if anycasting IPv4 routes.

The second bug wasn't mentioned in the first mail: https://github.com/jech/babeld/issues/47

Best Regards,
Fabian

On 23.10.19 22:23, Fabian Bläse wrote:
> Hi threre,
> 
> babeld-1.9.1 seems to have a bug with v4mapped routes. I've described the problem here [1] and made a patch with a possible fix for the issue here [2].
> 
> This issue makes babeld-1.9.1 unusable in bigger networks if IPv4 is used and multiple routers announce the same prefixes.
> The patch is tested and actively running inside a bigger babeld network.
> 
> Best Regards,
> Fabian
> 
> [1] https://github.com/jech/babeld/issues/46
> [2] https://github.com/jech/babeld/pull/45
> 
> 
> _______________________________________________
> Babel-users mailing list
> Babel-users at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/babel-users
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/babel-users/attachments/20200216/c49a1000/attachment.sig>