INTL 3:770/1 3:770/3   
   REPLYADDR bp@www.zefox.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID: 6b6b4164   
   REPLY: 50562d8c   
   PID: SoupGate-Win32 v1.05   
   Lawrence D'Oliveiro wrote:   
   > On Mon, 23 Sep 2024 16:38:25 -0000 (UTC), bp wrote:   
   >   
   >> Why is still unclear.   
   >   
   > You didn’t check the logs with journalctl, as I suggested?   
      
   I don't know what to look for.   
      
   The problem seemed solved by explicitly requiring wlan0   
   in Network > Advanced Options > preconfigured > Device.   
      
   At your prompting I did run   
   journalctl | grep -i wlan0 | grep -i failed   
   which yielded a repeating pattern of messages ending with:   
      
   Sep 22 09:30:54 raspberrypi wpa_supplicant[823]: wlan0: CTRL-EVE   
   T-SSID-TEMP-DISABLED id=0 ssid="d-link.zefox.net" auth_failures=1 duration=10   
   reason=CONN_FAILED   
   Sep 22 09:31:11 raspberrypi wpa_supplicant[823]: wlan0: CTRL-EVE   
   T-SSID-TEMP-DISABLED id=0 ssid="d-link.zefox.net" auth_failures=2 duration=20   
   reason=CONN_FAILED   
   Sep 22 09:31:27 raspberrypi wpa_supplicant[823]: wlan0: CTRL-EVE   
   T-SSID-TEMP-DISABLED id=0 ssid="d-link.zefox.net" auth_failures=1 duration=10   
   reason=CONN_FAILED   
   Sep 22 09:31:44 raspberrypi wpa_supplicant[823]: wlan0: CTRL-EVE   
   T-SSID-TEMP-DISABLED id=0 ssid="d-link.zefox.net" auth_failures=2 duration=20   
   reason=CONN_FAILED   
   Sep 22 09:31:45 raspberrypi wpa_supplicant[823]: wlan0: CTRL-EVE   
   T-SSID-TEMP-DISABLED id=0 ssid="d-link.zefox.net" auth_failures=1 duration=10   
   reason=CONN_FAILED   
   Sep 22 09:32:02 raspberrypi wpa_supplicant[823]: wlan0: CTRL-EVE   
   T-SSID-TEMP-DISABLED id=0 ssid="d-link.zefox.net" auth_failures=2 duration=20   
   reason=CONN_FAILED   
   Sep 22 09:32:10 raspberrypi NetworkManager[821]: [1727022730.2605]   
   device (wlan0): state change: config -> failed (reason 'no-secrets',   
   sys-iface-state: 'managed')   
   Sep 22 09:32:10 raspberrypi NetworkManager[821]: [1727022730.2612]   
   device (wlan0): Activation: failed for connection 'preconfigured'   
   Sep 22 09:32:10 raspberrypi NetworkManager[821]: [1727022730.2614]   
   device (wlan0): state change: failed -> disconnected (reason 'none',   
   sys-iface-state: 'managed')   
   as the last block of text. No errors after   
   roughly the time I changed the network settings to add Device wlan0,   
   which was done mid-morning on the 22nd, I think.   
      
   Running   
   journalctl | grep -i wlan0 | grep -i success   
   produced much output, ending with   
   Sep 22 09:35:14 raspberrypi NetworkManager[821]: [1727022914.3489]   
   device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.   
   Connected to wireless network "d-link.zefox.net"   
   Sep 22 09:35:14 raspberrypi NetworkManager[821]: [1727022914.5427]   
   device (wlan0): Activation: successful, device activated.   
   Sep 23 09:12:57 raspberrypi NetworkManager[819]: [1727107977.4602]   
   device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.   
   Connected to wireless network "d-link.zefox.net"   
   Sep 23 09:12:57 raspberrypi NetworkManager[819]: [1727107977.6547]   
   device (wlan0): Activation: successful, device activated.   
      
   The timestamp gap from Sep 22 to Sep 23 matches the pause before I   
   made the Device wlan0 change.   
      
   This isn't very clever use of journalctl, admittedly, and I don't really   
   understand what it's showing me now.   
      
   Running   
   journalctl | grep -i wlan0 | grep -i supplicant-failed   
   produces just three lines:   
   Sep 21 07:36:41 raspberrypi NetworkManager[826]: [1726929401.0115]   
   device (p2p-dev-wlan0): state change: disconnected -> unavailable (reason   
   'supplicant-failed', sys-iface-state: 'managed')   
   Sep 21 07:38:51 raspberrypi NetworkManager[826]: [1726929531.4462]   
   device (p2p-dev-wlan0): state change: disconnected -> unavailable (reason   
   'supplicant-failed', sys-iface-state: 'managed')   
   Sep 22 08:05:07 raspberrypi NetworkManager[821]: [1727017507.7245]   
   device (p2p-dev-wlan0): state change: disconnected -> unavailable (reason   
   'supplicant-failed', sys-iface-state: 'managed')   
      
   If any of this makes sense please clue me in. Meanwhile wifi seems to work,   
   so I can get back to wrestling with your TLS exercises.   
      
   Thanks for all your help!   
      
   bob prohaska   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 19/38 90/1 105/81 106/201 129/305 153/757 7715 218/700 840   
   SEEN-BY: 220/70 226/17 30 100 227/114 229/110 111 114 200 206 300   
   SEEN-BY: 229/317 400 426 428 470 550 616 664 700 266/512 267/800 282/1038   
   SEEN-BY: 291/111 292/854 310/31 320/219 322/757 342/200 396/45 460/58   
   SEEN-BY: 633/280 281 412 418 420 509 2744 712/848 770/1 3 100 330   
   SEEN-BY: 770/340 772/210 220 230 5020/400 5075/35   
   PATH: 770/3 1 633/280 229/426   
      
|