From owner-freebsd-net@freebsd.org Wed May 15 19:53:58 2019 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 9C04915A03DD for ; Wed, 15 May 2019 19:53:58 +0000 (UTC) (envelope-from driesm.michiels@gmail.com) Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 864086ED0A for ; Wed, 15 May 2019 19:53:56 +0000 (UTC) (envelope-from driesm.michiels@gmail.com) Received: by mail-ed1-x531.google.com with SMTP id w11so1509348edl.5 for ; Wed, 15 May 2019 12:53:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:content-language :thread-index; bh=/yfKUT7RXHHUKL9bKWH6Ll1nBR0UoNnazcoNlHfdP8c=; b=Ea+Nkz7KwQbxUxNVypftSClJlOXJg/cKUQ328xc2gr2Uaq1SMWD1ffK5NCX49/rC16 KIW4774sXSr23K0nybDPOcIdEEZmB7jcZyoXwyqdSzciBRreR3SU8KkKf7l4WFuWrdsU U2m6cc91kV+zCIqDakSIrYFSf1MUu5b9otjD92qOqK7HPSFvpOYZqhjExrQOZfeAJyU0 qthWmNQe5a0gNrHdJGJO+OO3Nd4lKUlSFNV6D5elVTt2He1WBKHIrvOZZeLL1pY23EXf RGU6boYo20NWSlBT+DhG+FGgxFcnAJiK56YXTDhwKSQS+7z2St2RGvtqWPJ0j0VWF7Kw u8Aw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:content-language :thread-index; bh=/yfKUT7RXHHUKL9bKWH6Ll1nBR0UoNnazcoNlHfdP8c=; b=QGbeeN3+d77Q5Ht4TDxifw6NESPbergJah5MZpG3OZMkSAZUPtAhJNDLcbmYlMN2he iABhIhI0pAjTkeJ4fhqBW8rjXugOjSjB2lLtzuQFIzGTrm1Mp6eQZMBJsa1259Ct0rt+ 1CGvpDx5ODh5Pe1abiRsh7LyFWSweJlcSgmeJEtXCWmhVkQPqjZf59ZybUMS4Ly1icuq RHQfMbWMtvG4Mj82redNahl3javzdUXYYFVYTWq6HofCNPtekrrLlnAC/23zSCXgLK2E iEGalg83GAGvDDarLno0NXJHjIigNNY89pK9wkbiSD0Fz4NCtsovblHGF4c1mxgHBDVY q32w== X-Gm-Message-State: APjAAAWAnbULBuUqjrS8C/aeVMpf1FIwBo4n4VIE0fgyFDz7LnVmhdpH dSuFhDwegDs1uhcTxm2UVfFHaDR4/8s= X-Google-Smtp-Source: APXvYqxQ6dfpwGwBCbr7BGlNERJ2Ro0LhAzcauuF6Cu1asueZ/shFcEmfs+Hb93+OYCW+8qq7NEawQ== X-Received: by 2002:a17:906:b20f:: with SMTP id p15mr23723571ejz.63.1557950034925; Wed, 15 May 2019 12:53:54 -0700 (PDT) Received: from DRIESPC (d8D874847.access.telenet.be. [141.135.72.71]) by smtp.gmail.com with ESMTPSA id d28sm630170ejl.83.2019.05.15.12.53.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 May 2019 12:53:54 -0700 (PDT) From: To: "'Hiroki Sato'" Cc: References: <001e01d50b49$176104d0$46230e70$@gmail.com> <20190516.032012.517661495892269813.hrs@allbsd.org> <006001d50b53$72a22e00$57e68a00$@gmail.com> <20190516.044252.1672818225777964175.hrs@allbsd.org> <00aa01d50b57$c84ac020$58e04060$@gmail.com> In-Reply-To: <00aa01d50b57$c84ac020$58e04060$@gmail.com> Subject: RE: DHCPv6 client in base Date: Wed, 15 May 2019 21:53:55 +0200 Message-ID: <00b101d50b57$edf75f90$c9e61eb0$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Content-Language: nl-be Thread-Index: AQLaN40i822Fq698RgLAgw7TO9S4zQG9t3h7Ai5ldU4BtRebPwJCxfmvpCMgt7A= X-Rspamd-Queue-Id: 864086ED0A X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Ea+Nkz7K; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of driesmmichiels@gmail.com designates 2a00:1450:4864:20::531 as permitted sender) smtp.mailfrom=driesmmichiels@gmail.com X-Spamd-Result: default: False [-6.73 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-1.00)[-0.998,0]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-2.73)[ip: (-9.10), ipnet: 2a00:1450::/32(-2.20), asn: 15169(-2.26), country: US(-0.06)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-net@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NO_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[1.3.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0] 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, 15 May 2019 19:53:58 -0000 > -----Original Message----- > From: driesm.michiels@gmail.com > Sent: woensdag 15 mei 2019 21:53 > To: 'Hiroki Sato' > Cc: freebsd-net@freebsd.org > Subject: RE: DHCPv6 client in base >=20 > > -----Original Message----- > > From: Hiroki Sato > > Sent: woensdag 15 mei 2019 21:43 > > To: driesm.michiels@gmail.com > > Cc: freebsd-net@freebsd.org > > Subject: Re: DHCPv6 client in base > > > > wrote > > in <006001d50b53$72a22e00$57e68a00$@gmail.com>: > > > > dr> > I have a plan to import wide-dhcp6 into the base system = because > > dr> > it is simple enough. > > dr> > > dr> Thats nice! Any timeline for this; 13.0 RELEASE? > > > > Yes, at the latest. I originally planned it before 12.0 but not > > happened for some non-technical reasons. > > > > dr> > More specifics about the complex configuration? > > dr> > > dr> My initial wording wasn't correct; wide-dhcp is in fact = featureful > > although buggy when config files get a bit bigger. > > dr> Well I'm trying to assign a 64 prefix to two virtual interfaces > > dr> and one > > physical from a 56 delegation. > > dr> For this config it errors out on parsing the config file ... = while > > dr> I'm 99% > > certain there is not a problem in it. > > dr> > > dr> interface em0 { > > dr> send rapid-commit; > > dr> send ia-na 1; > > dr> send ia-pd 1; > > dr> }; > > dr> > > dr> id-assoc na 1 { }; > > dr> > > dr> id-assoc pd 1 { > > dr> prefix ::/56 infinity; > > dr> prefix-interface igb0 { > > dr> sla-id 0; > > dr> sla-len 8; > > dr> }; > > dr> prefix-interface lo1 { > > dr> sla-id 1; > > dr> sla-len 8; > > dr> }; > > dr> prefix-interface tun0 { > > dr> sla-id 2; > > dr> sla-len 8; > > dr> }; > > dr> }; > > dr> > > dr> May 15 21:20:50 May 15 21:20:50 vados dhcp6c[94383]: failed to > > dr> parse configuration file > > > > In this configuration dhcp6c does not work because lo1 has no L2 > > address to generate an interface ID which will be used with the /64 > > prefix. Is there any specific reason why you want to use a loopback > interface? >=20 > I was planning to use the prefix on lo1 as the ext_if argument in an = IPFW > NPTv6 rule. > That would translate my private jail addresses to their corresponding = global > ones from the prefix. > I know its possible with VIMAGE to just run rtadvd on a bridge but I = rather > stay away from that, one rule in IPFW is all I need. Was planning a similar setup for my OpenVPN clients on the tun0 = interface. >=20 > > > > -- Hiroki