From nobody Sun Aug 07 07:38:52 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 4M0rn630qYz4Y4sD for ; Sun, 7 Aug 2022 07:39:06 +0000 (UTC) (envelope-from dfr@rabson.org) Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4M0rn553S3z3wJr for ; Sun, 7 Aug 2022 07:39:05 +0000 (UTC) (envelope-from dfr@rabson.org) Received: by mail-lj1-x22a.google.com with SMTP id x25so7038158ljm.5 for ; Sun, 07 Aug 2022 00:39:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rabson-org.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=x8A6885xCWV8ujnCIcVV3DdCtnh7Ii0maYFfCht2qRU=; b=6izRL2EPBGjC+jfdy7mOFlkx+vjWKxfMZJjjx6khtVnOA3DCHnnlvsAuSOBQSppYPc RhZa5X4WX9fRHgmEnyvyyLdmLGqt14aFZVjqKvf3WCBdmpwwsxUePsaojgKF5Ou12E/R n15ggNAfY9+dcMez8Um5w6wU43I6wUBzdwFctyWWrysEdfQEtOoszjll6vGOUmgAOw/Y WrK5xuzXlxkUjM0FRqhMenljIVdEBqXEOIwvxuLanFmddQoz+BQYXiqx1F7Wc7tykK8C m6PAgqO3x3qnc3cetHwvuI3pxCnIPmr4xQx0cRQ17m2+D406lYw6XqykxGdGt8CNLc9m etiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=x8A6885xCWV8ujnCIcVV3DdCtnh7Ii0maYFfCht2qRU=; b=DYYv0fcSi1r22K+U+OBJQRe6r3c4ev3bY3ST7bbWPLAvT/wiEmLzG+hP54jPRQk+Tm G5ULR+XblS5xObQk6laL8SwohvKmTmDvVyl7qWIdeGsHu1vJ4hXdAcqlQeLfd5ORolxb wx2VV9AuKkMfPb4WfMvCwV64ufCJLRhAfQAbFzMSwdwyW+ueJeKdTR/nkPwQzeSlK4Q4 b5Ex/6//5iLHGgEQ633fJ/EoZHNNIQcHU7Gk/9zkl0pv0BX5t8f2YPmO0LXe01PxXx8k DovwsQnZVz2dI1EpXqlEC2IHqM1+9EFNpklveCbEHGcj69zeanP/XXGg/Pghxexlff76 TRnA== X-Gm-Message-State: ACgBeo2OcFiA+8Y5JGn55fkSwWThSpDRs+TAsHWZlPZ4Vhaq55UfHuBd dPwK8rSpbjTlYikzkLoOWHiMTTVGnWOErkzRISryqOq+RXdY5g== X-Google-Smtp-Source: AA6agR6LGCsz7vzS/VRlAX7v2SIBlPPq6JE0NnhrjPgFja3hKctCkD4LRzf9WMxnCVPtd8nuGtuIFgiz/hl7Zjig4ss= X-Received: by 2002:a2e:bd89:0:b0:25a:86c8:93ca with SMTP id o9-20020a2ebd89000000b0025a86c893camr3969375ljq.419.1659857943498; Sun, 07 Aug 2022 00:39:03 -0700 (PDT) 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 References: <9831CA1D-1AE2-4B46-A781-D6B98BECDFBA@opnsense.org> In-Reply-To: <9831CA1D-1AE2-4B46-A781-D6B98BECDFBA@opnsense.org> From: Doug Rabson Date: Sun, 7 Aug 2022 08:38:52 +0100 Message-ID: Subject: Re: Import dhcpcd(8) into FreeBSD base To: Franco Fichtner Cc: Ben Woods , FreeBSD Net , emaste@freebsd.org, roy@marples.name, Hiroki Sato , brooks@freebsd.org, cy@freebsd.org, Philip Paeps Content-Type: multipart/alternative; boundary="00000000000019ac6805e5a1cb9a" X-Rspamd-Queue-Id: 4M0rn553S3z3wJr X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=rabson-org.20210112.gappssmtp.com header.s=20210112 header.b=6izRL2EP; dmarc=none; spf=pass (mx1.freebsd.org: domain of dfr@rabson.org designates 2a00:1450:4864:20::22a as permitted sender) smtp.mailfrom=dfr@rabson.org X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; R_DKIM_ALLOW(-0.20)[rabson-org.20210112.gappssmtp.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[freebsd-net@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::22a:from]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_SEVEN(0.00)[9]; ARC_NA(0.00)[]; DMARC_NA(0.00)[rabson.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[dfr]; DKIM_TRACE(0.00)[rabson-org.20210112.gappssmtp.com:+]; TO_DN_SOME(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; PREVIOUSLY_DELIVERED(0.00)[freebsd-net@freebsd.org]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N --00000000000019ac6805e5a1cb9a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, 7 Aug 2022 at 08:08, Franco Fichtner wrote: > Hi Ben, > > > On 7. Aug 2022, at 7:31 AM, Ben Woods wrote: > > > > Reason: ensure fresh installs of FreeBSD support using DHCPv6 and prefi= x > delegation to obtain an IP address (not supported by dhclient or rtsold). > Having it in ports/packages could be problematic if people cannot obtain = an > IPv6 address to download it. > > > > Why dhcpcd vs other DHCPv6 clients? It=E2=80=99s well supported, full f= eatured, > included in NetBSD and DragonflyBSD base, and is now sandboxed with > capsicum. The other DHCP clients tend to either not support DHCPv6 > (dhcpleased) or are no longer actively maintained (wide-dhcpv6-client). > > Having worked on dhclient and rtsold in FreeBSD and worked with it for > years > in pfSense/OPNsense the proposal here seems to be to throw all progress > away > that would definitely have to be rebuilt in the years to follow for the > all- > in-one (?) replacement. > I'm not sure what the problem is here? I'm using dhcpcd client in my home lab with pfsense acting as dhcp and dhcp6 server and it works great, including prefix delegation. Choosing a new dhcp client in FreeBSD certainly doesn't require {pf,opn}sense to use that client. > > For OPNsense we did fork strip down and improve wide-dhcpv6 over the year= s: > > https://github.com/opnsense/dhcp6c > > It could use more work and cleanups, but basically all that is required i= s > to > bring it into FreeBSD and use it to skip a long trail of said future work > both > in dhcpcd and putting back existing perks of the current dhclient and > rtsold. > > The basic question is: what's not working in dhclident? How is rtsold > inferior? > Main thing that's missing for me is dynamic dns - my dhcp server updates my local DNS using ddns. This works well for ipv4 and I've been using it this way for years. For ipv6, rtsold is limited to handing advertising the local prefix. Using dhcpcd for both means I get both A and AAAA records in my local DNS which makes me happy. > > It seems like "It=E2=80=99s well supported, full featured, included in Ne= tBSD and > DragonflyBSD base" incorporates none of the real world concerns for > migratory > work so for the time being I don't think it's a solid proposal, also > because > it will cause heavy downstream disruption in OPNsense/pfSense in a few > years > as well. > Again, not seeing the harm for either OPNsense or pfSense - these distributions are free to choose another client. --00000000000019ac6805e5a1cb9a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, 7 Aug 2022 at 08:08, Franco F= ichtner <franco@opnsense.org&= gt; wrote:
Hi Ben,

