From owner-freebsd-net@freebsd.org Wed May 17 07:47:07 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D908D70BED for ; Wed, 17 May 2017 07:47:07 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward2j.cmail.yandex.net (forward2j.cmail.yandex.net [IPv6:2a02:6b8:0:1630::15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 799F2B52 for ; Wed, 17 May 2017 07:47:06 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp1j.mail.yandex.net (smtp1j.mail.yandex.net [95.108.130.59]) by forward2j.cmail.yandex.net (Yandex) with ESMTP id 702F7212DA; Wed, 17 May 2017 10:47:02 +0300 (MSK) Received: from smtp1j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1j.mail.yandex.net (Yandex) with ESMTP id 53C763C80F9E; Wed, 17 May 2017 10:47:00 +0300 (MSK) Received: by smtp1j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 3JCSGgiQ1A-l0gCZ5Hk; Wed, 17 May 2017 10:47:00 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1495007220; bh=pyvufvxXapelDLVE2kcFStl4NWRXVcwCh0V8uVpoY9I=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=K1IVdr2IbnZQfQBf09l8tqVz3ZLWWOfTpcAFyQZQgiP+8MvuKIgt6h+PHvzYgef8y aqFrlve02lIj+8FqA3Bsq1Wko07L27oLOuaPIvu7b0HM9Hy/kQtN9inVzH8s/QXHeW +wTb4OY61RRjxLyw7OlaylZoZxYu+FQMLrtdEV4c= Authentication-Results: smtp1j.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: Public IPv6s fail on KVM bridge with "No buffer space available" To: William Gathoye , freebsd-net@freebsd.org References: From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <84cecdc7-e331-d3bc-3fb3-e35507e231d6@yandex.ru> Date: Wed, 17 May 2017 10:45:25 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="BO3lnaN8vO57KVejrGSdlmIo1kMbb5TV3" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 May 2017 07:47:07 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --BO3lnaN8vO57KVejrGSdlmIo1kMbb5TV3 Content-Type: multipart/mixed; boundary="HDBwRCJIjLwvXC9jLAsogtpRJmqaiiF4A"; protected-headers="v1" From: "Andrey V. Elsukov" To: William Gathoye , freebsd-net@freebsd.org Message-ID: <84cecdc7-e331-d3bc-3fb3-e35507e231d6@yandex.ru> Subject: Re: Public IPv6s fail on KVM bridge with "No buffer space available" References: In-Reply-To: --HDBwRCJIjLwvXC9jLAsogtpRJmqaiiF4A Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable 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 pin= g > 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: >=20 > [...] > ping6: sendmsg: No buffer space available > [...] >=20 > ifconfig vtnet0 inet6 prefixlen 64 > route add -inet6 -iface vtnet0 > route add -inet6 default >=20 > 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. --=20 WBR, Andrey V. Elsukov --HDBwRCJIjLwvXC9jLAsogtpRJmqaiiF4A-- --BO3lnaN8vO57KVejrGSdlmIo1kMbb5TV3 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 - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlkb/5UACgkQAcXqBBDI oXpvRggAutV+ymmlI802IX9idw4VveDb28H3lP/zs2HBnrCk/bPV9l8gFkfMbzQ7 nwfkHvBa0HgGNg8vE362rORi+ObFmNXbBv/4HoDlZW7pdiSJwUVW261WPFl0FMhe aazbDF81CsJS++qeqXGtuyRwqCG2znELuk9KQk3JbC05aknzVm9D2l1dKFPWSaZa ffjxXwoftPo4oV37nAWfHw+szaz7Hn+PGsRZxYp+37zFQ61Sf9bKwrKhL25OUb0I DQ82npb5HXaXN5KPWyPGH2hCBl1XLiAE/fYPYtKIgNtUC3LDNOqQ2LgtrQGu3W6A R6YdVuxSIQT02a9HILnyAtrAXAWgGA== =4mgq -----END PGP SIGNATURE----- --BO3lnaN8vO57KVejrGSdlmIo1kMbb5TV3--