From: news@druck.org.uk   
      
   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 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.   
   >>>>   
   >>> Then delete the 2,4 GHZ SSID...   
   >>   
   >> 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. This   
   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   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)