From owner-freebsd-net@freebsd.org Wed May 15 19:43:41 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 CE596159FCEA for ; Wed, 15 May 2019 19:43:40 +0000 (UTC) (envelope-from hrs@allbsd.org) Received: from mail.allbsd.org (mx.allbsd.org [IPv6:2001:2f0:104:e001::41]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.allbsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 01B5D6E457 for ; Wed, 15 May 2019 19:43:39 +0000 (UTC) (envelope-from hrs@allbsd.org) Received: from mail-d.allbsd.org ([IPv6:2409:11:a740:4700:58:65ff:fe00:b0b]) (authenticated bits=56) by mail.allbsd.org (8.15.2/8.15.2) with ESMTPSA id x4FJh7iR083494 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) (Client CN "/CN=mail.allbsd.org", Issuer "/C=US/O=Let's+20Encrypt/CN=Let's+20Encrypt+20Authority+20X3"); Thu, 16 May 2019 04:43:17 +0900 (JST) (envelope-from hrs@allbsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=allbsd.org; s=20190220; t=1557949414; bh=k/Usp9CQZZUSLRvZOBriygGlykl/woJ0I1qW/WQGHPU=; h=Date:To:Cc:Subject:From:In-Reply-To:References; b=bdOMGeQUx3U6kgLJO7PG5tIkOJ6sgxr32k2gsXYxwfA6ooa0KqoUg8/MOK9ubZy+F gYGs9EAYmyBdRJW5doh4ZtbHY//8tFp4/rQNJrqwrUqeL8BEVjN/8UT3HotYLZrpfy b332vEvn5yOylQQuhRFAJA79hnjRimuHpA6d6oOE= Received: from alph.d.allbsd.org ([IPv6:2409:11:a740:4700:16:ceff:fe34:2700]) by mail-d.allbsd.org (8.15.2/8.15.2) with ESMTPS id x4FJh2FP072332 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 16 May 2019 04:43:02 +0900 (JST) (envelope-from hrs@allbsd.org) Received: from localhost (localhost [[UNIX: localhost]]) (authenticated bits=0) by alph.d.allbsd.org (8.15.2/8.15.2) with ESMTPA id x4FJh0b1072328; Thu, 16 May 2019 04:43:01 +0900 (JST) (envelope-from hrs@allbsd.org) Date: Thu, 16 May 2019 04:42:52 +0900 (JST) Message-Id: <20190516.044252.1672818225777964175.hrs@allbsd.org> To: driesm.michiels@gmail.com Cc: freebsd-net@freebsd.org Subject: Re: DHCPv6 client in base From: Hiroki Sato In-Reply-To: <006001d50b53$72a22e00$57e68a00$@gmail.com> References: <001e01d50b49$176104d0$46230e70$@gmail.com> <20190516.032012.517661495892269813.hrs@allbsd.org> <006001d50b53$72a22e00$57e68a00$@gmail.com> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Thu_May_16_04_42_52_2019_627)--" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mail.allbsd.org [IPv6:2001:2f0:104:e001:0:0:0:41]); Thu, 16 May 2019 04:43:26 +0900 (JST) X-Spam-Status: No, score=2.7 required=13.0 tests=CONTENT_TYPE_PRESENT, QENCPTR1, RCVD_IN_AHBL,RCVD_IN_AHBL_PROXY,RCVD_IN_AHBL_SPAM,RDNS_NONE, UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.2 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mx.allbsd.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, 15 May 2019 19:43:41 -0000 ----Security_Multipart(Thu_May_16_04_42_52_2019_627)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit wrote in <006001d50b53$72a22e00$57e68a00$@gmail.com>: dr> > I have a plan to import wide-dhcp6 into the base system because it is simple dr> > 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 and one physical from a 56 delegation. dr> For this config it errors out on parsing the config file ... while 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 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? -- Hiroki ----Security_Multipart(Thu_May_16_04_42_52_2019_627)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iEYEABECAAYFAlzca7wACgkQTyzT2CeTzy1sPQCgoE4pUN3kJ/L4777a2k0iZQpw N0kAn1TVwDiwddUIEfnwbSWMCCtEUQl0 =YUWe -----END PGP SIGNATURE----- ----Security_Multipart(Thu_May_16_04_42_52_2019_627)----