Date: Mon, 7 Oct 2019 12:20:50 -0700 From: Julian Elischer <julian@freebsd.org> To: Roy Marples <roy@marples.name>, 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: <02104834-6ceb-e808-68a6-74ddd29f6075@freebsd.org> In-Reply-To: <8f869d59-ecf8-8e9f-ad64-74a64f744dfa@marples.name> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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? > Linux == netlink(3) > Solaris == route(4) along with an unholy mashup of streamio(7) > > I try and keep OS specific defines out of the main code. > > dhcpcd is also in the FreeBSD ports tree and is currently up to date. Nice to know. 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? Every tool set comes with advocates and someone is sure to be upset if we choose one. :-) 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). > Roy >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?02104834-6ceb-e808-68a6-74ddd29f6075>