Ondrej Zajicek <santiago@crfreenet.org> writes:
On Tue, May 30, 2017 at 03:20:42PM +0200, Toke Høiland-Jørgensen wrote:
This adds support for dual-stack v4/v6 operation to the Babel protocol. Routing messages will be exchanged over IPv6, but IPv4 routes can be carried in the messages being exchanged. This matches how the reference Babel implementation (babeld) works.
Hi
Merged. I did some minor modifications. First, adding 'active' next_hop fields to struct babel_iface, so value in babel_iface_config is kept unmodified. Second, adding next_hop fields instead of just next_hop_seen fields to struct babel_write_state, so it is ready for third-party next hops.
Right, fair enough. Your changes look good to me.
BTW, are third-party next hops allowed in Babel? I checked RFC 6126 but found nothing.
Hmm, third-party next hops as in a next hop that is on a different node than the one running the routing protocol? There's no explicit support for it, but I guess you could do that (i.e., there's nothing that explicitly forbids it either). Not sure how babeld will react to non-LL next hop addresses...
Also note that the new next hop options are missing its documentation. Perhaps you could send following patch with that?
Ah yes, sorry about that. Was going to add that in v2, but guess I must have forgotten. Will send a separate patch that updates the documentation :) -Toke