Hi Ondrej,
To reproduce the use case, connect a Juniper and a BIRD by a GRE tunnel, and use
OSPFv3 to advertise IPv4 networks. Here are the simplified configurations:
# Juniper side:
set interfaces gr-0/0/0.233 tunnel source
set interfaces gr-0/0/0.233 tunnel destination
set interfaces gr-0/0/0
The presets are still handled, in babel_iface_finish of
proto/babel/config.Y.
On 11/9/23 05:25, Toke Høiland-Jørgensen wrote:
Nick Cao via Bird-users writes:
Resend of the patch in
http://trubka.network.cz/pipermail/bird-users/2023-June/017058.html
ETX link quality estimation algorithm is
Hi
Thanks, merged.
I hope it does not break some multipoint tunnels like Wireguard, they
often have bad flags reported by kernel, but they should be configured as
PtMP anyways.
I wonder what use case is fixed by this patch, as the iface still needs
an IP address just to be considered in ospf_ifa
On Thu, Nov 09, 2023 at 11:25:10AM +0100, Toke Høiland-Jørgensen via Bird-users
wrote:
> Nick Cao via Bird-users writes:
>
> Sorry for missing this earlier, but it looks like with your patch bird
> will no longer honour the "wires" or "wireless" setting at all? Which
> will break old configs, so
Hello all,
I heard recently about the lightweight tunnel infrastructure in Linux
kernel (ip route ... encap ...). And I think this might be helpful in
the context of this thread. Linux kernel allows already to add
encapsulation parameters to the route entry in its table. So you do
not need to crea
Nick Cao via Bird-users writes:
> Resend of the patch in
> http://trubka.network.cz/pipermail/bird-users/2023-June/017058.html
>
> ETX link quality estimation algorithm is useful for link types other than
> wireless,
> especially when using babel with tunnels where packet losses do occur.
> ---
