From owner-freebsd-bugs@freebsd.org Sat Aug 12 20:19:19 2017 Return-Path: Delivered-To: freebsd-bugs@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 A8282DC7CD1 for ; Sat, 12 Aug 2017 20:19:19 +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 mx1.freebsd.org (Postfix) with ESMTPS id 961C46FE5B for ; Sat, 12 Aug 2017 20:19:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7CKJJpn040539 for ; Sat, 12 Aug 2017 20:19:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 221445] The absence of the accept_rtadv option causes an error "ping6: sendmsg: No buffer space available" Date: Sat, 12 Aug 2017 20:19:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: admin@support.od.ua X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@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-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 20:19:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221445 --- Comment #4 from Vladislav V. Prodan --- (In reply to Andrey V. Elsukov from comment #3) >> Read the description of the bug again. >> I described how I managed to get the ipv6 to work. >It is wrong, and this is why it doesn't work. It's someone who did not quite correctly implement the IPv6 implementation = in FreeBSD. I can give a working example for Debian, there is the same crutch in the destination route for the default router. >> ifconfig_em0_ipv6=3D"inet6 2001:41d0:e:XXX::1/128" >What is the reason of /128 prefix length? So decided marketers in the OVH. I already pointed out to them that there a= re a number of vulnerabilities related to the substitution of IPv6 addresses. Personally, I only need one ipv6 address. >> ipv6_static_routes=3D"ipv6gw" >> ipv6_route_ipv6gw=3D"-host 2001:41d0:000e:03ff:ff:ff:ff:ff -iface em0" >This will not work on FreeBSD due to implementation specificity.=20 Why not? It works the same. # netstat -rn6 Routing tables Internet6: Destination Gateway Flags N= etif Expire ::/96 ::1 UGRS = lo0 default fe80::12bd:18ff:fee5:ff80%em0 UG = em0 ::1 link#2 UH = lo0 ::ffff:0.0.0.0/96 ::1 UGRS = lo0 2001:41d0:e:XXX::/56 link#1 U = em0 2001:41d0:e:XXX::1 link#1 UHS = lo0 ... 2001:41d0:e:3ff:ff:ff:ff:ff 00:22:4d:ad:ff:dc UHS = em0 ... fe80::/10 ::1 UGRS = lo0 fe80::%em0/64 link#1 U = em0 fe80::222:4dff:fead:ffdc%em0 link#1 UHS = lo0 fe80::%lo0/64 link#2 U = lo0 fe80::1%lo0 link#2 UHS = lo0 ff02::/16 ::1 UGRS = lo0 >When the kernel is going to send IPv6 packet, it does L2 lookup to determi= ne L2 address. ND6 code does lookup for destination address only when an ad= dress is considered as neighbor. When you have not configured the correct p= refix, the ND6 has not any interfaces where the destination address can be = considered as neighbor. In your case even the L2 address of default router = can not be found. Honestly, I do not care how ND6 is implemented in FreeBSD. I have issued a static IPv6 address with a given mask. I have an IPv6 router address by default. So what if he's not in the L2 segment? The network interface, where this Ip= v6 is located, I know. Next, with these packages, the switches and routers of = the hoster will be sorted out. I have a typical network scheme for many hosters dedicated servers. I have a test machine with which I can work for a while to correct this abnormal behavior. If you have the time and the desire to eliminate this, in personal correspondence I will provide access to the server. --=20 You are receiving this mail because: You are the assignee for the bug.=