Hi Maria,
It looks like it doesn't like the configuration of directing IPv6 prefix
that we receive from gw (we have 3 sessions) to ifname. The multipath is
working fine for IPv6 after I removed that configuration, and it works for
both bird v1 and v2:
fdaa::/16 proto bird src fdaa:dc60:20:1::a3e:
On Tue, Feb 18, 2025 at 07:27:10PM +0200, Mantas Mikulėnas wrote:
> > The behavior you are describing:
> >
> > > it was consistently choosing a 1+ metric path through another area,
> > > despite having a direct 10-metric path to the origin in the same backbone
> > > area.
> >
> > It seems to me
On Tue, Feb 18, 2025, 18:38 Ondrej Zajicek wrote:
> On Tue, Feb 18, 2025 at 12:51:09PM +0200, Mantas Mikulėnas via Bird-users
> wrote:
> > From: Mantas Mikulėnas
> >
> > For an ordinary E1 or E2 route exported by another Bird2 router in the
> > same area, it was consistently choosing a 1+ me
On Tue, Feb 18, 2025 at 12:51:09PM +0200, Mantas Mikulėnas via Bird-users wrote:
> From: Mantas Mikulėnas
>
> For an ordinary E1 or E2 route exported by another Bird2 router in the
> same area, it was consistently choosing a 1+ metric path through
> another area, despite having a direct 10-me
From: Mantas Mikulėnas
For an ordinary E1 or E2 route exported by another Bird2 router in the
same area, it was consistently choosing a 1+ metric path through
another area, despite having a direct 10-metric path to the origin in
the same backbone area.
It seems that this was because the rule
