Date: Sun, 7 Aug 2022 13:15:56 +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: <CACA0VUgF8ojK70MKdAjLkabxD-_2iF9A88xYnShL0Znfw12qgg@mail.gmail.com> In-Reply-To: <4F9FB59F-A635-405B-98FF-EF17E9C8BBDA@opnsense.org> References: <e401671f-6a67-49ed-bc41-e8fbb9de27cb@www.fastmail.com> <9831CA1D-1AE2-4B46-A781-D6B98BECDFBA@opnsense.org> <CACA0VUicpWgOjdxkLM0DmiX94M2OaYnEns9BbCfz9_Z5VQ_CVA@mail.gmail.com> <4F9FB59F-A635-405B-98FF-EF17E9C8BBDA@opnsense.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Sun, 7 Aug 2022 at 09:04, Franco Fichtner <franco@opnsense.org> 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 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.
[-- Attachment #2 --]
<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, 7 Aug 2022 at 09:04, Franco Fichtner <<a href="mailto:franco@opnsense.org">franco@opnsense.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><br>
> On 7. Aug 2022, at 9:38 AM, Doug Rabson <<a href="mailto:dfr@rabson.org" target="_blank">dfr@rabson.org</a>> wrote:<br>
> <br>
> 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.<br>
<br>
Good, but keep in mind that your home lab is not millions of downstream users. ;)<br></blockquote><div><br></div><div>Of course but this argument is confusing - we are talking about DHCP client, not server. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">> 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.<br>
<br>
<br>
Dynamic AAAA records for client leases is a problem, but isn't that also a<br>
general issue with isc-dhcpd? What's your main DHCP server for IPv6?<br></blockquote><div><br></div><div>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.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
> Again, not seeing the harm for either OPNsense or pfSense - these distributions are free to choose another client.<br>
<br>
If you want to say "not my work, not my harm" that's possibly fine, but not<br>
well-rounded in a real world setting as indicated by your former status.<br></blockquote><div><br></div><div>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'.</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
It is still a lot of work to get it working mostly like it did before and at<br>
least one FreeBSD major release will suffer from the inferiority of switching<br>
to a new integration. I'm sure disrupting basic IPv4 DHCP capability which was<br>
always working prior will come as a surprise to people involved in green lighting<br>
this, but this is likely an unavoidable consequence of the proposal.<br></blockquote><div><br></div><div>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).</div><div><br></div><div>Doug.</div><div><br></div></div></div>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACA0VUgF8ojK70MKdAjLkabxD-_2iF9A88xYnShL0Znfw12qgg>