On 30/10/2024 08:20, Tauno Voipio wrote:
dhcpcd is not needed: systemd-networkd contains a pretty good DHCP
client when properly configured.
I have no desire to give any more control of my systems to the systemd
virus.
On 29/10/2024 21:08, Lawrence D'Oliveiro wrote:
On Tue, 29 Oct 2024 20:28:40 +0000, druck wrote:
Quite often my Linux Laptops which use Network Manager decide
they would like to try WiFi networks other than the one I've chosen,
that's easily fixed via the gui, but not what you want on headless
systems.
You could use nmcli to control it.
If you can log in to a headless system which isn't connecting to the Wifi.
---druck
On 30/10/2024 16:18, bp@www.zefox.net wrote:
druck <news@druck.org.uk> wrote:
This is why I wasn't happy about Raspbian moving from dhcpcd to Network
Manager. Quite often my Linux Laptops which use Network Manager decide
they would like to try WiFi networks other than the one I've chosen,
that's easily fixed via the gui, but not what you want on headless
systems.
Were the unwanted wifi explorations immediate and consistent,
Seemingly random.
You could try disabling the NetworkManager service, and reinstalling
dhcpcd so the WiFi is only selected by the contents of the
wpa_supplicant.conf file. It worked fine for everything before Bookworm. >>>
It seems wiser to learn how to live with Bookworm sooner rather than
later.
Up to now RasPiOS has been trouble-free to the point that I know very
little
about it. Trying to second-guess the developers is likely to end badly,
at least when I'm the one doing the guessing 8-)
The maturity of Raspbian's Bookworm is there yet. I had to jump to it
for my new Pi 5 machines, and I've also got it on a Pi 4 for reference,
but the older headless machines are staying on Bullseye until some of
the problems have been ironed out.
Well at least all headless Pis will run a console session via some form
of USB keyboard and HDMI screen.
On 30/10/2024 21:24, druck wrote:
On 29/10/2024 21:08, Lawrence D'Oliveiro wrote:Well at least all headless Pis will run a console session via some form
On Tue, 29 Oct 2024 20:28:40 +0000, druck wrote:
Quite often my Linux Laptops which use Network Manager decide
they would like to try WiFi networks other than the one I've chosen,
that's easily fixed via the gui, but not what you want on headless
systems.
You could use nmcli to control it.
If you can log in to a headless system which isn't connecting to the
Wifi.
of USB keyboard and HDMI screen. You wont need a mouse so one USB port
is enough
That what I have used when faced with loss of of connectivity.
However, when using Network Manager, it sometimes decides to try a
different network ...
A Raspberry Pi still has a built-in Ethernet interface, doesn’t it?
If it was in range of an Ethernet switch, I wouldn't be using WiFi!
However, when using Network Manager, it sometimes decides to try a
different network, leaving a remote headless Pi stuffed. Whilst all my 'desktop/media' Pi's (connected to monitors and keyboards) are on
Bookworm, all the headless ones are remaining on Bullseye for the time
being.
On 31/10/2024 21:54, druck wrote:
However, when using Network Manager, it sometimes decides to try a
different network, leaving a remote headless Pi stuffed. Whilst all my
'desktop/media' Pi's (connected to monitors and keyboards) are on
Bookworm, all the headless ones are remaining on Bullseye for the time
being.
I already told you the solution to that.
There is a priority system in network manager.
Otherwise it will connect to whatever it connected to last time, or
sometimes not
If you have more than one connection profile use:
sudo nmcli c modify MYCONNECTIONNAME connection.autoconnect-priority 1
Randomly created connections are default priority zero
This is also an accessible parameter from the GUI widget if you have a
GUI interface
It will then at least try only that SSID *first*
Or delete any alternative connection profiles.
On Wed, 30 Oct 2024 21:26:30 +0000, druck wrote:
On 30/10/2024 08:20, Tauno Voipio wrote:
dhcpcd is not needed: systemd-networkd contains a pretty good DHCP
client when properly configured.
I have no desire to give any more control of my systems to the systemd
virus.
Give people a way out of their pain, some people prefer the pain.
Why? Answers on a postcard, please.
On 01/11/2024 12:50, druck wrote:
Except it doesn't actually work all the time. I've set up all my Pi'sThen delete the 2,4 GHZ SSID...
which have both 2.4 GHz and 5 GHz WiFi with a higher priority to the
5GHz network which has a different SSID to the 2.4 GHz one. Most of
the time they honour that but occasionally I find one has switched
back to 2.4 GHz, and it's not because the 5GHz signal strength has
dropped according to the logging.
On 01/11/2024 10:24, The Natural Philosopher wrote:
On 31/10/2024 21:54, druck wrote:
However, when using Network Manager, it sometimes decides to try a
different network, leaving a remote headless Pi stuffed. Whilst all
my 'desktop/media' Pi's (connected to monitors and keyboards) are on
Bookworm, all the headless ones are remaining on Bullseye for the
time being.
I already told you the solution to that.
There is a priority system in network manager.
Otherwise it will connect to whatever it connected to last time, or
sometimes not
If you have more than one connection profile use:
sudo nmcli c modify MYCONNECTIONNAME connection.autoconnect-priority 1 >>
Randomly created connections are default priority zero
This is also an accessible parameter from the GUI widget if you have a
GUI interface
It will then at least try only that SSID *first*
Or delete any alternative connection profiles
Except it doesn't actually work all the time. I've set up all my Pi's
which have both 2.4 GHz and 5 GHz WiFi with a higher priority to the
5GHz network which has a different SSID to the 2.4 GHz one. Most of the
time they honour that but occasionally I find one has switched back to
2.4 GHz, and it's not because the 5GHz signal strength has dropped
according to the logging.
Network manager has not yet reached the required level of stability.
---druck
On 01/11/2024 13:47, The Natural Philosopher wrote:
On 01/11/2024 12:50, druck wrote:
Except it doesn't actually work all the time. I've set up all my Pi'sThen delete the 2,4 GHZ SSID...
which have both 2.4 GHz and 5 GHz WiFi with a higher priority to the
5GHz network which has a different SSID to the 2.4 GHz one. Most of
the time they honour that but occasionally I find one has switched
back to 2.4 GHz, and it's not because the 5GHz signal strength has
dropped according to the logging.
That's really not the point is it.
---druck
On 01/11/2024 14:15, druck wrote:
On 01/11/2024 13:47, The Natural Philosopher wrote:
On 01/11/2024 12:50, druck wrote:
Except it doesn't actually work all the time. I've set up all myThen delete the 2,4 GHZ SSID...
Pi's which have both 2.4 GHz and 5 GHz WiFi with a higher priority
to the 5GHz network which has a different SSID to the 2.4 GHz one.
Most of the time they honour that but occasionally I find one has
switched back to 2.4 GHz, and it's not because the 5GHz signal
strength has dropped according to the logging.
That's really not the point is it.
---druck
It is. If you have an SSID registerd with the Pi that is 2.4GHZ its
going to sometimes connect to it
So remove it from the PI. It then wont know it exists.
On 01/11/2024 at 15:16, The Natural Philosopher wrote:
On 01/11/2024 14:15, druck wrote:
On 01/11/2024 13:47, The Natural Philosopher wrote:
On 01/11/2024 12:50, druck wrote:
Except it doesn't actually work all the time. I've set up all myThen delete the 2,4 GHZ SSID...
Pi's which have both 2.4 GHz and 5 GHz WiFi with a higher priority
to the 5GHz network which has a different SSID to the 2.4 GHz one.
Most of the time they honour that but occasionally I find one has
switched back to 2.4 GHz, and it's not because the 5GHz signal
strength has dropped according to the logging.
That's really not the point is it.
---druck
It is. If you have an SSID registerd with the Pi that is 2.4GHZ its
going to sometimes connect to it
So remove it from the PI. It then wont know it exists.
Well it will still know it exists; it just won't know the password for it.
On 31/10/2024 00:00, Lawrence D'Oliveiro wrote:
On Wed, 30 Oct 2024 21:26:30 +0000, druck wrote:
On 30/10/2024 08:20, Tauno Voipio wrote:
dhcpcd is not needed: systemd-networkd contains a pretty good DHCP
client when properly configured.
I have no desire to give any more control of my systems to the systemd
virus.
Give people a way out of their pain, some people prefer the pain.
Anything to do with systemd is enviably more pain.
On 01/11/2024 14:15, druck wrote:
On 01/11/2024 13:47, The Natural Philosopher wrote:
On 01/11/2024 12:50, druck wrote:
Except it doesn't actually work all the time. I've set up all myThen delete the 2,4 GHZ SSID...
Pi's which have both 2.4 GHz and 5 GHz WiFi with a higher priority
to the 5GHz network which has a different SSID to the 2.4 GHz one.
Most of the time they honour that but occasionally I find one has
switched back to 2.4 GHz, and it's not because the 5GHz signal
strength has dropped according to the logging.
That's really not the point is it.
It is. If you have an SSID registerd with the Pi that is 2.4GHZ its
going to sometimes connect to it
So remove it from the PI. It then wont know it exists.
On 01/11/2024 15:16, The Natural Philosopher wrote:
On 01/11/2024 14:15, druck wrote:
On 01/11/2024 13:47, The Natural Philosopher wrote:
On 01/11/2024 12:50, druck wrote:
Except it doesn't actually work all the time. I've set up all myThen delete the 2,4 GHZ SSID...
Pi's which have both 2.4 GHz and 5 GHz WiFi with a higher priority
to the 5GHz network which has a different SSID to the 2.4 GHz one.
Most of the time they honour that but occasionally I find one has
switched back to 2.4 GHz, and it's not because the 5GHz signal
strength has dropped according to the logging.
That's really not the point is it.
It is. If you have an SSID registerd with the Pi that is 2.4GHZ its
going to sometimes connect to it
So remove it from the PI. It then wont know it exists.
No it's not. You are recommending the use of Network Manager instead of DHCPCD/WPA_Supplicant for headless Pi's, when it has serious problems
which I and others have detailed. Your response is to suggest an
increasing number of workarounds, some of which reduce useful
functionality.
The reason the 2.4GHz SSID is configured is in case the Pi needs to be relocated to another part of the property where 5 GHz is too weak.
has never been a problem when using DHCPCD/WPA_Supplicant, so I'm not
about to remove it in order to use a flaky Network Manager.
The sensible solution is to use the correct tool for the job, rather
than whatever happens to be installed by default by Raspbian. This is an advantage of Linux, instead of being stuck with whatever Microsoft
mandates you should use in Windows.
---druck
On 01/11/2024 20:40, druck wrote:
The sensible solution is to use the correct tool for the job, rather
than whatever happens to be installed by default by Raspbian. This is
an advantage of Linux, instead of being stuck with whatever Microsoft
mandates you should use in Windows.
---druck
If you want to tread a lone path that is your privilege.
Don't expect support from those who have chosen to understand the main
road.
On 02/11/2024 11:10, The Natural Philosopher wrote:
On 01/11/2024 20:40, druck wrote:
The sensible solution is to use the correct tool for the job, rather
than whatever happens to be installed by default by Raspbian. This is
an advantage of Linux, instead of being stuck with whatever Microsoft
mandates you should use in Windows.
---druck
If you want to tread a lone path that is your privilege.
Don't expect support from those who have chosen to understand the main
road.
I hate to interrupt your argument, but I'm the one giving support not
asking for it. Remind me what your motivation is again?
---druck
| Sysop: | Tetrazocine |
|---|---|
| Location: | Melbourne, VIC, Australia |
| Users: | 14 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 71:21:19 |
| Calls: | 178 |
| Files: | 21,502 |
| Messages: | 79,639 |