From nobody Sun Aug 7 12:15:56 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 4M0ywn1SLsz4XktK for ; Sun, 7 Aug 2022 12:16:09 +0000 (UTC) (envelope-from dfr@rabson.org) Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (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 4M0ywm3lZpz3LpT for ; Sun, 7 Aug 2022 12:16:08 +0000 (UTC) (envelope-from dfr@rabson.org) Received: by mail-lf1-x132.google.com with SMTP id x19so920321lfq.7 for ; Sun, 07 Aug 2022 05:16:08 -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=GQ3qTr/OIFryp9MHuOi8YJTkqEBw/u1gr5xpgI9CKPE=; b=c3neC2CgMJyzwVUcA8xQ9+2H1POZgb07TnrRoZNd2/aRl61kmSe0zKTL/0t/PZv4IU C2s4R8t4/BMl54neg6i28ayYZ8954s8WfShF8bB3wSZFHCoVFEabOjEu2sCtTurE1EZw XPGCfYWmCiEGmhH/tSim4DYYRiIUbPC7L5V5+aD9XTnradD8PwYP6S7R/8R6g1Nst0LH SR44Mp77/SnFcJjNKQ6iz3h4/1Zru6QQwQ4AV+rsiKwX5FoIodpmb+Va2Ag6bZWAujZK btXzoBGtOMxYl42xL2QOcTIwc5NZfJ7wm38f5BMPyD/XXz4LGiqebVEo9D0Ij1vx1d2J G51w== 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=GQ3qTr/OIFryp9MHuOi8YJTkqEBw/u1gr5xpgI9CKPE=; b=qIO7+5pHdk13ZNVDG0fpXfmGvGE9cv3hfMSSoq32yl0ArnsHt0J35ioxCM7bRhImg/ WUAyoD/OD0hyLJxWoXKlM3jbm45dUFaY4odlnc3YAI2xmv53g7YQyz8Ag49Uvb/RXDWy /XrbRFGnQ/bmWhC5ukSdrLgqYo0OTiuofabo8VE00l//wbln0zbfanlBWchtC4jM94lO wLP+r0HEEXNuB13lxO1eQr5uK3fFvb7jyjP/7DdUsrhEF8SutYoRMHbSVY0Ds5DRqouF WPKzuQiJ0xJU2tiwEDJrRELTAfEaiKhhc0LqOKI74qjdzNu874G9aDv4ZUOf2lUPe2iD Odog== X-Gm-Message-State: ACgBeo1wlWHvuNA1M3Z2bZ0WPh+tGdDEL+5e06XYxuLfcbV5jfDf5FCb Ed6DoNGHlL793uvGUa3lDWF6b5ZvoIu3xvGkz/f+NgJrfEBmZA== X-Google-Smtp-Source: AA6agR6weGwZOq7MUnv7AAeOH5nO10Q6ex/GG73cxFQ2zhYmsEg0qUcjo1ZpRI58lhqO3mHvpHJwVp0xJDL1TJ/Vxis= X-Received: by 2002:a05:6512:3e12:b0:48a:a64f:7228 with SMTP id i18-20020a0565123e1200b0048aa64f7228mr5330827lfv.159.1659874566944; Sun, 07 Aug 2022 05:16:06 -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> <4F9FB59F-A635-405B-98FF-EF17E9C8BBDA@opnsense.org> In-Reply-To: <4F9FB59F-A635-405B-98FF-EF17E9C8BBDA@opnsense.org> From: Doug Rabson Date: Sun, 7 Aug 2022 13:15:56 +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="000000000000ef545605e5a5a99e" X-Rspamd-Queue-Id: 4M0ywm3lZpz3LpT X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=rabson-org.20210112.gappssmtp.com header.s=20210112 header.b=c3neC2Cg; dmarc=none; spf=pass (mx1.freebsd.org: domain of dfr@rabson.org designates 2a00:1450:4864:20::132 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]; 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::132: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 --000000000000ef545605e5a5a99e Content-Type: text/plain; charset="UTF-8" On Sun, 7 Aug 2022 at 09:04, Franco Fichtner wrote: > > > On 7. Aug 2022, at 9:38 AM, Doug Rabson wrote: > > > > 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. > > Good, but keep in mind that your home lab is not millions of downstream > users. ;) > Of course but this argument is confusing - we are talking about DHCP client, not server. > > 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. > > > Dynamic AAAA records for client leases is a problem, but isn't that also a > general issue with isc-dhcpd? What's your main DHCP server for IPv6? > I'm using the pfSense default DHCP server for both IPV4 and IPV4 - as far as I remember, this is isc-dhcpd and in a previous iteration of my home infra, I had isc-dhcpd working (with dynamic DNS) for both v4 and v6. > > > Again, not seeing the harm for either OPNsense or pfSense - these > distributions are free to choose another client. > > If you want to say "not my work, not my harm" that's possibly fine, but not > well-rounded in a real world setting as indicated by your former status. > I'm saying that the base system's choice of DHCP client has little bearing on pfSense or OPNsense. I don't understand the comment on 'former status'. > > It is still a lot of work to get it working mostly like it did before and > at > least one FreeBSD major release will suffer from the inferiority of > switching > to a new integration. I'm sure disrupting basic IPv4 DHCP capability > which was > always working prior will come as a surprise to people involved in green > lighting > this, but this is likely an unavoidable consequence of the proposal. > Of course, whatever solution we choose for DHCP needs to be integrated properly. To be honest, all I want is a DHCPv6 client integrated in base - I don't care if it's dhcpcd or something else but until we have that, IPv6 is a second class citizen (IMO). Doug. --000000000000ef545605e5a5a99e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


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

> On 7. Aug 2022, at 9:38 AM, Doug Rabson <dfr@rabson.org> wrote:
>
> 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 g= reat, including prefix delegation. Choosing a new dhcp client in FreeBSD ce= rtainly doesn't require {pf,opn}sense to use that client.

Good, but keep in mind that your home lab is not millions of downstream use= rs.=C2=A0 ;)

