Public IPv6s fail on KVM bridge with "No buffer space available"

Andrey V. Elsukov bu7cher at yandex.ru
Wed May 17 07:47:07 UTC 2017


On 17.05.2017 00:24, William Gathoye wrote:
> Contrary to the other LXC/KVM, the latter cannot ping any IPv6 machines
> outside those accessible directly from the bridge. As soon I try to ping
> either the gateway of my hypervisor (still in IPv6), or any other far
> away IPv6 hosts (e.g. google.com), I got the following error message:
> 
>     [...]
>     ping6: sendmsg: No buffer space available
>     [...]
> 
>     ifconfig vtnet0 inet6 <ipv6> prefixlen 64
>     route add -inet6 <gw ipv6> -iface vtnet0
>     route add -inet6 default <gw ipv6>
> 
> Please note all my GWs are outside of my IP subnets.

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.

-- 
WBR, Andrey V. Elsukov

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 553 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-net/attachments/20170517/83886828/attachment.sig>


More information about the freebsd-net mailing list