Apologies, I didn't realize you had already tried masking the service. Since Fedora uses systemd in the initramfs, I *think* you could instead try booting with systemd.mask=NetworkManager.service, which will should mask it early boot before your rootfs is even mounted.
On Fri, Nov 8, 2019 at 8:31 PM Anthony Joseph Messina <[email protected]> wrote: > Thank you for responding Ryan. AFAIK, I don't have both systemd-networkd > and > NetworkManager "running" or enabled. In fact, I have had NetworkManager > disabled on these systems for some time (back through F27, I believe). > Post > upgrade (or fresh install) I ensure that NetworkManager is not re-enabled, > and > that systemd-networkd is enabled. Unforuntately, trying to remove > NetworkManager completely seems like a heavy hammer based on the `dnf > remove` > output below. > > Also, these identical systemd-networkd configurations do work on F30, just > not > on systems upgraded to F31. > > The only recent change I notice in F31, is that NetworkManager is > initialized > during early boot even when the service is disabled and masked. > > This is the early boot NetworkManager output: > <info> [1573262139.2398] NetworkManager (version 1.20.4-1.fc31) is > starting... (for the first time) > <info> [1573262139.2399] Read config: > /etc/NetworkManager/NetworkManager.conf > <info> [1573262139.2416] auth[0x55b3f3c8b4a0]: create auth-manager: D-Bus > connection not available. Polkit is disabled and all requests are > authenticated. > <info> [1573262139.2426] manager[0x55b3f3c94060]: monitoring kernel > firmware > directory '/lib/firmware'. > <info> [1573262139.2427] hostname: hostname: hostnamed not used as proxy > creation failed with: Could not connect: No such file or directory > <info> [1573262139.2428] hostname: hostname changed from (none) to "linux- > ws1.messinet.com" > <info> [1573262139.2430] dns-mgr[0x55b3f3c8f210]: init: > dns=default,systemd- > resolved rc-manager=symlink > <info> [1573262139.2447] Loaded device plugin: NMTeamFactory (/usr/lib64/ > NetworkManager/1.20.4-1.fc31/libnm-device-plugin-team.so) > <info> [1573262139.2448] manager: rfkill: Wi-Fi enabled by radio > killswitch; > enabled by state file > <info> [1573262139.2448] manager: rfkill: WWAN enabled by radio > killswitch; > enabled by state file > <info> [1573262139.2448] manager: Networking is enabled by state file > <info> [1573262139.2448] dhcp-init: Using DHCP client 'internal' > <info> [1573262139.2453] settings: Loaded settings plugin: ifcfg-rh > ("/usr/ > lib64/NetworkManager/1.20.4-1.fc31/libnm-settings-plugin-ifcfg-rh.so") > <info> [1573262139.2454] settings: Loaded settings plugin: keyfile > (internal) > <info> [1573262139.2459] device (lo): carrier: link connected > <info> [1573262139.2460] manager: (lo): new Generic device > (/org/freedesktop/ > NetworkManager/Devices/1) > <info> [1573262139.2464] manager: (eno1): new Ethernet device (/org/ > freedesktop/NetworkManager/Devices/2) > <info> [1573262139.2466] device (eno1): state change: unmanaged -> > unavailable (reason 'managed', sys-iface-state: 'external') > <warn> [1573262139.4343] sleep-monitor-sd: failed to acquire D-Bus proxy: > Could not connect: No such file or directory > <warn> [1573262139.4343] firewall: could not connect to system D-Bus > (Could > not connect: No such file or directory) > <warn> [1573262139.4344] ifcfg-rh: dbus: couldn't initialize system bus: > Could not connect: No such file or directory > > ~]# dnf --assumeno remove NetworkManager > Dependencies resolved. > > ========================================================================================================================================================================================================================================================================================== > Package > > Architecture Version > > Repository Size > > ========================================================================================================================================================================================================================================================================================== > Removing: > NetworkManager > > x86_64 1:1.20.4-1.fc31 > > @fedora 9.6 M > Removing dependent packages: > NetworkManager-adsl > > x86_64 1:1.20.4-1.fc31 > > @fedora 52 k > NetworkManager-bluetooth > > x86_64 1:1.20.4-1.fc31 > > @fedora 158 k > NetworkManager-ppp > > x86_64 1:1.20.4-1.fc31 > > @fedora 91 k > initial-setup-gui > > x86_64 0.3.76-1.fc31 > > @fedora 26 k > plasma-nm-l2tp > > x86_64 5.16.5-1.fc31 > > @fedora 378 k > plasma-nm-openconnect > > x86_64 5.16.5-1.fc31 > > @fedora 323 k > plasma-nm-openswan > > x86_64 5.16.5-1.fc31 > > @fedora 162 k > plasma-nm-openvpn > > x86_64 5.16.5-1.fc31 > > @fedora 918 k > plasma-nm-pptp > > x86_64 5.16.5-1.fc31 > > @fedora 301 k > plasma-nm-vpnc > > x86_64 5.16.5-1.fc31 > > @fedora 448 k > Removing unused dependencies: > NetworkManager-l2tp > > x86_64 1.2.14-1.fc31 > > @updates 552 k > NetworkManager-libreswan > > x86_64 1.2.12-1.fc31 > > @fedora 450 k > NetworkManager-openconnect > > x86_64 1.2.6-2.fc31 > > @fedora 2.2 M > NetworkManager-openvpn > > x86_64 > 1:1.8.10-1.fc31.1 > > @fedora 1.1 M > NetworkManager-pptp > > x86_64 1:1.2.8-1.fc31.2 > > @fedora 594 k > NetworkManager-team > > x86_64 1:1.20.4-1.fc31 > > @fedora 61 k > NetworkManager-vpnc > > x86_64 1:1.2.6-3.fc31 > > @fedora 620 k > NetworkManager-wifi > > x86_64 1:1.20.4-1.fc31 > > @fedora 340 k > NetworkManager-wwan > > x86_64 1:1.20.4-1.fc31 > > @fedora 189 k > anaconda-core > > x86_64 31.22.6-2.fc31 > > @fedora 10 M > anaconda-gui > > x86_64 31.22.6-2.fc31 > > @fedora 2.3 M > anaconda-tui > > x86_64 31.22.6-2.fc31 > > @fedora 379 k > anaconda-user-help > > noarch 26.1-10.fc31 > > @fedora 574 k > anaconda-widgets > > x86_64 31.22.6-2.fc31 > > @fedora 101 k > bcache-tools > > x86_64 1.0.8-16.fc31 > > @fedora 106 k > blivet-data > > noarch 1:3.1.5-2.fc31 > > @fedora 369 k > blivet-gui-runtime > > noarch 2.1.11-2.fc31 > > @fedora 1.0 M > bluez-libs > > x86_64 5.51-1.fc31 > > @fedora 171 k > daxctl-libs > > x86_64 67-1.fc31 > > @updates 94 k > device-mapper-multipath > > x86_64 0.8.0-3.fc31 > > @fedora 281 k > device-mapper-multipath-libs > > x86_64 0.8.0-3.fc31 > > @fedora 881 k > dmraid > > x86_64 > 1.0.0.rc16-43.fc31 > > @fedora 359 k > dmraid-events > > x86_64 > 1.0.0.rc16-43.fc31 > > @fedora 17 k > initial-setup > > x86_64 0.3.76-1.fc31 > > @fedora 230 k > keybinder3 > > x86_64 0.3.2-7.fc31 > > @fedora 32 k > kf5-modemmanager-qt > > x86_64 5.61.0-1.fc31 > > @fedora 901 k > ldns > > x86_64 1.7.0-26.fc31 > > @fedora 422 k > libblockdev-btrfs > > x86_64 2.23-1.fc31 > > @fedora 28 k > libblockdev-dm > > x86_64 2.23-1.fc31 > > @fedora 24 k > libblockdev-kbd > > x86_64 2.23-1.fc31 > > @fedora 40 k > libblockdev-lvm > > x86_64 2.23-1.fc31 > > @fedora 52 k > libblockdev-mpath > > x86_64 2.23-1.fc31 > > @fedora 24 k > libblockdev-nvdimm > > x86_64 2.23-1.fc31 > > @fedora 24 k > libgnomekbd > > x86_64 3.26.1-2.fc31 > > @fedora 632 k > libndp > > x86_64 1.7-4.fc31 > > @fedora 107 k > libnl3-cli > > x86_64 3.5.0-1.fc31 > > @fedora 1.0 M > libnma > > x86_64 1.8.22-1.fc31.1 > > @fedora 524 k > libpskc > > x86_64 2.6.2-3.fc31 > > @fedora 92 k > libreport-anaconda > > x86_64 2.10.1-2.fc31 > > @fedora 18 k > libreswan > > x86_64 3.29-1.fc31.1 > > @fedora 4.5 M > libteam > > x86_64 1.29-2.fc31 > > @fedora 160 k > libtimezonemap > > x86_64 0.4.5.1-6.fc31 > > @fedora 6.7 M > libxklavier > > x86_64 5.4-14.fc31 > > @fedora 165 k > mobile-broadband-provider-info > > noarch 20190618-2.fc31 > > @fedora 488 k > ndctl > > x86_64 67-1.fc31 > > @updates 363 k > ndctl-libs > > x86_64 67-1.fc31 > > @updates 350 k > nm-connection-editor > > x86_64 1.8.22-1.fc31.1 > > @fedora 5.6 M > openconnect > > x86_64 8.05-1.fc31 > > @fedora 2.8 M > openvpn > > x86_64 2.4.7-2.fc31 > > @fedora 1.3 M > pkcs11-helper > > x86_64 1.22-8.fc31 > > @fedora 156 k > plasma-nm > > x86_64 5.16.5-1.fc31 > > @fedora 4.9 M > pptp > > x86_64 1.10.0-7.fc31 > > @fedora 161 k > python3-blivet > > noarch 1:3.1.5-2.fc31 > > @fedora 3.2 M > python3-blockdev > > x86_64 2.23-1.fc31 > > @fedora 80 k > python3-bytesize > > x86_64 2.1-2.fc31 > > @fedora 40 k > python3-kickstart > > noarch 3.21-1.fc31 > > @fedora 2.3 M > python3-langtable > > noarch 0.0.47-1.fc31 > > @fedora 1.2 M > python3-meh > > noarch 0.48-1.fc31 > > @fedora 284 k > python3-meh-gui > > noarch 0.48-1.fc31 > > @fedora 24 k > python3-ntplib > > noarch 0.3.3-15.fc31 > > @fedora 28 k > python3-pid > > noarch 2.2.3-3.fc31 > > @fedora 35 k > python3-productmd > > noarch 1.21-2.fc31 > > @fedora 248 k > python3-pwquality > > x86_64 1.4.1-1.fc31 > > @fedora 25 k > python3-pyparted > > x86_64 1:3.11.2-2.fc31 > > @fedora 364 k > python3-pyudev > > noarch 0.21.0-11.fc31 > > @fedora 315 k > python3-requests-file > > noarch 1.4.3-11.fc31 > > @fedora 9.4 k > python3-requests-ftp > > noarch 0.3.1-15.fc31 > > @fedora 37 k > python3-simpleline > > noarch 1.6-1.fc31 > > @fedora 440 k > sgpio > > x86_64 1.2.0.10-24.fc31 > > @fedora 24 k > stoken-libs > > x86_64 0.91-8.fc31 > > @fedora 94 k > teamd > > x86_64 1.29-2.fc31 > > @fedora 282 k > tigervnc-license > > noarch 1.9.0-7.fc31 > > @fedora 18 k > tigervnc-server-minimal > > x86_64 1.9.0-7.fc31 > > @fedora 3.0 M > tpm2-tss > > x86_64 2.3.1-1.fc31 > > @fedora 1.2 M > userspace-rcu > > x86_64 0.11.1-2.fc31 > > @fedora 417 k > vpnc > > x86_64 > 0.5.3-36.svn550.fc31 > > @fedora 212 k > vpnc-script > > noarch > 20171004-6.git6f87b0f.fc31 > > @fedora 26 k > wpa_supplicant > > x86_64 1:2.9-2.fc31 > > @updates 5.2 M > xl2tpd > > x86_64 1.3.14-1.fc31 > > @fedora 211 k > > Transaction Summary > > ========================================================================================================================================================================================================================================================================================== > Remove 90 Packages > > Freed space: 86 M > Operation aborted. > > On Friday, November 8, 2019 8:14:54 PM CST Ryan Gonzalez wrote: > > Having two networking systems running at once can cause all sorts of > > problems, not sure if this is the issue here or why NM is still starting > > but you can try using 'systemctl mask' on it to completely prevent it > from > > running. > > > > On Fri, Nov 8, 2019, 7:37 PM Anthony Joseph Messina < > [email protected]> > > wrote: I apologize if this isn't the right place to post this request for > > assistance. I've attempted the Fedora User's list with no luck and would > > prefer to ask before filing a bug. > > > > After a successful "dnf systemd upgrade" F30->F31, I'm finding that a > few of > > my machines which use systemd-networkd instead of NetworkManager are no > > longer autoconfiguring IPv6 addresses. I also noticed that even though > > NetworkManager is disabled, it is initiated in early boot, which I'm not > > sure is related. > > > > It appears as though the system isn't assigning the link-local address > and > > therefore can't communicate via IPv6. If anyone has any pointers on > where > > to begin, I'd appreciate it. Thanks. -A > > > > Both systems below use the following > > /etc/systemd/network/10-wired-dhcp.network: > > > > [Match] > > Name=en* > > > > [Network] > > DHCP=yes > > IPv6PrivacyExtensions=yes > > > > > > Both systems are running: > > kernel-5.3.8-300.fc31.x86_64 > > systemd-243-4.gitef67743.fc31.x86_64 > > NetworkManager-1.20.4-1.fc31.x86_64 > > > > > > A system that IS working with systemd-networkd displays the following > debug > > output: > > > > eno1: New device has no master, continuing without > > eno1: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST > > eno1: Link 2 added > > eno1: udev initialized link > > eno1: State changed: pending -> initialized > > eno1: Saved original MTU: 1500 > > eno1: Remembering foreign address: fe80::f64d:30ff:fe6e:2cf5/64 (valid > > forever) eno1: Gained IPv6LL > > eno1: Remembering route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a, > > scope: global, table: local, proto: boot, type: unicast eno1: Remembering > > route: dst: fe80::f64d:30ff:fe6e:2cf5/128, src: n/a, gw: n/a, prefsrc: > n/a, > > scope: global, table: local, proto: kernel, type: local eno1: Remembering > > route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a, scope: global, > > table: main, proto: kernel, type: unicast eno1: Remembering updated > > address: fe80::f64d:30ff:fe6e:2cf5/64 (valid forever) eno1: Updating > > remembered route: dst: fe80::f64d:30ff:fe6e:2cf5/128, src: n/a, gw: n/a, > > prefsrc: n/a, scope: global, table: local, proto: kernel, type: local > eno1: > > Link state is up-to-date > > eno1: found matching network '/etc/systemd/network/10-wired-dhcp.network' > > Setting '/proc/sys/net/ipv6/conf/eno1/disable_ipv6' to '0' > > eno1: IPv6 successfully enabled > > Setting '/proc/sys/net/ipv6/conf/eno1/proxy_ndp' to '0' > > Setting '/proc/sys/net/ipv6/conf/eno1/use_tempaddr' to '2' > > Setting '/proc/sys/net/ipv6/conf/eno1/accept_ra' to '0' > > eno1: Started LLDP. > > eno1: Setting address genmode for link > > eno1: Acquiring DHCPv4 lease > > eno1: Discovering IPv6 routers > > eno1: State changed: initialized -> configuring > > eno1: Acquiring DHCPv6 lease on NDisc request > > > > > > Another system that IS NOT working displays the following debug output > (note > > the missing Remembering foreign address and Gained IPv6LL lines): > > > > eno1: New device has no master, continuing without > > eno1: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST > > eno1: Link 2 added > > eno1: udev initialized link > > eno1: State changed: pending -> initialized > > eno1: Saved original MTU: 1500 > > eno1: Remembering route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a, > > scope: global, table: local, proto: boot, type: unicast eno1: Link state > is > > up-to-date > > eno1: found matching network '/etc/systemd/network/10-wired-dhcp.network' > > eno1: IPv6 successfully enabled > > eno1: Started LLDP. > > eno1: Setting address genmode for link > > eno1: Acquiring DHCPv4 lease > > eno1: State changed: initialized -> configuring > > > > -- Ryan (ライアン) Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else https://refi64.com/
_______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
