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. BTW, are third-party next hops allowed in Babel? I checked RFC 6126 but found nothing. Also note that the new next hop options are missing its documentation. Perhaps you could send following patch with that? -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
signature.asc
Description: Digital signature