Of course but this argumen= t is confusing - we are talking about DHCP client, not server.=C2=A0
<= div>=C2=A0
> 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, rts= old is limited to handing advertising the local prefix. Using dhcpcd for bo= th means I get both A and AAAA records in my local DNS which makes me happy= .


Dynamic AAAA records for client leases is a problem, but isn't that als= o a
general issue with isc-dhcpd?=C2=A0 What's your main DHCP server for IP= v6?

I'm using the pfSense default D= HCP server for both IPV4 and IPV4 - as far as I remember, this is isc-dhcpd= and in a previous iteration of my home infra, I had isc-dhcpd working (wit= h dynamic DNS) for both v4 and v6.
=C2=A0

> Again, not seeing the harm for either OPNsense or pfSense - these dist= ributions are free to choose another client.

If you want to say "not my work, not my harm" that's possibly= fine, but not
well-rounded in a real world setting as indicated by your former status.

I'm saying that the base system's= choice of DHCP client has little bearing on pfSense or OPNsense. I don'= ;t understand the comment on 'former status'.
=C2=A0
<= /div>

It is still a lot of work to get it working mostly like it did before and a= t
least one FreeBSD major release will suffer from the inferiority of switchi= ng
to a new integration.=C2=A0 I'm sure disrupting basic IPv4 DHCP capabil= ity which was
always working prior will come as a surprise to people involved in green li= ghting
this, but this is likely an unavoidable consequence of the proposal.

Of course, whatever solution we choose for DH= CP needs to be integrated properly. To be honest, all I want is a DHCPv6 cl= ient integrated in base - I don't care if it's dhcpcd or something = else but until we have that, IPv6 is a second class citizen (IMO).

Doug.

--000000000000ef545605e5a5a99e--