From nobody Fri Jun 20 13:43:51 2025 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 4bNzGM0sQFz602kr for ; Fri, 20 Jun 2025 13:43:55 +0000 (UTC) (envelope-from SRS0=UZb3=ZD=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int-backup.realworks.nl (smtp-relay-int-backup.realworks.nl [87.255.56.188]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4bNzGL5btbz3V9H for ; Fri, 20 Jun 2025 13:43:54 +0000 (UTC) (envelope-from SRS0=UZb3=ZD=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Received: from smtp-relay-int-backup.realworks.nl (crmpreview2.colo2.realworks.nl [10.2.52.32]) by mailrelayint2.colo2.realworks.nl (Postfix) with ESMTP id 4bNzGH4vjsz6g; Fri, 20 Jun 2025 15:43:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1750427031; 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: in-reply-to:in-reply-to:references:references; bh=sQsUHKcQ+bkbf0q8c0xxKUNjOHpJgi+jelgxf6efnHw=; b=LURlGY8jZZejZsdZMUDqJeGVziNfDfHcHDW3/jttFE6q8JJb8IqqfW85eTTuFQqge5BLrT LuwHugPimj2FDr4s7OCtt6E+g0KsmtTS0oaTMHq1PnYBBmsOKbE8b8j1Iu83ZrQI2JD1se Rrwsk0/r/TVte50jJ8TtRaElAqEbk+wdy5A6pnQmH8qS3zogsF8xACrdsLQad+RBDttcV4 vmDi6ziM4qPE9u98AKCxSvUrIilriR2j3NniRHgHNED93e3SVD8FKHxiFuuraTAoPa1AEg CY7A5Hj3ruUdRAtRXi9QmJ8Vf4jT/Go/oHZlvhViM7gpyukgkJ5KiNJcmYL7xw== Received: from crmpreview2.colo2.realworks.nl (localhost [127.0.0.1]) by crmpreview2.colo2.realworks.nl (Postfix) with ESMTP id 501D22611D0; Fri, 20 Jun 2025 15:43:51 +0200 (CEST) Date: Fri, 20 Jun 2025 15:43:51 +0200 (CEST) From: Ronald Klop To: Karl Denninger Cc: freebsd-net@freebsd.org Message-ID: <549425506.8980.1750427031217@localhost> In-Reply-To: <5f4fe904-dda8-42d8-8325-dd3bb0403df8@denninger.net> References: <18ff2d4772a.129dde187836962.5411001908566459400@marples.name> <1188806329.62817.1750321263908@localhost> <5f4fe904-dda8-42d8-8325-dd3bb0403df8@denninger.net> Subject: Re: dhcpcd(8) into FreeBSD base 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 Content-Type: multipart/alternative; boundary="----=_Part_8979_847187254.1750427031055" X-Mailer: Realworks (753.38) X-Originating-Host: from (83-81-212-149.cable.dynamic.v4.ziggo.nl [83.81.212.149]) by crmpreview2.colo2.realworks.nl [10.2.52.32] with HTTP; Fri, 20 Jun 2025 15:43:51 +0200 Importance: Normal X-Priority: 3 (Normal) X-Originating-User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:139.0) Gecko/20100101 Firefox/139.0 X-Rspamd-Queue-Id: 4bNzGL5btbz3V9H X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:38930, ipnet:87.255.32.0/19, country:NL] ------=_Part_8979_847187254.1750427031055 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I have tried the "noip4ll" and "noarp" option. Didn't change anything. My issue ended up that dhcpcd said in the logs it would sent a dhcp packet (the port 67/68 thing), but nothing appeared on the network. And so the lease timed out after a long time and it removed the IP address from the interface. Ronald. Van: Karl Denninger Datum:vrijdag, 20 juni 2025 15:24 Aan:freebsd-net@freebsd.org Onderwerp:Re: dhcpcd(8) into FreeBSD base > > On 6/19/2025 04:21, Ronald Klop wrote: >> Hi, >> >> I don't know the details about your setup, but I tried dhcpcd in my network last few months and I encountered that it: >> >> - runs fine in a 14.X jail on a 14.X machine (RPI3B) for both IP4 and IP6 >> - it does not work well on a 14.X jail on a 15.x machines. (RPI4) >> >> The symptoms look a lot like what you describe. Sometimes it got an address and a day later it was gone again. Restarting sometimes helped, often didn't change anything. >> Up to the point that I started reading to code of dhcpcd and encountered that it writes a line in the log about getting a lease and the next statement was sending a packet out on the network and I never see that packet in tcpdump. >> >> Anyway on the RPI3 I still use it. On the RPI4 I went back to dhclient + SLAAC after I put a lot of time in tcpdumping and testing. Maybe it is just that 14 userland doesn't match enough with 15 kernel to do BPF/dhcp. But than again.... with dhclient it works fine. >> >> I didn't run dhcpcd yet on the host OS yet as I was first testing it in the VNET jails. >> >> Just my 2 cents. >> >> Regards, >> Ronald. >> > > Now that's very curious. > > Could you (where you can control what's going on with the other end, which I can't) try again with "noip4ll" and "noarp" and see if you still get the oddness? > > I have a suspicion this is the cause (from the docs "noarp" should be enough to disable both, but never hurts to stick 'em both in there) -- and if so then perhaps default behavior should be changed. > > -- > Karl Denninger > karl@denninger.net > The Market Ticker > [S/MIME encrypted email preferred] > ------=_Part_8979_847187254.1750427031055 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit
I have tried the "noip4ll" and "noarp" option. Didn't change anything.

My issue ended up that dhcpcd said in the logs it would sent a dhcp packet (the port 67/68 thing), but nothing appeared on the network. And so the lease timed out after a long time and it removed the IP address from the interface.

Ronald.

 

Van: Karl Denninger <karl@denninger.net>
Datum:vrijdag, 20 juni 2025 15:24
Aan:freebsd-net@freebsd.org
Onderwerp:Re: dhcpcd(8) into FreeBSD base

On 6/19/2025 04:21, Ronald Klop wrote:
Hi,

I don't know the details about your setup, but I tried dhcpcd in my network last few months and I encountered that it:

- runs fine in a 14.X jail on a 14.X machine (RPI3B) for both IP4 and IP6
- it does not work well on a 14.X jail on a 15.x machines. (RPI4)

The symptoms look a lot like what you describe. Sometimes it got an address and a day later it was gone again. Restarting sometimes helped, often didn't change anything.
Up to the point that I started reading to code of dhcpcd and encountered that it writes a line in the log about getting a lease and the next statement was sending a packet out on the network and I never see that packet in tcpdump.

Anyway on the RPI3 I still use it. On the RPI4 I went back to dhclient + SLAAC after I put a lot of time in tcpdumping and testing. Maybe it is just that 14 userland doesn't match enough with 15 kernel to do BPF/dhcp. But than again.... with dhclient it works fine.

I didn't run dhcpcd yet on the host OS yet as I was first testing it in the VNET jails.

Just my 2 cents.

Regards,
Ronald.
 

Now that's very curious.

Could you (where you can control what's going on with the other end, which I can't) try again with "noip4ll" and "noarp" and see if you still get the oddness?

I have a suspicion this is the cause (from the docs "noarp" should be enough to disable both, but never hurts to stick 'em both in there) -- and if so then perhaps default behavior should be changed.

--
Karl Denninger
karl@denninger.net
The Market Ticker
[S/MIME encrypted email preferred]
 

  ------=_Part_8979_847187254.1750427031055--