From owner-freebsd-net@freebsd.org Wed Nov 21 08:56:50 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31933112D462 for ; Wed, 21 Nov 2018 08:56:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B76A67562C for ; Wed, 21 Nov 2018 08:56:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7AAE4112D461; Wed, 21 Nov 2018 08:56:49 +0000 (UTC) Delivered-To: net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68F5F112D45F for ; Wed, 21 Nov 2018 08:56:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0212D7562B for ; Wed, 21 Nov 2018 08:56:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1CDA11C438 for ; Wed, 21 Nov 2018 08:56:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id wAL8ulOG032586 for ; Wed, 21 Nov 2018 08:56:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id wAL8uloH032584 for net@FreeBSD.org; Wed, 21 Nov 2018 08:56:47 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 233283] IPv6 routing problem when using FreeBSD as a VPS at a cloud provider Date: Wed, 21 Nov 2018 08:56:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Rspamd-Queue-Id: B76A67562C X-Spamd-Result: default: False [0.35 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.12)[-0.124,0]; ASN(0.00)[asn:10310, ipnet:2001:1900:2254::/48, country:US]; NEURAL_SPAM_SHORT(0.61)[0.613,0]; NEURAL_HAM_LONG(-0.14)[-0.138,0] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.29 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, 21 Nov 2018 08:56:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233283 --- Comment #14 from Andrey V. Elsukov --- (In reply to Conrad Meyer from comment #13) > (In reply to Andrey V. Elsukov from comment #7) > Isn't this patch a bit of a kludge? The existing check for the entry in = our > L2 entry cache should be sufficient =E2=80=94 why don't we populate LLE c= ache with > on-link off-prefix routers? >=20 > It's not clear to me the exact ordering, but it seems somehow we get a > router advertisement and insert it into our routing table without populat= ing > the LLE of the sender in the LLE cache. Such route can by added by administrator. The main user's complain is that = for IPv4 you can add route like `route add -host A.B.C.D -iface em0`, but for I= Pv6 this won't work, because you need to have configured prefix on the interfac= e, without the prefix ND6 will think that address on this link is not neighbor, and won't send NS, and you will get ENOBUFS error when try to send a packet= to specified host. This patch adds the check and now the kernel at least will = try to resolve address on the interface. So, in general you are able to add on-link route to your gateway like this: route -6 add -host fd00::1 -iface em0 --=20 You are receiving this mail because: You are the assignee for the bug.=