Date: Tue, 24 Aug 2021 18:57:56 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 256767] ifconfig(8) NOAUTO and rc.conf(5): untimely configuration (up) of a network interface when it should be down Message-ID: <bug-256767-227-M8Epm0tXKs@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256767-227@https.bugs.freebsd.org/bugzilla/> References: <bug-256767-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256767 Mason Loring Bliss <mason@blisses.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mason@blisses.org --- Comment #4 from Mason Loring Bliss <mason@blisses.org> --- I see a very similar issue. rc.conf: ifconfig_em0=3D"NOAUTO DHCP" wlans_iwn0=3D"wlan0" ifconfig_wlan0=3D"NOAUTO WPA DHCP" When I log into an X session, one of the things that happens is barrierc=20 launches as a user process, and it sits in a window looping over failures=20 because there is (correctly) no network. But then I notice it connecting,=20 with ifconfig showing me a configured em0. Racing the system for a test, I logged in and quickly said 'ifconfig' in a= =20 terminal, and saw no configured interfaces, but I then quickly said 'ps ax= =20 | grep dhc' and saw: 84491 - R 0:00.01 /bin/sh /etc/rc.d/dhclient quietstart em0 (env) ...and shortly thereafter em0 was connected. And then, a bit later: $ ps ax | grep dhc 13818 - ICs 0:00.00 dhclient: em0 (dhclient) 89207 - Is 0:00.00 dhclient: system.syslog (dhclient) 91789 - Is 0:00.00 dhclient: em0 [priv] (dhclient) 58103 11 S+ 0:00.00 grep dhc I have yet to dig into what's launching the dhclient. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256767-227-M8Epm0tXKs>