On Tue, Apr 02, 2024 at 11:49:21PM +0200, Pim van Pelt via Bird-users wrote:
> Hoi Ondrej,
Hi
> On 02.04.2024 16:40, Ondrej Zajicek via Bird-users wrote:
> > Although one could have option that forces it to interpret as IPv6, i
> > would prefer to have 'extended next hop' option that allows to a
Hoi Ondrej,
On 02.04.2024 16:40, Ondrej Zajicek via Bird-users wrote:
Although one could have option that forces it to interpret as IPv6, i
would prefer to have 'extended next hop' option that allows to accept
both IPv4 and IPv6 next hops in Link-LSA.
Did you mean that:
1) under normal circumst
Hello,
It would be helpful if you showed "ip route show" instead of "ip route
get" for your routes, so that one could see actual routes you have in
the routing table. Please also show you bird configuration.
Regards,
Alexander
On Fri, Mar 29, 2024 at 8:53 AM Yasen Atanasov wrote:
>
> Hello,
>
>
On Sun, Mar 31, 2024 at 11:34:43AM +0200, Daniel Gröber wrote:
> Hi Babelers,
>
> I've just come across a reason I'd want to run babel with both bird and
> babeld on the same node and have them become neighbours. The details are
> tedious -- my usual disclamer applies ;)
If you want to have both
On Mon, Apr 01, 2024 at 04:14:51PM +0200, Sebastian Hahn wrote:
> > Sebastian - my interpretation of 5838 is slightly different, and I don't
> > think it expressly forbids xAF nexthops:
> > > 2.5: Although IPv6 link local addresses could be used as next hops for
> > > IPv4 address families, it is
