From owner-freebsd-current@freebsd.org Fri Nov 30 16:40:39 2018 Return-Path: Delivered-To: freebsd-current@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 AC4331149040 for ; Fri, 30 Nov 2018 16:40:39 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 28BEB6B8E1 for ; Fri, 30 Nov 2018 16:40:39 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 265B18D4A217; Fri, 30 Nov 2018 16:40:31 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 2B38CD1F857; Fri, 30 Nov 2018 16:40:30 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id NJuolPl1aby3; Fri, 30 Nov 2018 16:40:28 +0000 (UTC) Received: from [192.168.2.110] (unknown [IPv6:fde9:577b:c1a9:31:2ef0:eeff:fe03:ee34]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 717F9D1F878; Fri, 30 Nov 2018 16:40:28 +0000 (UTC) From: "Bjoern A. Zeeb" To: "Christoph Moench-Tegeder" , "O. Hartmann" Cc: freebsd-current@freebsd.org Subject: Re: ipv6/ppp: FreeBSD obtains linklocal on tun0 only Date: Fri, 30 Nov 2018 16:41:02 +0000 X-Mailer: MailMate (2.0BETAr6132) Message-ID: In-Reply-To: <20181130155937.GA74153@elch.exwg.net> References: <20181130131259.1654aee3@thor.intern.walstatt.dynvpn.de> <20181130155937.GA74153@elch.exwg.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 28BEB6B8E1 X-Spamd-Result: default: False [-4.59 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2a01:4f8:13b:39f::9f:25]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zabbadoz.net]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: cross.sbone.de]; NEURAL_HAM_SHORT(-0.96)[-0.962,0]; IP_SCORE(-1.32)[ipnet: 2a01:4f8::/29(-3.92), asn: 24940(-2.67), country: DE(-0.02)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Nov 2018 16:40:39 -0000 On 30 Nov 2018, at 15:59, Christoph Moench-Tegeder wrote: > ## O. Hartmann (ohartmann@walstatt.org): > >> As far as I know, with the IPv4 stack a IPv4 address is obtained >> automatically, so I would expect the same for IPv6. > > The fun with "automatically" is that there's more than one way... > DHCPv6 and NDP (IPV6 Neighbour Discovery Protocol/Router Solicitation) > have been mentioned, the third option is IPV6CP (PPP options, just as > PPP-with-IPv4 does with IPCP). I've no idea what your provider does, so... No, IPV6CP, to my very best 15 year old memory only negotiates the interface identifiers, which are used to generate the link-local addresses. There is no negotiation for full prefix/global addresses, hence it is different to the IPCP NCP used for IPv4. One wants to run rtsol on the link and then depending on the O/M bits possibly also DHCPv6 I’d assume. There’s a couple of other options and shortcuts, on how to configure global addresses (as always, if you know you have a static prefix assigned, one can do it by hand for example); and then there are shortcuts as to when you’d perform DAD, which shouldn’t bother the user. These days there should also be options with regards to RFC4941 (privacy extensions for stateless address autoconf). It may no be uncommon to run the ptp-link with link-local addresses only and configure an address from a prefix on lo0 or the internal interface only; but I am doubtful FreeBSD’s userland implementation is that sophisticated. /bz