Re: FC31 : won't activate interfaces - "strictly unmanaged"
On 1/26/20 3:16 AM, Thomas Haller via networkmanager-list wrote: On Sat, 2020-01-25 at 14:34 -0500, sean darcy via networkmanager-list wrote: Fedora FC31. NetworkManager-1.20.10-1.fc31.x86_64 This a cross post with Fedora user. On FC31 I can't persistently rename the interfaces, see: https://bugzilla.redhat.com/show_bug.cgi?id=1777893 I'll give up and use FC31 interface names : enp1s0 and enp0s20u3. I've used nmtui to set up the interfaces. But NM won't activate them because they are "strictly unmanaged" !! Hi, I think this is a bug. NetworkManager is running in initrd. Thereby it already activates the interface. Later, udev wants to rename the interface, but since it's already up, it fails to do so. The result is that udev doesn't indicate that the device is initialized, which causes NM to wait for it (and thus it's unmanaged). It seems there are several potential issues: - why does NetworkManager even run in initrd, if you didn't configure it to do so? - if NM is running in initrd, should it wait for udev to rename the device? - why does udev completely fail in this case? - maybe NM should after a timeout stop waiting for udev, to mitigate this issue. You could look at the logfile to verify that. Enable level=TRACE logging, but most interesting are also the messages from initrd and udev. best, Thomas What does that mean and how do I fix it ? Is there some other way to persistently activate the interface ? /etc/network/interfaces does not exist. sean cat /etc/sysconfig/network-scripts/ifcfg-enp* TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none IPADDR=10.10.11.251 PREFIX=24 DNS1=10.10.11.251 DEFROUTE=no IPV4_FAILURE_FATAL=no IPV6INIT=no IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=enp0s20u3 UUID=bf8aa45c-31e4-403a-9c14-c1a59bf0f2b2 ONBOOT=yes DEVICE=enp0s20u3 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=dhcp DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=enp1s0 UUID=a1b089e9-5a13-4df7-8f09-9f54ebc56cea DEVICE=enp1s0 ONBOOT=yes Thanks for the quick response. I hope it's not a bug, since I'd like to get this machine up and running. "Enable level=TRACE" where ? rsyslogd.conf ? For kernel ? udevd? everything ? sean ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to Build Network Manager ?
Hi, I can also provide some assistance regarding meson if necessary. The first step would be to execute meson in the cloned NM repository providing a build directory. Something like `meson _build`. If this step is successful, you would then execute ninja to build it providing the previously used build directory, `ninja -C _build`. Hope this is useful as a starting step. BR, El dom., 26 ene. 2020 a las 9:11, Thomas Haller via networkmanager-list (< networkmanager-list@gnome.org>) escribió: > On Sun, 2020-01-26 at 04:18 +, Ammar Sheikh wrote: > > Hello. > > I am not familiar with the Meson Build System. How do i build > > NetworkManager ? > > Hi, > > > See https://wiki.gnome.org/Projects/NetworkManager/Hacking > > Is something still unclear? > > You can also use autotools. > > > best, > Thomas > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: FC31 : won't activate interfaces - "strictly unmanaged"
On Sat, 2020-01-25 at 14:34 -0500, sean darcy via networkmanager-list wrote: > Fedora FC31. NetworkManager-1.20.10-1.fc31.x86_64 > This a cross post with Fedora user. > > On FC31 I can't persistently rename the interfaces, see: > https://bugzilla.redhat.com/show_bug.cgi?id=1777893 > > I'll give up and use FC31 interface names : enp1s0 and enp0s20u3. > > I've used nmtui to set up the interfaces. But NM won't activate them > because they are "strictly unmanaged" !! Hi, I think this is a bug. NetworkManager is running in initrd. Thereby it already activates the interface. Later, udev wants to rename the interface, but since it's already up, it fails to do so. The result is that udev doesn't indicate that the device is initialized, which causes NM to wait for it (and thus it's unmanaged). It seems there are several potential issues: - why does NetworkManager even run in initrd, if you didn't configure it to do so? - if NM is running in initrd, should it wait for udev to rename the device? - why does udev completely fail in this case? - maybe NM should after a timeout stop waiting for udev, to mitigate this issue. You could look at the logfile to verify that. Enable level=TRACE logging, but most interesting are also the messages from initrd and udev. best, Thomas > > What does that mean and how do I fix it ? > > Is there some other way to persistently activate the interface ? > > /etc/network/interfaces does not exist. > > sean > > cat /etc/sysconfig/network-scripts/ifcfg-enp* > TYPE=Ethernet > PROXY_METHOD=none > BROWSER_ONLY=no > BOOTPROTO=none > IPADDR=10.10.11.251 > PREFIX=24 > DNS1=10.10.11.251 > DEFROUTE=no > IPV4_FAILURE_FATAL=no > IPV6INIT=no > IPV6_AUTOCONF=yes > IPV6_DEFROUTE=yes > IPV6_FAILURE_FATAL=no > IPV6_ADDR_GEN_MODE=stable-privacy > NAME=enp0s20u3 > UUID=bf8aa45c-31e4-403a-9c14-c1a59bf0f2b2 > ONBOOT=yes > DEVICE=enp0s20u3 > > TYPE=Ethernet > PROXY_METHOD=none > BROWSER_ONLY=no > BOOTPROTO=dhcp > DEFROUTE=yes > IPV4_FAILURE_FATAL=no > IPV6INIT=yes > IPV6_AUTOCONF=yes > IPV6_DEFROUTE=yes > IPV6_FAILURE_FATAL=no > IPV6_ADDR_GEN_MODE=stable-privacy > NAME=enp1s0 > UUID=a1b089e9-5a13-4df7-8f09-9f54ebc56cea > DEVICE=enp1s0 > ONBOOT=yes > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list > signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: How to Build Network Manager ?
On Sun, 2020-01-26 at 04:18 +, Ammar Sheikh wrote: > Hello. > I am not familiar with the Meson Build System. How do i build > NetworkManager ? Hi, See https://wiki.gnome.org/Projects/NetworkManager/Hacking Is something still unclear? You can also use autotools. best, Thomas signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
How to Build Network Manager ?
Hello.I am not familiar with the Meson Build System. How do i build NetworkManager ? Thanks ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
