Date: Wed, 3 Dec 2025 11:34:59 +0100 From: A FreeBSD User <freebsd@walstatt-de.de> To: Ronald Klop <ronald-lists@klop.ws> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, Dag-Erling =?UTF-8?B?U23DuHJncmF2?= <des@FreeBSD.org> Subject: Re: 15-STABLE: dhclient fails on em0 (Lenovo T580) Message-ID: <20251203113526.398dfc6c@thor.sb211.local> In-Reply-To: <1585113262.3581.1764757070010@localhost> 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>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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 --] -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCaTASbgAKCRCxzvs8Oqok rwtwAQDX1vZUGTyiAa+BvT62EydZrRBKvEglfxrsqJljT084hQD/X0+tYeVGdXYj IgcFgFWYUAA7/MuRpDIbqYwtgv/mXgU= =0Cu/ -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20251203113526.398dfc6c>