A power cut this a.m had my Pi zero W reconnecting to the wrong wifi.
Which forced me to delve into the depths of network manager as evinced
by nmcli. Network manager is the new way to manage networks, and like systemd, its all changed for the sake of it
You probably can edit the files directly - mine were in /etc/NetworkManager/system-connections, but it's safer to use nmcli tools
You can set a priority if you have more than one wifi SSID.
sudo nmcli c modify <connection name> connection.autoconnect-priority 1
You can also force it to use 5Ghz or 2.4Ghz or let it decide
sudo nmcli c modify <connection name> 802-11-wireless.band "bg"
or
sudo nmcli c modify <connection name> 802-11-wireless.band "a"
"bg" is 2.4GHz, "a" is 5GHz.
It may well be that bookworm has changed the implicit defaults in
network manager.
It is well worth dumping the connections with
sudo nmcli connection show <connection name>
To work out what the connection names are, use
sudo nmcli c show
I think - but am not sure - that you can set more stuff through the
command line than through the GUI interface to network manager
On 27/10/2024 at 15:37, The Natural Philosopher wrote:
A power cut this a.m had my Pi zero W reconnecting to the wrong wifi.
Which forced me to delve into the depths of network manager as evinced
by nmcli. Network manager is the new way to manage networks, and like
systemd, its all changed for the sake of it
You probably can edit the files directly - mine were in
/etc/NetworkManager/system-connections, but it's safer to use nmcli tools
You can set a priority if you have more than one wifi SSID.
sudo nmcli c modify <connection name> connection.autoconnect-priority 1
You can also force it to use 5Ghz or 2.4Ghz or let it decide
sudo nmcli c modify <connection name> 802-11-wireless.band "bg"
or
sudo nmcli c modify <connection name> 802-11-wireless.band "a"
"bg" is 2.4GHz, "a" is 5GHz.
It may well be that bookworm has changed the implicit defaults in
network manager.
It is well worth dumping the connections with
sudo nmcli connection show <connection name>
To work out what the connection names are, use
sudo nmcli c show
I think - but am not sure - that you can set more stuff through the
command line than through the GUI interface to network manager
Have you tried nmtui?
A power cut this a.m had my Pi zero W reconnecting to the wrong wifi.
Which forced me to delve into the depths of network manager as evinced
by nmcli. Network manager is the new way to manage networks, and like systemd, its all changed for the sake of it
You probably can edit the files directly - mine were in /etc/NetworkManager/system-connections, but it's safer to use nmcli tools
You can set a priority if you have more than one wifi SSID.
sudo nmcli c modify <connection name> connection.autoconnect-priority 1
You can also force it to use 5Ghz or 2.4Ghz or let it decide
sudo nmcli c modify <connection name> 802-11-wireless.band "bg"
or
sudo nmcli c modify <connection name> 802-11-wireless.band "a"
"bg" is 2.4GHz, "a" is 5GHz.
It may well be that bookworm has changed the implicit defaults in
network manager.
It is well worth dumping the connections with
sudo nmcli connection show <connection name>
To work out what the connection names are, use
sudo nmcli c show
I think - but am not sure - that you can set more stuff through the
command line than through the GUI interface to network manager
After a bit more fumbling it appears that the wifi connects readily when
the wired ethernet is also connected.
After a bit more fumbling it appears that the wifi connects readily
when the wired ethernet is also connected. Maybe that's significant,
but exactly how isn't apparent to me.
The bookworm wifi saga continues. After a software update that
resulted in a black screen (fixed by rebooting from microSD,
which inexplicably mounted root from USB)
bp@www.zefox.net wrote:
After a bit more fumbling it appears that the wifi connects readily
when the wired ethernet is also connected. Maybe that's significant,
but exactly how isn't apparent to me.
The bookworm wifi saga continues. After a software update that
resulted in a black screen (fixed by rebooting from microSD,
which inexplicably mounted root from USB) the machine started
booting from USB but couldn't start the internal wifi.
After connecting a usb-wifi dongle and rebooting, first the usb-wifi interface came up unprompted and then the internal wifi came up a
moment later. Now both interfaces are up and working using 2417 MHz
channel 2 but different IPs.
So, it looks like the behavior of the internal wifi is dependent
on both wired ethernet and USB ethernet connectivity.
If anybody has thoughts on what I'm doing wrong please post. This
is becoming very confusing, unless it's just teething trouble with
bookworm.
Thanks for reading,
bob prohaska
On 06/11/2024 17:08, bp@www.zefox.net wrote:
The bookworm wifi saga continues. After a software update that
resulted in a black screen (fixed by rebooting from microSD,
which inexplicably mounted root from USB)
I had that.
Hadn't fully made the USB drive bootable.
bp@www.zefox.net wrote:
The bookworm wifi saga continues. After a software update that
resulted in a black screen (fixed by rebooting from microSD,
which inexplicably mounted root from USB) the machine started
booting from USB but couldn't start the internal wifi.
After connecting a usb-wifi dongle and rebooting, first the usb-wifi interface came up unprompted and then the internal wifi came up a
moment later. Now both interfaces are up and working using 2417 MHz
channel 2 but different IPs.
So, it looks like the behavior of the internal wifi is dependent
on both wired ethernet and USB ethernet connectivity.
If anybody has thoughts on what I'm doing wrong please post. This
is becoming very confusing, unless it's just teething trouble with
bookworm.
On 06/11/2024 17:08, bp@www.zefox.net wrote:
bp@www.zefox.net wrote:
The bookworm wifi saga continues. After a software update that
resulted in a black screen (fixed by rebooting from microSD,
which inexplicably mounted root from USB) the machine started
booting from USB but couldn't start the internal wifi.
After connecting a usb-wifi dongle and rebooting, first the usb-wifi
interface came up unprompted and then the internal wifi came up a
moment later. Now both interfaces are up and working using 2417 MHz
channel 2 but different IPs.
So, it looks like the behavior of the internal wifi is dependent
on both wired ethernet and USB ethernet connectivity.
It should not be, but I'm confused you mention USB-WiFi in one paragraph
and USB-Ethernet in another.
Did you start with a fresh Bookworm image?Initialy, yes. It was customized on microSD,
What have you installed since?Nothing apart from supplied upgrades, but I am using wayland, which
What other hardware is connected?One powered hub, running the added usb-wifi dongle
Are you using an official power supply?No, but the Pi5 reads 5.07 volts at the GPIO header.
Apologies for the mix-up. I meant to report that the behaviour of
the internal Wi-Fi seems to be affected by both use of wired Ethernet
and use of USB Wi-Fi. The internal Wi-Fi connected spontaneously after connecting either a wired Ethernet cable or a USB-wifi dongle. Alas,
that behaviour is not repeatable.
On 27/10/2024 15:37, The Natural Philosopher wrote:
A power cut this a.m had my Pi zero W reconnecting to the wrong wifi.
[Snip]
You can also force it to use 5Ghz or 2.4Ghz or let it decide
Hold on, the Zero W and the Zero 2 both only have 2.4GHz WiFi
The 2.4/5 GHz Pi's are the 3B+, 4B and 5.
On 11/11/2024 22:20, bp@www.zefox.net wrote:
Apologies for the mix-up. I meant to report that the behaviour of
the internal Wi-Fi seems to be affected by both use of wired Ethernet
and use of USB Wi-Fi. The internal Wi-Fi connected spontaneously after
connecting either a wired Ethernet cable or a USB-wifi dongle. Alas,
that behaviour is not repeatable.
I am still fighting a similar issue in that one of my pis will not sort
its dns out until its been sorted out so to speak.
The common factor is a service that wont work until connectivity that it should provide itself is already established.
I wonder if the wifi software needs access to something before it will
wake up.
Apolgies for the mixup. I meant to report that the behavior of
the internal wifi seems to be affected by both use of wired ethernet
and use of usb wifi. The internal wifi connected spontaneously after connecting either a wired ethernet cable or a usb-wifi dongle. Alas,
that behavior is not repeatable. In the present config the usb-wifi
dongle connects, I can't get the internal wifi to connect though
it does detect the access point.
There does seem to be a large discrepancy between wlan0 and wlan1
signal strength: wlan1 reports 93-96%, internal wlan0 only 79%.
Prior to the recent upgrades (but still bookworm) wlan0 reporting
more than about 70% gave a decent connection.
Did you start with a fresh Bookworm image?Initialy, yes. It was customized on microSD,
moved to a USB hard disk using Raspberry Pi Imager.
What have you installed since?Nothing apart from supplied upgrades, but I am using wayland, which
has been described as troublesome.
What other hardware is connected?One powered hub, running the added usb-wifi dongle
(old Ralink RT5370) plus an old Dell keyboard and mouse..
Are you using an official power supply?No, but the Pi5 reads 5.07 volts at the GPIO header.
As this saga plays out the USB-Wifi dongle seems to
work quite well. Maybe it's all down to the better
signal strength. Because the problem appeared shortly
after an OS upgrade I tended to blame that. Perhaps
I'm mistaken.
On 11/11/2024 22:20, bp@www.zefox.net wrote:
Apolgies for the mixup. I meant to report that the behavior of
the internal wifi seems to be affected by both use of wired ethernet
and use of usb wifi. The internal wifi connected spontaneously after
connecting either a wired ethernet cable or a usb-wifi dongle. Alas,
that behavior is not repeatable. In the present config the usb-wifi
dongle connects, I can't get the internal wifi to connect though
it does detect the access point.
That does sound like some of the Network Manager behaviour I've
experienced on a couple of Linux Mint laptops.
There does seem to be a large discrepancy between wlan0 and wlan1
signal strength: wlan1 reports 93-96%, internal wlan0 only 79%.
Prior to the recent upgrades (but still bookworm) wlan0 reporting
more than about 70% gave a decent connection.
The WiFi antenna on the motherboard is very small, as long as it's a
normal sized USB WiFi stuck and not one of the tiny nub ones, it's
antenna will be far bigger.
That's why I used dongles in the shed at the bottom of the garden for
years with the Pi 1 and then 2, as the signal strength was better than a
Pi 3 with built in WiFi, although the reliability of the dongles wasn't great. Incidentally I'm now using my first Asus router as an Ethernet to
WiFi bridge, which connects to the house easily over 5GHz with it's
large triple antenna.
Did you start with a fresh Bookworm image?Initialy, yes. It was customized on microSD,
moved to a USB hard disk using Raspberry Pi Imager.
So it's a vanilla install using NetWork Manager and not an upgrade from Bullseye as I've been doing to retain the old well working DHCPCD and
WPA supplicant networking.
What have you installed since?Nothing apart from supplied upgrades, but I am using wayland, which
has been described as troublesome.
It can be, but not usually to networking.
What other hardware is connected?One powered hub, running the added usb-wifi dongle
(old Ralink RT5370) plus an old Dell keyboard and mouse..
Are you using an official power supply?No, but the Pi5 reads 5.07 volts at the GPIO header.
As this saga plays out the USB-Wifi dongle seems to
work quite well. Maybe it's all down to the better
signal strength. Because the problem appeared shortly
after an OS upgrade I tended to blame that. Perhaps
I'm mistaken.
Normally on Pi's I'd be looking at a hardware issue to do with the power supply and the amount of USB devices connected, but I think you are
right in this case, and it's Network Manager getting confused about what interfaces are available.
---druck
On 12/11/2024 17:54, druck wrote:
On 11/11/2024 22:20, bp@www.zefox.net wrote:Or perhaps what priority order they are to be selected in.
Apolgies for the mixup. I meant to report that the behavior of
the internal wifi seems to be affected by both use of wired ethernet
and use of usb wifi. The internal wifi connected spontaneously after
connecting either a wired ethernet cable or a usb-wifi dongle. Alas,
that behavior is not repeatable. In the present config the usb-wifi
dongle connects, I can't get the internal wifi to connect though
it does detect the access point.
That does sound like some of the Network Manager behaviour I've
experienced on a couple of Linux Mint laptops.
There does seem to be a large discrepancy between wlan0 and wlan1
signal strength: wlan1 reports 93-96%, internal wlan0 only 79%.
Prior to the recent upgrades (but still bookworm) wlan0 reporting
more than about 70% gave a decent connection.
The WiFi antenna on the motherboard is very small, as long as it's a
normal sized USB WiFi stuck and not one of the tiny nub ones, it's
antenna will be far bigger.
That's why I used dongles in the shed at the bottom of the garden for
years with the Pi 1 and then 2, as the signal strength was better than a
Pi 3 with built in WiFi, although the reliability of the dongles wasn't
great. Incidentally I'm now using my first Asus router as an Ethernet to
WiFi bridge, which connects to the house easily over 5GHz with it's
large triple antenna.
Did you start with a fresh Bookworm image?Initialy, yes. It was customized on microSD,
moved to a USB hard disk using Raspberry Pi Imager.
So it's a vanilla install using NetWork Manager and not an upgrade from
Bullseye as I've been doing to retain the old well working DHCPCD and
WPA supplicant networking.
What have you installed since?Nothing apart from supplied upgrades, but I am using wayland, which
has been described as troublesome.
It can be, but not usually to networking.
What other hardware is connected?One powered hub, running the added usb-wifi dongle
(old Ralink RT5370) plus an old Dell keyboard and mouse..
Are you using an official power supply?No, but the Pi5 reads 5.07 volts at the GPIO header.
As this saga plays out the USB-Wifi dongle seems to
work quite well. Maybe it's all down to the better
signal strength. Because the problem appeared shortly
after an OS upgrade I tended to blame that. Perhaps
I'm mistaken.
Normally on Pi's I'd be looking at a hardware issue to do with the power
supply and the amount of USB devices connected, but I think you are
right in this case, and it's Network Manager getting confused about what
interfaces are available.
Perhaps its insisting on Ethernet before it brings up wifi etc etc.
For now I'll plan to use a WiFi dongle on the Pi5 and watch what happens.
bp@www.zefox.net wrote:
Just got a new usb-wifi adapter, a TP-Link AC1300 which works on both
2.4 and 5 GHz (the old dongle was 2.4 GHz only). It worked on the fly
out of the box, No problems whatsoever. I wondered if access to 5 GHz
bands might sidetrack the connection process, but not at all.
There is still a problem with NetworkManager-wait-online.service
failing regardless of which dongle is used. No ill effect seems
to result, but it is strange.
| Sysop: | Nitro |
|---|---|
| Location: | Portland, OR |
| Users: | 4 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 217:45:00 |
| Calls: | 139 |
| Files: | 752 |
| Messages: | 87,380 |