Date: Thu, 4 Dec 2025 11:51:35 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: A FreeBSD User <freebsd@walstatt-de.de> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> Subject: Re: 15-STABLE: dhclient fails on em0 (Lenovo T580) 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>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Hi, You have dhcp6c configured on a lagg0 interface, and the lagg0 interface is created, but not configured anywhere in your configuration. But your problem 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="SYNCDHCP" instead of "DHCP"? That should start dhclient earlier and wait for the IP and must give output of dhclient. 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 really 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 from 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ørgrav" <des@FreeBSD.org> Onderwerp: Re: 15-STABLE: dhclient fails on em0 (Lenovo T580) > > 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 approach. 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 and 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.conf in /etc/rc.conf. My > > rc.conf is usually just 10 or 20 lines. Some network config and enabling 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ørgrav" <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ørgrav <des@FreeBSD.org> wrote: > > > > > > > A FreeBSD User <freebsd@walstatt-de.de> writes: > > > > > Dag-Erling Smørgrav <des@FreeBSD.org> writes: > > > > > > As a workaround, add this to /boot/loader.conf: > > > > > > > > > > > > net.inet.ip.fw.default_to_accept="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 therefore assumed > > > > that the problem was that dhclient was trying to acquire a lease before > > > > the firewall was configured. Switching default_to_accept 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 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 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. Result 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 maintained boxes. > > > > > > Kind regards, > > > > > > oh > > > > > > > > > > > > > > > > > > > > -- > > A FreeBSD user > > > > [-- Attachment #2 --] <html><head></head><body>Hi,<br> <br> You have dhcp6c configured on a lagg0 interface, and the lagg0 interface is created, but not configured anywhere in your configuration. But your problem is about IPv4 and not IPv6. So it might not be related. But it makes me wonder about your config.<br> <br> I can't find in your log messages that dhclient is ever started.<br> Can you try to configure ifconfig_em0="SYNCDHCP" instead of "DHCP"? That should start dhclient earlier and wait for the IP and must give output of dhclient. Please reply with the console log output of that boot run.<br> <br> To me your configuration looks really messy, so I'm sorry that I can't really 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 from your /etc/rc.conf and only keep lines that actually configure something.<br> <br> I hope you figure out the issue some day.<br> <br> Regards,<br> Ronald.<br> <br> <br> <p><strong>Van:</strong> A FreeBSD User <freebsd@walstatt-de.de><br> <strong>Datum:</strong> woensdag, 3 december 2025 11:34<br> <strong>Aan:</strong> Ronald Klop <ronald-lists@klop.ws><br> <strong>CC:</strong> FreeBSD CURRENT <freebsd-current@freebsd.org>, "Dag-Erling Smørgrav" <des@FreeBSD.org><br> <strong>Onderwerp:</strong> Re: 15-STABLE: dhclient fails on em0 (Lenovo T580)</p> <blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px"> <div class="MessageRFC822Viewer" id="P"> <div class="MultipartMixedViewer"> <div class="TextPlainViewer" id="P.P.P1">Am Tage des Herren Wed, 3 Dec 2025 11:17:50 +0100 (CET)<br> Ronald Klop <ronald-lists@klop.ws> schrieb:<br> <br> > Hi,<br> ><br> > Did you copy /etc/defaults/rc.conf to /etc/rc.conf?<br> <br> Yes, I do, since I change things on an experimental basis quite often.<br> <br> That never induced any issue in the last decades using this kind of approach. Each variable<br> set in defaults/rc.conf should be cleanly overriden via rc.conf and rc.conf.local, shouldn't<br> it? The only possible issue I could imagine is the order variables appear and being processed<br> by rc.subr and siblings ... or am I wrong?<br> <br> Kind regards,<br> oh<br> ><br> > AFAIK, the idea is to only override settings from /etc/defaults/rc.conf in /etc/rc.conf. My<br> > rc.conf is usually just 10 or 20 lines. Some network config and enabling some services. Like<br> > what you have in /etc/rc.conf.local.<br> ><br> > Regards,<br> > Ronald.<br> ><br> > <br> > Van: FreeBSD User <freebsd@walstatt-de.de><br> > Datum: woensdag, 3 december 2025 10:15<br> > Aan: "Dag-Erling Smørgrav" <des@FreeBSD.org><br> > CC: FreeBSD CURRENT <freebsd-current@freebsd.org><br> > Onderwerp: Re: 15-STABLE: dhclient fails on em0 (Lenovo T580)<br> > ><br> > > On Tue, 02 Dec 2025 20:51:33 +0100<br> > > Dag-Erling Smørgrav <des@FreeBSD.org> wrote:<br> > > <br> > > > A FreeBSD User <freebsd@walstatt-de.de> writes: <br> > > > > Dag-Erling Smørgrav <des@FreeBSD.org> writes: <br> > > > > > As a workaround, add this to /boot/loader.conf:<br> > > > > ><br> > > > > > net.inet.ip.fw.default_to_accept="1" <br> > > > > the above "trick" doesn't help. <br> > > ><br> > > > This is concerning.<br> > > ><br> > > > The fact that `dhclient em0` works after the firewall is up proves that<br> > > > the firewall rules themselves are not the issue. I therefore assumed<br> > > > that the problem was that dhclient was trying to acquire a lease before<br> > > > the firewall was configured. Switching default_to_accept on should have<br> > > > made that possible. The fact that it doesn't means the firewall isn't<br> > > > to blame at all. Something else is causing dhclient not to run at boot.<br> > > ><br> > > > Could you please provide the output from the following command:<br> > > ><br> > > > grep -r '^[^#]' /etc/rc.conf*<br> > > ><br> > > > Could you please also provide a log of the boot messages, if possible?<br> > > ><br> > > > DES <br> > ><br> > > Having had a feeling that statically compiling in FIREWALL (ipw) support into<br> > > my kernel, I tested by excluding the appropritae lines and adding the<br> > > /boot/loader.conf.local line again allow packets by default. Result is the very<br> > > same.<br> > ><br> > > Attached you'll find the requested files.<br> > ><br> > > A side note: I do etcupdate on a regular basis on all of the maintained boxes.<br> > ><br> > > Kind regards,<br> > ><br> > > oh<br> > ><br> > ><br> > ><br> > > <br> ><br> > <br> <br> <br> <br> -- <br> <br> A FreeBSD user</div> <hr> <div class="DefaultViewer"> </div> </div> </div> </blockquote> <br> </body></html>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1485528976.4376.1764845495552>