Date: Mon, 17 Dec 2018 14:45:42 +0300 From: "Andrey V. Elsukov" <bu7cher@yandex.ru> To: Donald Sharp <sharpd@cumulusnetworks.com>, freebsd-net@freebsd.org Cc: =?UTF-8?Q?Olivier_Cochard-Labb=c3=a9?= <olivier@freebsd.org>, George Neville-Neil <gnn@FreeBSD.org> Subject: Re: RFC 5549? Message-ID: <45cb71a0-8135-30e2-6096-784c4fc44fea@yandex.ru> In-Reply-To: <e4dc5bcb-15ba-a4b6-ddfb-a3fff7720dfb@yandex.ru> References: <CAK989yck%2BW7co1QvTOEiHNHAf3nv1kDBx6cjwo9dLX9r6TvGFw@mail.gmail.com> <e4dc5bcb-15ba-a4b6-ddfb-a3fff7720dfb@yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dI8uyWhyBAbBVLfWVKHGw4o2fV8VGFpIA Content-Type: multipart/mixed; boundary="4LStG5ujZTb13lJXFWat1uN3Uble71yxi"; protected-headers="v1" From: "Andrey V. Elsukov" <bu7cher@yandex.ru> To: Donald Sharp <sharpd@cumulusnetworks.com>, freebsd-net@freebsd.org Cc: =?UTF-8?Q?Olivier_Cochard-Labb=c3=a9?= <olivier@freebsd.org>, George Neville-Neil <gnn@FreeBSD.org> Message-ID: <45cb71a0-8135-30e2-6096-784c4fc44fea@yandex.ru> Subject: Re: RFC 5549? References: <CAK989yck+W7co1QvTOEiHNHAf3nv1kDBx6cjwo9dLX9r6TvGFw@mail.gmail.com> <e4dc5bcb-15ba-a4b6-ddfb-a3fff7720dfb@yandex.ru> In-Reply-To: <e4dc5bcb-15ba-a4b6-ddfb-a3fff7720dfb@yandex.ru> --4LStG5ujZTb13lJXFWat1uN3Uble71yxi Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 11.12.2018 15:07, Andrey V. Elsukov wrote: >> The FRRouting project has some basic support for rfc 5549 and I've >> been asked to see if it is possible to get this bit of code working >> with the FRRouting freebsd kernel interface. What is RFC 5549 you >> ask? The tl;dr of it is that you have v4 prefixes w/ a v6 gateway. >> For some more background the linux implementation cheats ( and I would= >> like to emphatically point out that I'm not suggesting this solution, >> I'm giving the linux solution to the problem as a data point to how it= >> was solved in one instance ) by installing a neighbor entry for >> `169.254.0.1 <outgoing interface> <mac address on the other side>` and= >> when installing the v4 prefix we see the v6 nexthop and replace it >> with `169.254.0.1 <outgoing interface>` in the netlink message to the >> kernel. Is support of RFC 5549 possible in Freebsd? >=20 > I have thought a bit about this, and have some ideas how implement this= =2E > In general we can install into the kernel routes that has IPv6 address > as gateway for IPv4 (currently this is not allowed by default, but it i= s > easy to allow). So, as a routing daemon developer you can use generic > API to install routes where RTAX_GATEWAY is IPv6 address. Hi, I have implemented basic support, so it can be tested now: https://reviews.freebsd.org/D18581 --=20 WBR, Andrey V. Elsukov --4LStG5ujZTb13lJXFWat1uN3Uble71yxi-- --dI8uyWhyBAbBVLfWVKHGw4o2fV8VGFpIA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlwXjGYACgkQAcXqBBDI oXpjMgf+N80MDjVuY8y+xlDD7/b7L50L3a1O6sJyXj9VfFz8KjGMpGjXAbEPFwDH S5uDDeFb2X6iYFzVXVeIH3NuQE2oCYpBnIB0dISA2A2EYmhFWedQWNaFrz1hNOcV fVMN1KKGO3o9eqghJmdvHG/brJ9jqTFM9A3SsoNAwRVjOEGnT7crXvbVs8HZ/nIO Jisea2KxJkpv1sUqclfGLriRC0YiyCNWp6e+m9VeRfflQjLP/XqQt5cWgduuxTtb EoCHSCSPr5MopI6jrXScxXlWzTvLJ2zacu+Idh4RW1LncRl/i/djmSEaN8N1NtyL Wwqgm3yyHsn3nQGl487xRQuZuacsMA== =CI07 -----END PGP SIGNATURE----- --dI8uyWhyBAbBVLfWVKHGw4o2fV8VGFpIA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45cb71a0-8135-30e2-6096-784c4fc44fea>