Date: Mon, 7 Oct 2019 21:31:10 +0100 From: Roy Marples <roy@marples.name> To: Julian Elischer <julian@freebsd.org>, Ben Woods <woodsb02@gmail.com>, Hiroki Sato <hrs@freebsd.org> Cc: freebsd-net@freebsd.org, driesm.michiels@gmail.com Subject: Re: DHCPv6 client in base Message-ID: <cd99088d-96c4-81a8-bac9-3f6fff5263f9@marples.name> In-Reply-To: <02104834-6ceb-e808-68a6-74ddd29f6075@freebsd.org> References: <001e01d50b49$176104d0$46230e70$@gmail.com> <20190516.032012.517661495892269813.hrs@allbsd.org> <CAOc73CCLPmB7m3yaDE7p4izJ8apaO5jcyRPyLkSJtopqsHxtSQ@mail.gmail.com> <f2ffbe69-31e9-b5ab-2a1d-209fc8261288@freebsd.org> <8f869d59-ecf8-8e9f-ad64-74a64f744dfa@marples.name> <02104834-6ceb-e808-68a6-74ddd29f6075@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/10/2019 20:20, Julian Elischer wrote:
> On 10/7/19 12:05 PM, Roy Marples wrote:
>> On 07/10/2019 19:45, Julian Elischer wrote:
>>> I'm not HRS, but as it uses netlink, how does NetBSD use it? (i.e.
>>> how do we simulate that?)
>>
>> dhcpcd has a driver per OS:
>> BSD == route(4)
>
> though sometimes I wonder if that could not be improved.. it's now what?
> 35 years old?
OpenBSD added:
route overflow detection
route message filtering which I ported to NetBSD and DragonFlyBSD
I added in NetBSD and DragonFlyBSD:
addition of address flags and process id to ifa_msghdr
ported route message filtering
For overflow detection I took a different path from OpenBSD and added it
per socket via an ioctl which cleared up some FIXME comments that have
existed since the code was in the repository.
Just because something is old does not mean it won't improve or get
maintained.
> I guess the question is really "How compatible with ISC/dhclient is it
> (seems somewhat so), does it give us advantages over staying with the
> current tools, and how supported are the other tools, vs these?
As far as dhclient calling a script is concerned. It's a near 100%
compatibility for DHCP4.
For all other protocols or options after I released dhcpcd-4, there is
none because dhcpcd got there first in all cases.
But the real question is how is compatible with the OpenBSD port of
dhclient? From a command line perspective, it's not.
There is no capsicum(4), chroot(4) or process seperation support either.
I don't know how much of a show stopper that is.
> Every tool set comes with advocates and someone is sure to be upset if
> we choose one. :-)
I won't be upset if you do choose dhcpcd.
I also won't advocate for it, this is entirely something for FreeBSD
folk to decide.
I am happy to answer any questions though and if you peruse dhcpcd or
netbsd mailing lists you'll find I solve issues fairly promptly.
> A dhcp Client is a necessary part of the OS (though a bit less so with
> IPV6) but the serer side can be a port. (as it is).
How is FreeBSD handling DNSSL + RDNSS over IPv6RA? That's pretty
standard now and I don't see a userland compoenent for it.
Client side DHCPv6 is disabled by default unless an IPv6RA is received
with either the Managed or Other flag set which then starts DHCPv6.
Enterprise setups like IPv6RA to handle the default router but the
address used by DHCPv6 which they can provision.
Of course, that's my view, yours may differ.
Roy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cd99088d-96c4-81a8-bac9-3f6fff5263f9>