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

2024-11-24 Thread Chris Webb
Toke Høiland-Jørgensen wrote: I think this should be turned into a proper enum (EXT_NEXT_HOP_OFF = 0, EXT_NEXT_HOP_ON = 1, EXT_NEXT_HOP_FORCE = 2 or something like that), instead of hard-coding the '2' everywhere. No problem, I'll respin with an explicit enum. :) Best wishes, Chris.

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

2024-11-24 Thread Toke Høiland-Jørgensen via Bird-users
Chris Webb 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

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

2024-11-24 Thread Chris Webb
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