From nobody Thu Dec 4 10:51:35 2025 X-Original-To: freebsd-current@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 4dMWXc1278z6HnX7 for ; Thu, 04 Dec 2025 10:51:44 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [31.134.205.98]) (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 4dMWXb1VNTz3g1R; Thu, 04 Dec 2025 10:51:43 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b="m4gzH4/K"; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of ronald-lists@klop.ws designates 31.134.205.98 as permitted sender) smtp.mailfrom=ronald-lists@klop.ws Received: from crmpreview5.colo2.realworks.nl (localhost [127.0.0.1]) by crmpreview5.colo2.realworks.nl (Postfix) with ESMTP id 9BFDEC02D5; Thu, 4 Dec 2025 11:51:35 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1764845496; 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=YbWeHsqkefpMCqlEKOuVvn6fdtSVvFD2NVNe7BwojUA=; b=m4gzH4/KlWVOifCof5bvMzLlb/33u5cA3GcA5o0X4Ear8h5q78nVXrE+W1LXoXvENECQmm nmrM1XKemPhW0RTrzwoH4OtI8I6CqjJByFKRQf/qC4JZ3FGNVZSYOx2yK+kWYeNaqpgj+x k/K84iDQIW+71IEj9mr+eUjdOzw1JP3COS6ob8Z9NvaI5QQyGTK9XkJTnltFRdI3BaE1EO ybkO5LdKncr4nmm2O8aG5C+DCl8QtNTH/5nopwJfrDc4C3MImpSPicoY1vti0OzEvRdbMu jRCbWmTlkfvrwi2zISCWcGoWrO15CfUkLiLryO4bYCtGkrExtZDrgJR1NkFmkw== Date: Thu, 4 Dec 2025 11:51:35 +0100 (CET) From: Ronald Klop To: A FreeBSD User Cc: FreeBSD CURRENT , =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= Message-ID: <1485528976.4376.1764845495552@localhost> In-Reply-To: <20251203113526.398dfc6c@thor.sb211.local> References: <20251128082630.3dbea678@hermann> <20251128110534.3987f908@hermann> <86fr9yie5u.fsf@ltc.des.dev> <20251201132649.5aef71e8@thor.sb211.local> <86a500hdbu.fsf@ltc.des.dev> <20251203101500.36545493@hermann> <1585113262.3581.1764757070010@localhost> <20251203113526.398dfc6c@thor.sb211.local> Subject: Re: 15-STABLE: dhclient fails on em0 (Lenovo T580) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4375_270468950.1764845495524" X-Mailer: Realworks (776.26) Importance: Normal X-Priority: 3 (Normal) X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; R_SPF_ALLOW(-0.20)[+ip4:31.134.205.64/26]; ONCE_RECEIVED(0.20)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ASN(0.00)[asn:51088, ipnet:31.134.200.0/21, country:NL]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; HAS_X_PRIO_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+] X-Rspamd-Queue-Id: 4dMWXb1VNTz3g1R ------=_Part_4375_270468950.1764845495524 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Hi, You have dhcp6c configured on a lagg0 interface, and the lagg0 interface is= created, but not configured anywhere in your configuration. But your probl= em is about IPv4 and not IPv6. So it might not be related. But it makes me = wonder about your config. I can't find in your log messages that dhclient is ever started. Can you try to configure ifconfig_em0=3D"SYNCDHCP" instead of "DHCP"? That = should start dhclient earlier and wait for the IP and must give output of d= hclient. Please reply with the console log output of that boot run. To me your configuration looks really messy, so I'm sorry that I can't real= ly help you any further. I can't easily figure out what you configured and = what is still the default. My advice would be to remove all the defaults fr= om your /etc/rc.conf and only keep lines that actually configure something. I hope you figure out the issue some day. Regards, Ronald. =20 Van: A FreeBSD User Datum: woensdag, 3 december 2025 11:34 Aan: Ronald Klop CC: FreeBSD CURRENT , "Dag-Erling Sm=C3=B8rgra= v" Onderwerp: Re: 15-STABLE: dhclient fails on em0 (Lenovo T580) >=20 > Am Tage des Herren Wed, 3 Dec 2025 11:17:50 +0100 (CET) > Ronald Klop schrieb: >=20 > > Hi, > > > > Did you copy /etc/defaults/rc.conf to /etc/rc.conf? >=20 > Yes, I do, since I change things on an experimental basis quite often. >=20 > That never induced any issue in the last decades using this kind of appro= ach. Each variable > set in defaults/rc.conf should be cleanly overriden via rc.conf and rc.co= nf.local, shouldn't > it? The only possible issue I could imagine is the order variables appear= and being processed > by rc.subr and siblings ... or am I wrong? >=20 > Kind regards, > oh > > > > AFAIK, the idea is to only override settings from /etc/defaults/rc.conf= in /etc/rc.conf. My > > rc.conf is usually just 10 or 20 lines. Some network config and enablin= g some services. Like > > what you have in /etc/rc.conf.local. > > > > Regards, > > Ronald. > > > > =20 > > Van: FreeBSD User > > Datum: woensdag, 3 december 2025 10:15 > > Aan: "Dag-Erling Sm=C3=B8rgrav" > > CC: FreeBSD CURRENT > > Onderwerp: Re: 15-STABLE: dhclient fails on em0 (Lenovo T580) > > > > > > On Tue, 02 Dec 2025 20:51:33 +0100 > > > Dag-Erling Sm=C3=B8rgrav wrote: > > > =20 > > > > A FreeBSD User writes: =20 > > > > > Dag-Erling Sm=C3=B8rgrav writes: =20 > > > > > > As a workaround, add this to /boot/loader.conf: > > > > > > > > > > > > net.inet.ip.fw.default_to_accept=3D"1" =20 > > > > > the above "trick" doesn't help. =20 > > > > > > > > This is concerning. > > > > > > > > The fact that `dhclient em0` works after the firewall is up proves = that > > > > the firewall rules themselves are not the issue. I therefore assum= ed > > > > that the problem was that dhclient was trying to acquire a lease be= fore > > > > the firewall was configured. Switching default_to_accept on should= have > > > > made that possible. The fact that it doesn't means the firewall is= n't > > > > to blame at all. Something else is causing dhclient not to run at = boot. > > > > > > > > Could you please provide the output from the following command: > > > > > > > > grep -r '^[^#]' /etc/rc.conf* > > > > > > > > Could you please also provide a log of the boot messages, if possib= le? > > > > > > > > DES =20 > > > > > > Having had a feeling that statically compiling in FIREWALL (ipw) supp= ort into > > > my kernel, I tested by excluding the appropritae lines and adding the > > > /boot/loader.conf.local line again allow packets by default. Result i= s the very > > > same. > > > > > > Attached you'll find the requested files. > > > > > > A side note: I do etcupdate on a regular basis on all of the maintain= ed boxes. > > > > > > Kind regards, > > > > > > oh > > > > > > > > > > > > =20 > > > > =20 >=20 >=20 >=20 > --=20 >=20 > A FreeBSD user >=20 >=20 >=20 > =20 =20 ------=_Part_4375_270468950.1764845495524 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi,

