Date: Sun, 7 Aug 2022 08:38:52 +0100 From: Doug Rabson <dfr@rabson.org> To: Franco Fichtner <franco@opnsense.org> Cc: Ben Woods <woodsb02@freebsd.org>, FreeBSD Net <freebsd-net@freebsd.org>, emaste@freebsd.org, roy@marples.name, Hiroki Sato <hrs@freebsd.org>, brooks@freebsd.org, cy@freebsd.org, Philip Paeps <philip@freebsd.org> Subject: Re: Import dhcpcd(8) into FreeBSD base Message-ID: <CACA0VUicpWgOjdxkLM0DmiX94M2OaYnEns9BbCfz9_Z5VQ_CVA@mail.gmail.com> In-Reply-To: <9831CA1D-1AE2-4B46-A781-D6B98BECDFBA@opnsense.org> References: <e401671f-6a67-49ed-bc41-e8fbb9de27cb@www.fastmail.com> <9831CA1D-1AE2-4B46-A781-D6B98BECDFBA@opnsense.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000019ac6805e5a1cb9a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
On Sun, 7 Aug 2022 at 08:08, Franco Fichtner <franco@opnsense.org> wrote:
> Hi Ben,
>
> > On 7. Aug 2022, at 7:31 AM, Ben Woods <woodsb02@FreeBSD.org> 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
<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sun, 7 Aug 2022 at 08:08, Franco F=
ichtner <<a href=3D"mailto:franco@opnsense.org">franco@opnsense.org</a>&=
gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-colo=
r:rgb(204,204,204);padding-left:1ex">Hi Ben,<br>
<br>
> On 7. Aug 2022, at 7:31 AM, Ben Woods <woodsb02@FreeBSD.org> wro=
te:<br>
> <br>
> 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.<br>
> <br>
> 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).<br>
<br>
Having worked on dhclient and rtsold in FreeBSD and worked with it for year=
s<br>
in pfSense/OPNsense the proposal here seems to be to throw all progress awa=
y<br>
that would definitely have to be rebuilt in the years to follow for the all=
-<br>
in-one (?) replacement.<br></blockquote><div><br></div><div>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.</div><div>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-w=
idth:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding=
-left:1ex">
<br>
For OPNsense we did fork strip down and improve wide-dhcpv6 over the years:=
<br>
<br>
<a href=3D"https://github.com/opnsense/dhcp6c" rel=3D"noreferrer" target=3D=
"_blank">https://github.com/opnsense/dhcp6c</a><br>;
<br>
It could use more work and cleanups, but basically all that is required is =
to<br>
bring it into FreeBSD and use it to skip a long trail of said future work b=
oth<br>
in dhcpcd and putting back existing perks of the current dhclient and rtsol=
d.<br>
<br>
The basic question is: what's not working in dhclident? How is rtsold i=
nferior?<br></blockquote><div><br></div><div>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.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;borde=
r-left-color:rgb(204,204,204);padding-left:1ex">
<br>
It seems like "It=E2=80=99s well supported, full featured, included in=
NetBSD and<br>
DragonflyBSD base" incorporates none of the real world concerns for mi=
gratory<br>
work so for the time being I don't think it's a solid proposal, als=
o because<br>
it will cause heavy downstream disruption in OPNsense/pfSense in a few year=
s<br>
as well.<br></blockquote><div><br></div><div>Again, not seeing the harm for=
either OPNsense or pfSense - these distributions are free to choose anothe=
r client.</div><div>=C2=A0</div></div></div>
--00000000000019ac6805e5a1cb9a--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACA0VUicpWgOjdxkLM0DmiX94M2OaYnEns9BbCfz9_Z5VQ_CVA>