[PATCH v2] Babel: Allow v6 next hop on interfaces with v4 addresses

[Ondrej Zajicek]

On Fri, Dec 06, 2024 at 05:51:57PM +0000, Chris Webb wrote:
> Toke Høiland-Jørgensen <toke at toke.dk> writes:
> 
> > Chris Webb <chris at arachsys.com> writes:
> > 
> > > By default, the Babel protocol will advertise an IPv6 extended next hop
> > > address on interfaces which don't have an IPv4 address. This is controlled
> > > by the 'extended next hop' option.
> > >
> > > Add support for 'extended next hop force' which advertises an extended
> > > next hop even when IPv4 addresses are present. (They may be temporary,
> > > for debugging or otherwise unsuitable for including in an
> > > advertisement.)
> > 
> > Acked-by: Toke Høiland-Jørgensen <toke at toke.dk>
> 
> Many thanks! Is there anything else needed from my side for this to be
> mergeable? Very happy to spin again with any changes if so?

Hello

Merged. I did some rather intrusive rework:

https://gitlab.nic.cz/labs/bird/-/commit/f80003e35b94cd7b5807b72a3697b7762a00f83f

- Changed it to be two separate options, existing one to control support
  for RFC 9229, the new one 'next hop prefer' to control the behavior

- Moved the effective code to the proper place (where the next hop is
  actually selected), that simplifies reconfiguration

I hope that is okay for you.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
"To err is human -- to blame it on a computer is even more so."