> On 7. Aug 2022, at 7:31 AM, Ben Woods <woodsb02@FreeBSD.org> wro= te:
>
> Reason: ensure fresh installs of FreeBSD support using DHCPv6 and pref= ix delegation to obtain an IP address (not supported by dhclient or rtsold)= . Having it in ports/packages could be problematic if people cannot obtain = an IPv6 address to download it.
>
> Why dhcpcd vs other DHCPv6 clients? It=E2=80=99s well supported, full = featured, included in NetBSD and DragonflyBSD base, and is now sandboxed wi= th capsicum. The other DHCP clients tend to either not support DHCPv6 (dhcp= leased) or are no longer actively maintained (wide-dhcpv6-client).

Having worked on dhclient and rtsold in FreeBSD and worked with it for year= s
in pfSense/OPNsense the proposal here seems to be to throw all progress awa= y
that would definitely have to be rebuilt in the years to follow for the all= -
in-one (?) replacement.

I'm not sur= e what the problem is here? I'm using dhcpcd client in my home lab with= pfsense acting as dhcp and dhcp6=C2=A0server and it works great, including= prefix delegation. Choosing a new dhcp client in FreeBSD certainly doesn&#= 39;t require {pf,opn}sense to use that client.
=C2=A0

For OPNsense we did fork strip down and improve wide-dhcpv6 over the years:=

https://github.com/opnsense/dhcp6c

It could use more work and cleanups, but basically all that is required is = to
bring it into FreeBSD and use it to skip a long trail of said future work b= oth
in dhcpcd and putting back existing perks of the current dhclient and rtsol= d.

The basic question is: what's not working in dhclident? How is rtsold i= nferior?

Main thing that's missing = for me is dynamic dns - my dhcp server updates my local DNS using ddns. Thi= s works well for ipv4 and I've been using it this way for years. For ip= v6, rtsold is limited to handing advertising the local prefix. Using dhcpcd= for both means I get both A and AAAA records in my local DNS which makes m= e happy.
=C2=A0

It seems like "It=E2=80=99s well supported, full featured, included in= NetBSD and
DragonflyBSD base" incorporates none of the real world concerns for mi= gratory
work so for the time being I don't think it's a solid proposal, als= o because
it will cause heavy downstream disruption in OPNsense/pfSense in a few year= s
as well.

Again, not seeing the harm for= either OPNsense or pfSense - these distributions are free to choose anothe= r client.
=C2=A0
--00000000000019ac6805e5a1cb9a--