Cannot connect to wifi network

inxi

System:
  Kernel: 5.19.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=21c7fde8-1bef-4f82-abc8-364dad2d6848 rw [email protected]
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1
    resume=UUID=59131e58-a432-49f0-bae1-aebf3325230e loglevel=3 ibt=off
  Desktop: KDE Plasma v: 5.25.4 tk: Qt v: 5.15.5 info: latte-dock
    wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: HP product: OMEN by HP Laptop 15-dc1xxx v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 8574 v: 21.17 serial: <superuser required> UEFI: AMI
    v: F.22 date: 05/03/2021
Battery:
  ID-1: BAT0 charge: 45.8 Wh (100.0%) condition: 45.8/45.8 Wh (100.0%)
    volts: 17.4 min: 15.4 model: HP Primary type: Li-ion serial: N/A
    status: full
CPU:
  Info: model: Intel Core i7-9750H bits: 64 type: MT MCP arch: Coffee Lake
    gen: core 9 built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158)
    stepping: 0xD (13) microcode: 0xF0
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 1850 high: 2600 min/max: 800/4500 scaling:
    driver: intel_pstate governor: powersave cores: 1: 1100 2: 2600 3: 2600
    4: 1100 5: 1101 6: 2600 7: 1100 8: 1100 9: 2600 10: 2600 11: 2600
    12: 1100 bogomips: 62399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB
    filling, PBRSB-eIBRS: SW sequence
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Hewlett-Packard
    driver: nvidia v: 515.65.01 alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-07) arch: Turing code: TUxxx
    process: TSMC 12nm built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8
    link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:1f11 class-ID: 0300
  Device-2: Lite-On HP Wide Vision HD Camera type: USB driver: uvcvideo
    bus-ID: 1-6:3 chip-ID: 04ca:707f class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3
    compositors: 1: kwin_x11 2: Tabby driver: X: loaded: nvidia gpu: nvidia
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 143 s-size: 341x191mm (13.43x7.52")
    s-diag: 391mm (15.39")
  Monitor-1: DP-2 res: 1920x1080 hz: 60 dpi: 142
    size: 344x194mm (13.54x7.64") diag: 395mm (15.55") modes: N/A
  OpenGL: renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2 v: 4.6.0 NVIDIA
    515.65.01 direct render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    chip-ID: 8086:a348 class-ID: 0403
  Device-2: NVIDIA TU106 High Definition Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f9 class-ID: 0403
  Sound Server-1: ALSA v: k5.19.2-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 16.1 running: no
  Sound Server-3: PipeWire v: 0.3.56 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 3c:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 3d:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  IF-ID-1: br-da2c536dbf10 state: down mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
  IF-ID-3: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-7:4 chip-ID: 8087:0029 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 port: 5020 bus-ID: 00:17.0 chip-ID: 8086:282a rev: N/A
    class-ID: 0104
Drives:
  Local Storage: total: 1.84 TiB used: 62.46 GiB (3.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZVLB1T0HBLR-000H1 size: 953.87 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: HPS0NEXF temp: 45.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 1B6Q scheme: GPT
Partition:
  ID-1: / raw-size: 896.9 GiB size: 896.9 GiB (100.00%) used: 62.46 GiB
    (7.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%) used: 563 KiB
    (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 896.9 GiB size: 896.9 GiB (100.00%) used: 62.46 GiB
    (7.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 896.9 GiB size: 896.9 GiB (100.00%) used: 62.46
    GiB (7.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 896.9 GiB size: 896.9 GiB (100.00%) used: 62.46
    GiB (7.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 31.23 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 34.36 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
  System Temperatures: cpu: 83.0 C pch: 54.0 C mobo: N/A gpu: nvidia
    temp: 55 C
  Fan Speeds (RPM): cpu: 2393 fan-2: 2207
Info:
  Processes: 338 Uptime: 4m wakeups: 1 Memory: 31.23 GiB used: 4.03 GiB
  (12.9%) Init: systemd v: 251 default: graphical tool: systemctl
  Compilers: gcc: 12.1.1 Packages: pacman: 1687 lib: 498 Shell: fish v: 3.5.1
  running-in: tabby inxi: 3.3.20
Garuda (2.6.6-1):
  System install date:     2021-07-24
  Last full system update: 2022-08-20
  Is partially upgraded:   No
  Relevant software:       tlp NetworkManager
  Windows dual boot:       Probably (Run as root to verify)
  Snapshots:               Timeshift (maybe)
  Failed units:

Hello community,

I have problems connecting to previously used wifi network. After changing authentication method on my router - was previously WPA2/3-EAP to only WPA2/3 - NetworkManager gets stuck on "Configuring interface" and never connects. I've tried removing the connection altogether from NM and reentering the password without success. I can connect to other SSIDs broadcasted by the router and previously never used just fine. There is no issue in the router (Mikrotik), logs show nothing and other devices can connect w/o problems. There is also no IP conflict, I've reseted the routers DHCP leases, also without success.

Any help in this matter would be greatly appreciated.

Thanks in advance!

Have you tried reverting this change?

3 Likes

Nope.

It was just a test in my homelab. Because the router has NAND memory there is a risk of destroying it with constant writes into it - and using EAP registers sessions IDs and everything into it.

Everything else works fine - other SSID which is using exactly the same authentication method / only different password works w/o problems.

Is there any way to reset NetworkManager completely? I suspect deleting the connection wasn't enough for some reason.

Then how do you know that was the cause?

2 Likes

Yesterday before I turned off my system it was working w/o problem when it was connected via old WPA2/3-EAP. Then from another computer I've changed security to WPA2/3. Today I can't connect to that SSID, but I can connect to other SSIDs that are broadcasted by my router. Only that one which was set to EAP won't work.

However I can connect to that SSID which had EAP and now has only WPA2/3 from another computer just fine, from my phone, from my smart TV, so I know the problem is not in the rouer.

This is the output of journalctl

srp 24 15:47:44 mikoshi NetworkManager[793]: <info>  [1661348864.9206] device (wlo1): Activation: (wifi) connection '☢ Lord Voldemodem ☢' has security, and secrets exist.  No new secrets needed.
srp 24 15:47:44 mikoshi NetworkManager[793]: <info>  [1661348864.9207] Config: added 'ssid' value '☢ Lord Voldemodem ☢'
srp 24 15:47:44 mikoshi NetworkManager[793]: <info>  [1661348864.9207] Config: added 'scan_ssid' value '1'
srp 24 15:47:44 mikoshi NetworkManager[793]: <info>  [1661348864.9207] Config: added 'bgscan' value 'simple:30:-70:86400'
srp 24 15:47:44 mikoshi NetworkManager[793]: <info>  [1661348864.9207] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
srp 24 15:47:44 mikoshi NetworkManager[793]: <info>  [1661348864.9207] Config: added 'auth_alg' value 'OPEN'
srp 24 15:47:44 mikoshi NetworkManager[793]: <info>  [1661348864.9207] Config: added 'psk' value '<hidden>'
srp 24 15:47:44 mikoshi NetworkManager[793]: <info>  [1661348864.9500] device (wlo1): supplicant interface state: disconnected -> scanning
srp 24 15:47:44 mikoshi NetworkManager[793]: <info>  [1661348864.9501] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning
srp 24 15:47:46 mikoshi NetworkManager[793]: <info>  [1661348866.4986] device (wlo1): supplicant interface state: scanning -> authenticating
srp 24 15:47:46 mikoshi NetworkManager[793]: <info>  [1661348866.4987] device (p2p-dev-wlo1): supplicant management interface state: scanning -> authenticating
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.7133] device (wlo1): supplicant interface state: authenticating -> associating
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.7134] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.7508] device (wlo1): supplicant interface state: associating -> associated
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.7508] device (p2p-dev-wlo1): supplicant management interface state: associating -> associated
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.8295] device (wlo1): supplicant interface state: associated -> 4way_handshake
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.8295] device (p2p-dev-wlo1): supplicant management interface state: associated -> 4way_handshake
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.8732] device (wlo1): supplicant interface state: 4way_handshake -> completed
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.8733] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "☢ Lord Voldemodem ☢"
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.8733] device (p2p-dev-wlo1): supplicant management interface state: 4way_handshake -> completed
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.8733] device (wlo1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.8736] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.9066] dhcp4 (wlo1): state changed new lease, address=10.100.10.116
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.9069] policy: set '☢ Lord Voldemodem ☢' (wlo1) as default for IPv4 routing and DNS
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.9156] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.9173] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.9175] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.9178] manager: NetworkManager state is now CONNECTED_SITE
srp 24 15:47:48 mikoshi NetworkManager[793]: <info>  [1661348868.9194] device (wlo1): Activation: successful, device activated.
srp 24 15:47:49 mikoshi NetworkManager[793]: <info>  [1661348869.0241] manager: NetworkManager state is now CONNECTED_GLOBAL
srp 24 15:48:17 mikoshi NetworkManager[793]: <info>  [1661348897.8861] audit: op="connection-delete" uuid="27a01034-1de1-43bd-a6e5-3815479ae18a" name="🔒 Voldemodem - Private" pid=3488 uid=1000 result="fail" reason="Error checking aut>
srp 24 15:48:17 mikoshi NetworkManager[793]: <info>  [1661348897.8862] audit: op="connection-delete" uuid="27a01034-1de1-43bd-a6e5-3815479ae18a" name="🔒 Voldemodem - Private" pid=3488 uid=1000 result="success"
srp 24 15:50:19 mikoshi NetworkManager[793]: <info>  [1661349019.0982] audit: op="statistics" interface="wlo1" ifindex=3 args="2000" pid=2327 uid=1000 result="success"
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.8395] device (wlo1): disconnecting for new activation request.
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.8395] device (wlo1): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.8401] audit: op="connection-add-activate" uuid="8f3174de-1488-4dff-9bab-dad3802e6bd9" name="🔒 Voldemodem - Private" pid=2327 uid=1000 result="success"
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.8581] audit: op="statistics" interface="br-da2c536dbf10" ifindex=5 args="0" pid=2327 uid=1000 result="success"
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9285] device (wlo1): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9412] dhcp4 (wlo1): canceled DHCP transaction
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9413] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9413] dhcp4 (wlo1): state changed no lease
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9522] device (wlo1): set-hw-addr: set MAC address to CA:21:46:E4:75:A4 (scanning)
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9596] device (wlo1): Activation: starting connection '🔒 Voldemodem - Private' (8f3174de-1488-4dff-9bab-dad3802e6bd9)
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9606] device (wlo1): supplicant interface state: completed -> disconnected
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9607] device (p2p-dev-wlo1): supplicant management interface state: completed -> disconnected
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9620] device (wlo1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9626] manager: NetworkManager state is now CONNECTING
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9720] device (wlo1): set-hw-addr: reset MAC address to 60:F2:62:F2:EC:3E (preserve)
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9756] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9761] device (wlo1): Activation: (wifi) access point '🔒 Voldemodem - Private' has security, but secrets are required.
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9761] device (wlo1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9777] device (wlo1): supplicant interface state: disconnected -> interface_disabled
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9778] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> interface_disabled
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9915] device (wlo1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9921] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9926] device (wlo1): Activation: (wifi) connection '🔒 Voldemodem - Private' has security, and secrets exist.  No new secrets needed.
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9926] Config: added 'ssid' value '🔒 Voldemodem - Private'
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9927] Config: added 'scan_ssid' value '1'
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9927] Config: added 'bgscan' value 'simple:30:-70:86400'
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9927] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9927] Config: added 'auth_alg' value 'OPEN'
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9928] Config: added 'psk' value '<hidden>'
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9959] device (wlo1): supplicant interface state: interface_disabled -> disconnected
srp 24 15:50:27 mikoshi NetworkManager[793]: <info>  [1661349027.9960] device (p2p-dev-wlo1): supplicant management interface state: interface_disabled -> disconnected
srp 24 15:50:29 mikoshi NetworkManager[793]: <info>  [1661349029.0180] device (wlo1): supplicant interface state: disconnected -> scanning
srp 24 15:50:29 mikoshi NetworkManager[793]: <info>  [1661349029.0180] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning
srp 24 15:50:29 mikoshi NetworkManager[793]: <info>  [1661349029.7379] device (wlo1): supplicant interface state: scanning -> authenticating
srp 24 15:50:29 mikoshi NetworkManager[793]: <info>  [1661349029.7380] device (p2p-dev-wlo1): supplicant management interface state: scanning -> authenticating
srp 24 15:50:41 mikoshi NetworkManager[793]: <info>  [1661349041.5663] device (wlo1): supplicant interface state: authenticating -> scanning
srp 24 15:50:41 mikoshi NetworkManager[793]: <info>  [1661349041.5664] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> scanning
srp 24 15:50:41 mikoshi NetworkManager[793]: <info>  [1661349041.5705] device (wlo1): supplicant interface state: scanning -> disconnected
srp 24 15:50:41 mikoshi NetworkManager[793]: <info>  [1661349041.5705] device (p2p-dev-wlo1): supplicant management interface state: scanning -> disconnected
srp 24 15:50:41 mikoshi NetworkManager[793]: <info>  [1661349041.6898] device (wlo1): supplicant interface state: disconnected -> authenticating
srp 24 15:50:41 mikoshi NetworkManager[793]: <info>  [1661349041.6898] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> authenticating
srp 24 15:50:46 mikoshi NetworkManager[793]: <info>  [1661349046.8528] device (wlo1): supplicant interface state: authenticating -> disconnected
srp 24 15:50:46 mikoshi NetworkManager[793]: <info>  [1661349046.8528] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> disconnected

There are no logs in the router.

That appears to be wrong.

Network Manager connection settings are stored under /etc/NetworkManager/system-connections , so if deleting that doesn't work it's not the connection settings with the problem.

3 Likes

Yea, I see that it tries to set this value even when I manually set WPA2-Personal in the NetworkManager.

What I do not understand is that the network security in the router is set up exactly the same on both SSIDs, only the passwords are different.

SSID with sec_home is working in Garuda and everywhere else. SSID with sec_private is working everywhere else, but not in Garuda.

Also thinking, it will be worth disabling WPA3 to see if that makes a difference. It might be that you were connecting using WPA2 previously without realising it?

4 Likes

Oh, sorry, forgot to write the solution here.

Yep, it was the SAE (WPA3). After turning it off, both networks started working correctly. I don't know where the issue came from, because in NetworkManager there was correctly selected WPA3-Personal.

However, because most of my IoT devices don't suporrt WPA3 (and some probably never will), disabling the WPA3 was not a problem for me.

Thanks!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.