From nobody Sun Aug 07 05:31:42 2022 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4M0nyd3mxFz4XmWf for ; Sun, 7 Aug 2022 05:32:09 +0000 (UTC) (envelope-from woodsb02@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4M0nyd38Nvz3mFk; Sun, 7 Aug 2022 05:32:09 +0000 (UTC) (envelope-from woodsb02@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1659850329; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type; bh=BS5KwkyQ1GFoK+OEkD4ldP4gfd+gYUZ1+NpgaFswfd0=; b=tG2bCkNYYRSRySmb7q3HMblBZHTlcNL5mHYu9uz5s3xjercNTDhn+hn4L5W/Se3OifQumN 83P96FfBqIudq2KftnZI/PEcFTc3Fjt+qn4P0rcOfgbIWR1qNeaCxQ/fXe2B907RAOYkLG k6hIg5SKlx1QkgTkGCiP1TlfNmIR0ygEo6ANzU/Gydp/qQVSjHEWBpdYw0gKHTLAjW7Zkw qsr5iNtiBE7rdRUVI9Oe0u0kTODvmdF337Gl15hLZM5Fy6ojJ2uUEtwdf4UgEVEn8PChTM m2qfZUbPHNiYXkDffMqd34Q+XBpGdZqlbh1rMuKb/b7GfDp8QP59C78GTpVYsg== Received: from auth2-smtp.messagingengine.com (auth2-smtp.messagingengine.com [66.111.4.228]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: woodsb02) by smtp.freebsd.org (Postfix) with ESMTPSA id 4M0nyd20Snz1LML; Sun, 7 Aug 2022 05:32:09 +0000 (UTC) (envelope-from woodsb02@freebsd.org) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailauth.nyi.internal (Postfix) with ESMTP id 9ADF827C0054; Sun, 7 Aug 2022 01:32:08 -0400 (EDT) Received: from imap46 ([10.202.2.96]) by compute2.internal (MEProxy); Sun, 07 Aug 2022 01:32:08 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdefgedgleejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfffhffvvefutgesrgdtre erreerjeenucfhrhhomhepfdeuvghnucghohhoughsfdcuoeifohhoughssgdtvdesfhhr vggvsghsugdrohhrgheqnecuggftrfgrthhtvghrnhepveegueffuddvtddthedthfdvtd dvjefhgfffueehhfevgefghfevgeeuleeiuddvnecuffhomhgrihhnpehfrhgvvggsshgu rdhorhhgpdhgihhthhhusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrh grmhepmhgrihhlfhhrohhmpegsvghnodhmvghsmhhtphgruhhthhhpvghrshhonhgrlhhi thihqddutdelfeeiiedvkeekqddvgeejkedvvdektddqfihoohgushgstddvpeepfhhrvg gvsghsugdrohhrghesfihoohgushdrrghm X-ME-Proxy: Feedback-ID: if9c9472a:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 5365B2A20075; Sun, 7 Aug 2022 01:32:08 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-758-ge0d20a54e1-fm-20220729.001-ge0d20a54 List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org Mime-Version: 1.0 Message-Id: Date: Sun, 07 Aug 2022 13:31:42 +0800 From: "Ben Woods" To: freebsd-net@freebsd.org Cc: emaste@freebsd.org, roy@marples.name, hrs@freebsd.org, brooks@freebsd.org, cy@freebsd.org, "Philip Paeps" Subject: Import dhcpcd(8) into FreeBSD base Content-Type: multipart/alternative; boundary=4ac2e87f860c42b1a90fd5385279aaf3 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1659850329; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type; bh=BS5KwkyQ1GFoK+OEkD4ldP4gfd+gYUZ1+NpgaFswfd0=; b=KW6IJdRkPPLHUZIl/wAUq895YctudGGAHgf0XTBOVMYRSPA97EI2bh8k+zxn72ZiKOvVcd +kJJmhgrMNYGB8I5RkU7JSmXjQldIgSFvVn8Jt6NZwCQrde1KpZcEqPVOH4NoZdJhZn5dZ b5Axde/yQFRLL3UkX+al/Pa5NzunCqXgyVumCRdJg8s1eFB2iU/j5MUbgmoWlDInvqFknD wtkOdgTxpnyEWB5rcwdU0yPkM0/MOPYT3WOBPuiHuMh1jO8cm/D/Lw+lXtSRKrTBq9i+dU Y8FyApVJMSAAh9qUNnrwBozoYRvGbKkqxCWs3fiCawcZ04W3y2+hKb905HaElA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1659850329; a=rsa-sha256; cv=none; b=aHQsSV8YRxwS/vdPiA5qdfZe1QcWoSH+n6n50OWIg7fnTMLhS9oAijY7mB88wuJQb30ygQ u+bCIs1JhpE9aNUvLRD0U9Vg/kL/b5KTMverZEYGuFJ/f2HzoyQ2FVqffLVrBPL2JGDClm mCYqZfEyK8099AkxIT2Mdd+XS/HtVBHVBvOGlqBtl0WMxJNpZlh83vnzN5Lp8goZs65XyD OmwU2og6O9p7eQaoYDJSXdQ+NE2NlBn9JQqxnutY39VNkj25F4cgFnGfhxlMU1yPunsAsY SI2mmPhcg0IIXtEzeBBhzAboKze+u6ek/0LAni4c4XUzqEZFiSei7PvtNrO9Xw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N --4ac2e87f860c42b1a90fd5385279aaf3 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi freebsd-net, I would like to propose dhcpcd is imported into FreeBSD base. Reason: ensure fresh installs of FreeBSD support using DHCPv6 and prefix= delegation to obtain an IP address (not supported by dhclient or rtsold= ). Having it in ports/packages could be problematic if people cannot obt= ain an IPv6 address to download it. Why dhcpcd vs other DHCPv6 clients? It=E2=80=99s well supported, full fe= atured, included in NetBSD and DragonflyBSD base, and is now sandboxed w= ith capsicum. The other DHCP clients tend to either not support DHCPv6 (= dhcpleased) or are no longer actively maintained (wide-dhcpv6-client). For those not familiar with dhcpcd, it=E2=80=99s a DHCP client, not serv= er. It can be run either in master mode (single instances manages DHCPv4= and DHCPv6 on all available network interfaces unless disabled in confi= g), or single interface mode if preferred. This was discussed once before on this mailing list in 2019, and I=E2=80= =99ve had a review open on phabricator for a few years. The main technic= al concern raised (capsicum sandboxing) was resolved upstream with the d= hcpcd 9.1.0 release in May 2020. What is perhaps missing is the broader = community agreement of the change and forward plan. If accepted, I would recommend a phased implementation such as that sugg= ested below - open to ideas. - 14.0 (and perhaps 13.2) - dhcpcd included but off by default (WITH_DHC= PCD=3Don, but rc.conf/network.subr continue to use dhclient/rtsold). Rel= ease notes list forward plan. - 14.1 - switch defaults in rc.conf/network.subr to use dhcpcd instead o= f dhclient/rtsold. Subject to any issues being addressed prior. Release = notes could list deprecation of dhclient/rtsold - this deprecation step = could be done slower if desired. - 15.0 - remove dhclient/rtsold - again, could be done slower if desired. I=E2=80=99d be keen to hear the thoughts of the community. If you want t= o try out dhcpcd today, it=E2=80=99s available in ports/packages. I should point out that I have a ports commit bit - not src. If accepted= , I=E2=80=99d either need a src committer to land it, or approve me comm= itting (via phabricator). https://reviews.freebsd.org/D22012 https://github.com/NetworkConfiguration/dhcpcd Regards, Ben -- From: Ben Woods woodsb02@freebsd.org --4ac2e87f860c42b1a90fd5385279aaf3 Content-Type: text/html;charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi freebsd-net,=

I would like to propose dhcpcd is imported= into FreeBSD base.

Reason: ensure fresh in= stalls of FreeBSD support using DHCPv6 and prefix delegation to obtain a= n IP address (not supported by dhclient or rtsold). Having it in ports/p= ackages could be problematic if people cannot obtain an IPv6 address to = download it.

Why dhcpcd vs other DHCPv6 cli= ents? It=E2=80=99s well supported, full featured, included in NetBSD and= DragonflyBSD base, and is now sandboxed with capsicum. The other DHCP c= lients tend to either not support DHCPv6 (dhcpleased) or are no longer a= ctively maintained (wide-dhcpv6-client).

Fo= r those not familiar with dhcpcd, it=E2=80=99s a DHCP client, not server= . It can be run either in master mode (single instances manages DHC= Pv4 and DHCPv6 on all available network interfaces unless disabled in co= nfig), or single interface mode if preferred.

This was discussed once before on this mailing list in 2019, and I=E2= =80=99ve had a review open on phabricator for a few years. The main tech= nical concern raised (capsicum sandboxing) was resolved upstream with th= e dhcpcd 9.1.0 release in May 2020. What is perhaps missing is the broad= er community agreement of the change and forward plan.
If accepted, I would recommend a phased implementation such = as that suggested below - open to ideas.

- = 14.0 (and perhaps 13.2) - dhcpcd included but off by default (WITH_DHCPC= D=3Don, but rc.conf/network.subr=  continue to use dhclient/rtsold). Release notes list forward p= lan.

- 14.1 - switch defaults in rc.conf/network.subr to use dhcpc= d instead of dhclient/rtsold. Subject to any issues being addressed prio= r. Release notes could list deprecation of dhclient/rtsold - this deprec= ation step could be done slower if desired.

- 15.0 - remove dhclient/rtsold - again, could be done slower if desire= d.

I=E2=80=99d be keen to hear the thoughts= of the community. If you want to try out dhcpcd today, it=E2=80=99s ava= ilable in ports/packages.

I should point ou= t that I have a ports commit bit - not src. If accepted, I=E2=80=99d eit= her need a src committer to land it, or approve me committing (via phabr= icator).


Regards,
Ben

--
From: Ben Woods
woods= b02@freebsd.org

--4ac2e87f860c42b1a90fd5385279aaf3--