Trouble connecting with NetworkManager
Hi, Since yesterday's upgrade, it's not possible to establish IPV4 networking with networkmanager 1.46.0-1 and networkmanager-qt5 5.115.0-1 on ethernet and Wi- Fi. It happens with both static and dynamic address assignment. A usable IPV6 address is obtained with DHCP on Wi-Fi. An IPV6 address is assigned on ethernet, but it is not usable to be online. # LC_ALL=C LANG=C journalctl -u NetworkManager -r |less Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6577] policy: set 'ETH0' (eth0) as default for IPv4 routing and DNS Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6566] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6556] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6551] manager: NetworkManager state is now CONNECTING Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6546] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6531] device (eth0): Activation: starting connection 'ETH0' (ea1d83f9-2dd7-4769-bbe9-ecd6aa48ff3b) Activating and deactivating NetworkManager-wait-online and NetworkManager- dispatcher do not help. Reverting to networkmanager-1.44.2-3 and networkmanager-qt5-5.112.0-1 is a working temporary solution. Devices: - Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15); Kernel driver in use: r8169 - Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78); Kernel driver in use: iwlwifi I'm reporting in the hope of a fix on the next upgrade. Regards.
Hi there, Try Connman as a network manager. It just works. Daniel On 25/02/2024 08:38, SET wrote:
Hi,
Since yesterday's upgrade, it's not possible to establish IPV4 networking with networkmanager 1.46.0-1 and networkmanager-qt5 5.115.0-1 on ethernet and Wi- Fi. It happens with both static and dynamic address assignment. A usable IPV6 address is obtained with DHCP on Wi-Fi. An IPV6 address is assigned on ethernet, but it is not usable to be online.
# LC_ALL=C LANG=C journalctl -u NetworkManager -r |less
Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6577] policy: set 'ETH0' (eth0) as default for IPv4 routing and DNS Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6566] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6556] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6551] manager: NetworkManager state is now CONNECTING Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6546] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6531] device (eth0): Activation: starting connection 'ETH0' (ea1d83f9-2dd7-4769-bbe9-ecd6aa48ff3b)
Activating and deactivating NetworkManager-wait-online and NetworkManager- dispatcher do not help.
Reverting to networkmanager-1.44.2-3 and networkmanager-qt5-5.112.0-1 is a working temporary solution.
Devices:
- Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15); Kernel driver in use: r8169 - Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78); Kernel driver in use: iwlwifi
I'm reporting in the hope of a fix on the next upgrade.
Regards.
On Sun, 2024-02-25 at 08:38 +0100, SET wrote:
Hi,
Since yesterday's upgrade, it's not possible to establish IPV4 networking with
If your network manager backend is still wpa-supplicant it may be worth trying iwd. i.e. Edit /etc/NetworkManager/conf.d/wifi_backend.conf : [device] wifi.backend=iwd -- Gene
Le dimanche 25 février 2024 11:33:04 CET Genes Lists a écrit :
If your network manager backend is still wpa-supplicant it may be worth trying iwd.
I'm using wpa-supplicant indeed. With 'wifi.backend=iwd', things got worse: no Wi-Fi network is seen in the NetworkManager's systray widget. @DanielRanc
Try Connman as a network manager. It just works.
Connman does not *seem* to have GUI widgets or any UI, I had a quick look. I am already a little familiar with netctl as UI-less app. I need a UI to manage things on my laptop. There have been fundamental changes to NetworkManager according to https://9to5linux.com/networkmanager-1-46-adds-support-for-6ghz-wi-fi-and-en... It's either a problem with NetworkManager itself, or it's up to KDE to catch up. I'll use networkmanager-1.44.2-3 for the while and hope for a transparent fix on next upgrades. Thank you all.
On Sun, 2024-02-25 at 12:07 +0100, SET wrote:
This looks like the same bug and should be fixed with 1.46.0-2 now in testing [1] [1] https://gitlab.archlinux.org/archlinux/packaging/packages/networkmanager/-/i... -- Gene
On 25/02/2024 12:07, SET wrote:
Le dimanche 25 février 2024 11:33:04 CET Genes Lists a écrit :
If your network manager backend is still wpa-supplicant it may be worth
trying iwd.
I'm using wpa-supplicant indeed.
With 'wifi.backend=iwd', things got worse: no Wi-Fi network is seen in the NetworkManager's systray widget.
@DanielRanc
Try Connman as a network manager. It just works.
Connman does not *seem* to have GUI widgets or any UI, I had a quick look. I am already a little familiar with netctl as UI-less app. I need a UI to manage things on my laptop.
I use CMST (Connman System Tray) from AUR, perfect for my use case.
There have been fundamental changes to NetworkManager according to
https://9to5linux.com/networkmanager-1-46-adds-support-for-6ghz-wi-fi-and-en...
It's either a problem with NetworkManager itself, or it's up to KDE to catch up.
I'll use networkmanager-1.44.2-3 for the while and hope for a transparent fix on next upgrades.
Thank you all.
On Sun, Feb 25, 2024 at 08:38:52AM +0100, SET wrote:
Hi,
Since yesterday's upgrade, it's not possible to establish IPV4 networking with networkmanager 1.46.0-1 and networkmanager-qt5 5.115.0-1 on ethernet and Wi- Fi. It happens with both static and dynamic address assignment. A usable IPV6 address is obtained with DHCP on Wi-Fi. An IPV6 address is assigned on ethernet, but it is not usable to be online.
# LC_ALL=C LANG=C journalctl -u NetworkManager -r |less
Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6577] policy: set 'ETH0' (eth0) as default for IPv4 routing and DNS Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6566] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6556] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6551] manager: NetworkManager state is now CONNECTING Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6546] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6531] device (eth0): Activation: starting connection 'ETH0' (ea1d83f9-2dd7-4769-bbe9-ecd6aa48ff3b)
Activating and deactivating NetworkManager-wait-online and NetworkManager- dispatcher do not help.
Reverting to networkmanager-1.44.2-3 and networkmanager-qt5-5.112.0-1 is a working temporary solution.
Any help from https://bbs.archlinux.org/viewtopic.php?id=293132? Merell -- The only difference in the game of love over the last few thousand years is that they've changed trumps from clubs to diamonds. -- The Indianapolis Star
On 2/25/24 08:38, SET wrote:
Hi,
Since yesterday's upgrade, it's not possible to establish IPV4 networking with networkmanager 1.46.0-1 and networkmanager-qt5 5.115.0-1 on ethernet and Wi- Fi. It happens with both static and dynamic address assignment. A usable IPV6 address is obtained with DHCP on Wi-Fi. An IPV6 address is assigned on ethernet, but it is not usable to be online.
# LC_ALL=C LANG=C journalctl -u NetworkManager -r |less
Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6577] policy: set 'ETH0' (eth0) as default for IPv4 routing and DNS Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6566] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6556] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6551] manager: NetworkManager state is now CONNECTING Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6546] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Feb 25 08:24:59 asus0.nmset.info NetworkManager[4136]: <info> [1708845899.6531] device (eth0): Activation: starting connection 'ETH0' (ea1d83f9-2dd7-4769-bbe9-ecd6aa48ff3b)
Activating and deactivating NetworkManager-wait-online and NetworkManager- dispatcher do not help.
Reverting to networkmanager-1.44.2-3 and networkmanager-qt5-5.112.0-1 is a working temporary solution.
Devices:
- Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15); Kernel driver in use: r8169 - Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78); Kernel driver in use: iwlwifi
I'm reporting in the hope of a fix on the next upgrade.
Regards.
FWIW on my system Networkmanager ipv4 and ipv6 run ok.
Updated yesterday morning.
Networkmanager --version : 1.46.0-1
ip address :
2: enp0s25:
Hello, dear
Le dimanche 25 février 2024 08:38:52 CET SET a écrit :
not possible to establish IPV4 networking with networkmanager 1.46.0-1
Just a ping to say that the problem is resolved with networkmanager 1.46.0-2. Network connections are established as before. Regards.
participants (6)
-
Abraham S.A.H.
-
Daniel Ranc
-
Genes Lists
-
Merell L. Matlock, Jr.
-
SET
-
Zerro