You have dhcp6c configured on a lagg0 interface, and the lagg0 interface is= created, but not configured anywhere in your configuration. But your probl= em is about IPv4 and not IPv6. So it might not be related. But it makes me = wonder about your config.

I can't find in your log messages that dhclient is ever started.
Can you try to configure ifconfig_em0=3D"SYNCDHCP" instead of "DHCP"? That = should start dhclient earlier and wait for the IP and must give output of d= hclient. Please reply with the console log output of that boot run.

To me your configuration looks really messy, so I'm sorry that I can't real= ly help you any further. I can't easily figure out what you configured and = what is still the default. My advice would be to remove all the defaults fr= om your /etc/rc.conf and only keep lines that actually configure something.=

I hope you figure out the issue some day.

Regards,
Ronald.


 

Van: A FreeBSD User <freebsd@walstatt-de.de>
Datum: woensdag, 3 december 2025 11:34
Aan: Ronald Klop <ronald-lists@klop.ws>
CC: FreeBSD CURRENT <freebsd-current@freebsd.org>, "= Dag-Erling Sm=C3=B8rgrav" <des@FreeBSD.org>
Onderwerp: Re: 15-STABLE: dhclient fails on em0 (Lenovo T5= 80)

Am Tage des Herren Wed, 3 Dec = 2025 11:17:50 +0100 (CET)
Ronald Klop <ronald-lists@klop.ws> schrieb:

