Babel + IPv4 = parse error

[Toke Høiland-Jørgensen]

Julian Schuh <julez at julez.in> writes:

> Hi all,
>
> for a current project I’m planning on using Babel as a lightweight, dual-stack routing protocol for a couple of simple tasks. For a proof of concept I’ve been using BIRD, and a plan to continue using BIRD at least in the backend.
>
> Sadly, I quickly hit a showstopper: none of the routes (neither v4 nor v6) exported from one side were imported on the other side. While investigating the problem I quickly stumbled over the following line in the debug log:
> “bird: bb: Bad TLV from fe80::xxx via vh type 8 pos 16 - parse error”
> After playing around for a little bit I found out: The problem appears
> whenever the route advertisement contains v4 routes.

Well, I'm running bird just fine with v4 routes, so it's not a total
failure, at least ;)

What's the output in birdc of 'show babel interfaces', 'show babel
routes' and 'show babel entries' on both sides?

-Toke