Date: Mon, 22 May 2017 14:03:54 +0200 From: William Gathoye <william@gathoye.be> To: "Andrey V. Elsukov" <bu7cher@yandex.ru>, alarig@swordarmor.fr, freebsd-net@freebsd.org Subject: Re: Public IPv6s fail on KVM bridge with "No buffer space available" Message-ID: <a44fa8c5-d48f-25eb-51d2-16d100ba5f53@gathoye.be> In-Reply-To: <84cecdc7-e331-d3bc-3fb3-e35507e231d6@yandex.ru> References: <fbfe1ff2-bd66-9a98-d56b-6d75265936bd@gathoye.be> <84cecdc7-e331-d3bc-3fb3-e35507e231d6@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) --aNeSV6RoDbCJSO8k62lMeHSswDQ68FhI4 Content-Type: multipart/mixed; boundary="1WBkh4ai208Pd4ew5clI3w84R6eCTEusC"; protected-headers="v1" From: William Gathoye <william@gathoye.be> To: "Andrey V. Elsukov" <bu7cher@yandex.ru>, alarig@swordarmor.fr, freebsd-net@freebsd.org Message-ID: <a44fa8c5-d48f-25eb-51d2-16d100ba5f53@gathoye.be> Subject: Re: Public IPv6s fail on KVM bridge with "No buffer space available" References: <fbfe1ff2-bd66-9a98-d56b-6d75265936bd@gathoye.be> <84cecdc7-e331-d3bc-3fb3-e35507e231d6@yandex.ru> In-Reply-To: <84cecdc7-e331-d3bc-3fb3-e35507e231d6@yandex.ru> --1WBkh4ai208Pd4ew5clI3w84R6eCTEusC Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Thanks all for your answers. Since I'm not subscribed to this list, please make sure I'm in your `To` field when replying. On 05/17/2017 09:45 AM, Andrey V. Elsukov wrote: >> Please note all my GWs are outside of my IP subnets. >=20 > FreeBSD's IPv6 NDP implementation can not find GWs layer 2 address, > since its IPv6 address is not considered as neighbor. You need to > configure IPv6 address on the vtnet0 interface from the same prefix as > GWs address. Or use link-local addresses. On 05/16/2017 21:36:54, Alarig Le Lay wrote: > Did you tried to use the fe80 of your router as gateway? After some discussion with guys from the company behind OPNsense, I have been able to solve my issue. My far gateway was in /56. Even if my IPv6 is not a /56, setting my IPv6 with a /56 prefix instead of the /64 fixed my issue. Thanks for the explanation with NDP, Andrey, this is what made us on the track. :) Btw, if I wanted to use link local addresses to communicate with the provider next hop gateway, how can I know the local link fe80 IPv6 address of that gateway since my provider (OVH) doesn't disclose it? Regards, And thanks again for your help. :) -- William Gathoye <william@gathoye.be> --1WBkh4ai208Pd4ew5clI3w84R6eCTEusC-- --aNeSV6RoDbCJSO8k62lMeHSswDQ68FhI4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE8ucX65+2FhkmJe7RDn3lLATXFoMFAlki06oACgkQDn3lLATX FoNVKQ/8Ck8NXvM6Bh570wxN+uxyP5WbJMTgFeKifIIHuZUIU5WkQvAxRpJ7x5wV yqBbnlwczFPx5sdnrcYjlgfjDl20cwPLHdHE4H9YBiLQvyodAoAFR0iFevT1hscJ ObRaZCZBduvm1I1LYbgmDMsmhjkK+KUi4ZHxGXzebNx7XrX0y/4jClWaWJzHIb/Z aI8ba5vXt0gHguJqiUQO/4VyihNEYueuxJhv55mml3Z7VrRYg/W8Cio4peMf4mqt rdVPsMQfp3c1m4M3TcyzBOiWwawNFESvHy36/hrnLxIsQkwOAaWRgkFsB1lWEDbB QChLFvLgtmWHvNLpe6Wzukl7PwKmSFmHP4DJB7iXsfTI5DyNaLOThq0PaqbqmVRp bDElfyQkPUKX9ZmZE0T01B4LBg026goQXqlZryXGUPCIk4vZmQ0jy+7ee0DsS/tM DtpupXNZK32LlDLzJrTCm601H9w+xuqyBJujGULqyRjJPkBiWcRIFDpXBmN/qBWE BUyBEIlG+sjeF66/JnXaioPNA0eu2QtbsZua5WoV2UmMbTARkwSpjHvN+MJxar1l 4TORkXrCISkJv5SHv2S6Rog9Lbs5F3Z8w6dTsBoAA7JnLEJUgcsLuGm7ntun0J8Z akSsT/GEGWVsnIFzj+mFeEHGI3Eux1JfGNuhUQEbB4bNfYEKpF4= =GLp5 -----END PGP SIGNATURE----- --aNeSV6RoDbCJSO8k62lMeHSswDQ68FhI4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a44fa8c5-d48f-25eb-51d2-16d100ba5f53>