From nobody Sun Aug 07 09:27:34 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 4M0vBj06wpz4YKYc for ; Sun, 7 Aug 2022 09:27:57 +0000 (UTC) (envelope-from woodsb02@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4M0vBh6hwtz46WM; Sun, 7 Aug 2022 09:27:56 +0000 (UTC) (envelope-from woodsb02@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1659864476; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=KiKeHlq7pgEe6nDyFmiHWb0tLxwgJo4xOL7niotLXWg=; b=xUEuz+C+acX4jKfbx81bOioa8PwsTMHReZYoCMcRxtkGK885r3/iaQBBbJcSKREf8iyV+O tdUskHRxKYOiE80GQR3gCfoIxcgQx3HsY2uQartb8BSSfmUDf66I6SQW8i/jvrdKrZhDbK A3fSiwjN24PWIi4WzUzf2n04OvNak+cQvmhi4gF368hV98MOYTY8Sfrvx7ylGjCKZAEUCg 74pcPutlWu2FnEsR+Dap6JYKJ1pJupwdh2eVD8zpv1xlpEzNb2NDRasp636xB5B/u4iG/h pIkz4GOzDO93tFBJR45i76/bVbzvm4remafnDtu46k0VYEwv0GG1SwYJMb85Tg== Received: from auth1-smtp.messagingengine.com (auth1-smtp.messagingengine.com [66.111.4.227]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: woodsb02) by smtp.freebsd.org (Postfix) with ESMTPSA id 4M0vBh5Frsz1QfB; Sun, 7 Aug 2022 09:27:56 +0000 (UTC) (envelope-from woodsb02@freebsd.org) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailauth.nyi.internal (Postfix) with ESMTP id F2D1127C005A; Sun, 7 Aug 2022 05:27:55 -0400 (EDT) Received: from imap46 ([10.202.2.96]) by compute2.internal (MEProxy); Sun, 07 Aug 2022 05:27:56 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdefiedgudejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvfevufgtgfesthhqredtreerjeenucfhrhhomhepfdeu vghnucghohhoughsfdcuoeifohhoughssgdtvdesfhhrvggvsghsugdrohhrgheqnecugg ftrfgrthhtvghrnhepkedvfeeuhefftdefvdfhheehkeevhedtveettdekkeetueetveeu ueefteetgfffnecuffhomhgrihhnpehgihhthhhusgdrtghomhenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsvghnodhmvghsmhhtphgruhht hhhpvghrshhonhgrlhhithihqddutdelfeeiiedvkeekqddvgeejkedvvdektddqfihooh gushgstddvpeepfhhrvggvsghsugdrohhrghesfihoohgushdrrghm X-ME-Proxy: Feedback-ID: if9c9472a:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id B05C12A20075; Sun, 7 Aug 2022 05:27:55 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-758-ge0d20a54e1-fm-20220729.001-ge0d20a54 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 Message-Id: <91d7cdca-977c-4a18-b6a7-5092acae3b06@www.fastmail.com> In-Reply-To: <9831CA1D-1AE2-4B46-A781-D6B98BECDFBA@opnsense.org> References: <9831CA1D-1AE2-4B46-A781-D6B98BECDFBA@opnsense.org> Date: Sun, 07 Aug 2022 17:27:34 +0800 From: "Ben Woods" To: "Franco Fichtner" Cc: "FreeBSD Net" , emaste@freebsd.org, roy@marples.name, "Hiroki Sato" , brooks@freebsd.org, cy@freebsd.org, "Philip Paeps" Subject: Re: Import dhcpcd(8) into FreeBSD base Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1659864476; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=KiKeHlq7pgEe6nDyFmiHWb0tLxwgJo4xOL7niotLXWg=; b=hEzKSFuxxyFTXRsBFH+E4Oh9kVTJyOeDyuWinuuZtEg+KXUi5oH2K/MvNiaOSuvQ1R49o1 DfeGbz+C5wT3hJpBasfk2cbaIXXuRzSyBvw61nBV9j23NO/E92eS5uHZJY/fk6k9Qi7fYI gMABG02X4kgL3gPSl84IrMi3syPpyjcIcyTtuvKv0pIiOb4ys9geSaZW5i+6X62qxeiX5o 50AgdLd1QdVSdZRvVwv66mN0HW+4MlzxXAuhjps7Azu3SsMSjUmE+qn3KVB4g5s+Dmf6kh ZeMFq/0Onf1gX3Q6tSVKQW++NGd+V5hlUtspn+P1i6xhJTkZDIK8kXrZuDuerg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1659864476; a=rsa-sha256; cv=none; b=GPH5iDORzyP+R0ck8OutV+v2KxDicV6LVSO8FohEiv75fq2zpJp1XEQ1dtniGeugdKgUvW gIH4foMDuSXixmSm7y7j0bzYkFlaKupr9KRx0xmEfXEX/BcbaLblzaWbeoPjAEnBCYZldI P0qBwx+w9l6K5u3x/M3WurRyT83psazKeBNnfnM2EKzdvxd7rOwi8EfehzccDAo1QV2V3m r0gqU5dVYQjt6e9Fhh36GgxlVPOhg02t2clK4nw4zvCmdb7X4OkM4B6w9H1iqh9mpaE49q JGsvn8BsAwqs1yQcSsJDdJTeQl0biR+M4ddzuftWbbPk347Wt3obsaxRx0XggA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On Sun, 7 Aug 2022, at 3:08 PM, Franco Fichtner wrote: > Hi Ben, > > 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 progres= s away > that would definitely have to be rebuilt in the years to follow for th= e all- > in-one (?) replacement. > > For OPNsense we did fork strip down and improve wide-dhcpv6 over the y= ears: > > https://github.com/opnsense/dhcp6c > > It could use more work and cleanups, but basically all that is require= d is to > bring it into FreeBSD and use it to skip a long trail of said future w= ork 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? Hi Franco, The thing that=E2=80=99s missing in rtsold is the same reason why opnsen= se has needed to add dhcp6c: DHCPv6. FreeBSD doesn=E2=80=99t have DHCPv6 support in base today, and therefore= should decide the best way to add it. I appreciate you=E2=80=99ve spent= years supporting dhcp6c and the existing tools, and we are therefore lo= oking at this problem space differently. For me, dhcpcd has been reliably working for a decade, with the remainin= g sandboxing security added years ago. It=E2=80=99s not a new implementa= tion that is yet to go through teething issues. From my point of view, a= single daemon that manages dynamic ip addressing makes sense, rather th= an 3 that have to combine to manage this separately. I appreciate that t= his would require re-work to integrate into the management layer of down= stream products that have found alternative solutions in the mean time. What I would ask is that you try dhcpcd for yourself (if you haven=E2=80= =99t already), and provide feedback on your experience. Also, would be keen to hear some of the perks of dhclient and rtsold - i= s it existing integration into your downstream management layer? (Not me= ant sarcastically). Cheers, Ben --=20 From: Ben Woods woodsb02@freebsd.org