> Hi,
>
> Did you copy /etc/defaults/rc.conf to /etc/rc.conf?

Yes, I do, since I change things on an experimental basis quite often.

That never induced any issue in the last decades using this kind of approac= h. Each variable
set in defaults/rc.conf should be cleanly overriden via rc.conf and rc.conf= .local, shouldn't
it? The only possible issue I could imagine is the order variables appear a= nd being processed
by rc.subr and siblings ... or am I wrong?

Kind regards,
oh
>
> AFAIK, the idea is to only override settings from /etc/defaults/rc.con= f in /etc/rc.conf. My
> rc.conf is usually just 10 or 20 lines. Some network config and enabli= ng some services. Like
> what you have in /etc/rc.conf.local.
>
> Regards,
> Ronald.
>
>  
> Van: FreeBSD User <freebsd@walstatt-de.de>
> Datum: woensdag, 3 december 2025 10:15
> Aan: "Dag-Erling Sm=C3=B8rgrav" <des@FreeBSD.org>
> CC: FreeBSD CURRENT <freebsd-current@freebsd.org>
> Onderwerp: Re: 15-STABLE: dhclient fails on em0 (Lenovo T580)
> >
> > On Tue, 02 Dec 2025 20:51:33 +0100
> > Dag-Erling Sm=C3=B8rgrav <des@FreeBSD.org> wrote:
> >   
> > > A FreeBSD User <freebsd@walstatt-de.de> writes:  =
> > > > Dag-Erling Sm=C3=B8rgrav <des@FreeBSD.org> writes= :    
> > > > > As a workaround, add this to /boot/loader.conf: > > > > >
> > > > >     net.inet.ip.fw.default_to_= accept=3D"1"    
> > > > the above "trick" doesn't help.    
> > >
> > > This is concerning.
> > >
> > > The fact that `dhclient em0` works after the firewall is up = proves that
> > > the firewall rules themselves are not the issue.  I the= refore assumed
> > > that the problem was that dhclient was trying to acquire a l= ease before
> > > the firewall was configured.  Switching default_to_acce= pt on should have
> > > made that possible.  The fact that it doesn't means the= firewall isn't
> > > to blame at all.  Something else is causing dhclient no= t to run at boot.
> > >
> > > Could you please provide the output from the following comma= nd:
> > >
> > >     grep -r '^[^#]' /etc/rc.conf*
> > >
> > > Could you please also provide a log of the boot messages, if= possible?
> > >
> > > DES  
> >
> > Having had a feeling that statically compiling in FIREWALL (ipw) = support into
> > my kernel, I tested by excluding the appropritae lines and adding= the
> > /boot/loader.conf.local line again allow packets by default. Resu= lt is the very
> > same.
> >
> > Attached you'll find the requested files.
> >
> > A side note: I do etcupdate on a regular basis on all of the main= tained boxes.
> >
> > Kind regards,
> >
> > oh
> >
> >
> >
> >    
>
>  



-- 

A FreeBSD user
 

  ------=_Part_4375_270468950.1764845495524--