iwd сonnects endlessly to the network

Jujumba · 2024-02-10 10:40:15

What's interesting to me is that I'm unable to connect to network by its bssid.

Windows claims that network's bssid is b4:69:21:3d:8c:a4, but nmcli is unable to connect ;(

$ nmcli device wifi connect b4:69:21:3d:8c:a4
Error: No access point with BSSID 'b4:69:21:3d:8c:a4' found.

Ouput of netsh wlan show interfaces : https://pastebin.com/QqPNtAQT

seth · 2024-02-10 10:44:48

Ask them whether they've changed anything about their network setup or configuration, added a MAC filter (that bounces you) and to reboot the router (or range extender) in doubt.
The bssid there is c8:9e:43:10:51:41 - the one you're trying to use from linux.
b4:69:21:3d:8c:a4 is an intel MAC, your notebook.

Jujumba · 2024-02-10 10:52:25

seth wrote:

Ask them whether they've changed anything about their network setup or configuration, added a MAC filter (that bounces you) and to reboot the router (or range extender) in doubt.

Thanks, I'll ask them to reboot

seth wrote:

The bssid there is c8:9e:43:10:51:41 - the one you're trying to use from linux.
b4:69:21:3d:8c:a4 is an intel MAC, your notebook.

So, I should not try to connect to network with that bssid (b4:69:21:3d:8c:a4) from linux?

Last edited by Jujumba (2024-02-10 10:55:35)

Jujumba · 2024-02-10 13:27:18

Jujumba wrote:

So, I should not try to connect to network with that bssid (b4:69:21:3d:8c:a4) from linux?

Sorry, I have to pay more attention. bssids seem to match, Windows machine connected to c8:9e:43:10:51:41, which I'm trying to connect from linux...

Jujumba · 2024-02-10 13:58:47

Just checked, I can connect to the Internet properly when connection to phone's hotspot

seth · 2024-02-10 14:57:56

Yes.
The problem is that the dhcp server in the fritzbox LAN doesn't respond.
With that netgear MAC, I suspect a range extender/repeater to be inbetween and that probably drops the ball (since you can connect to that AP fine, it just doesn't get you ahead)

Talk to your neighbours.

Jujumba · 2024-02-10 15:28:42

seth wrote:

Yes.
The problem is that the dhcp server in the fritzbox LAN doesn't respond.
With that netgear MAC, I suspect a range extender/repeater to be inbetween and that probably drops the ball (since you can connect to that AP fine, it just doesn't get you ahead)
Talk to your neighbours.

Reboot of router didn't help, and there is no range extender

seth · 2024-02-10 15:31:32

Did they say whether they changed anything else about the AP? Any idea why it has a netgear MAC?
Configure NM to use wpa_supplicant, reboot, try to connect, post the journal.

Jujumba · 2024-02-10 16:08:44

seth wrote:

Did they say whether they changed anything else about the AP?

No changes, they are not technical users so I hadn't expected any changes in network at all

seth wrote:

Any idea why it has a netgear MAC?

None

seth wrote:

Configure NM to use wpa_supplicant

You mean disabling awd back-end?

seth · 2024-02-10 16:11:01

"iwd", but yes.

Jujumba · 2024-02-10 16:17:53

After rebooting and and disabling iwd backend:

$ systemctl --type=service --state=running              
  UNIT                              LOAD   ACTIVE SUB     DESCRIPTION                                   
  bluetooth.service                 loaded active running Bluetooth service
  dbus-broker.service               loaded active running D-Bus System Message Bus
  getty@tty1.service                loaded active running Getty on tty1
  NetworkManager-dispatcher.service loaded active running Network Manager Script Dispatcher Service
  NetworkManager.service            loaded active running Network Manager
  polkit.service                    loaded active running Authorization Manager
  rtkit-daemon.service              loaded active running RealtimeKit Scheduling Policy Service
  systemd-hostnamed.service         loaded active running Hostname Service
  systemd-journald.service          loaded active running Journal Service
  systemd-logind.service            loaded active running User Login Management
  systemd-udevd.service             loaded active running Rule-based Manager for Device Events and Files
  systemd-userdbd.service           loaded active running User Database Manager
  user@1000.service                 loaded active running User Manager for UID 1000
  wpa_supplicant.service            loaded active running WPA supplicant

Journal: https://pastebin.com/kzrZ21Eg

seth · 2024-02-10 16:39:26

Feb 10 17:15:08 arch wpa_supplicant[560]: wlan0: SME: Trying to authenticate with c8:9e:43:10:51:41 (SSID='inhabitant' freq=5180 MHz)
Feb 10 17:15:08 arch kernel: wlan0: authenticate with c8:9e:43:10:51:41 (local address=e0:0a:f6:3f:3d:21)
Feb 10 17:15:08 arch kernel: wlan0: send auth to c8:9e:43:10:51:41 (try 1/3)
Feb 10 17:15:08 arch wpa_supplicant[560]: wlan0: Trying to associate with c8:9e:43:10:51:41 (SSID='inhabitant' freq=5180 MHz)
Feb 10 17:15:08 arch kernel: wlan0: associate with c8:9e:43:10:51:41 (try 1/3)
Feb 10 17:15:08 arch kernel: wlan0: RX AssocResp from c8:9e:43:10:51:41 (capab=0x511 status=30 aid=0)
Feb 10 17:15:08 arch kernel: wlan0: c8:9e:43:10:51:41 rejected association temporarily; comeback duration 1000 TU (1024 ms)
Feb 10 17:15:10 arch kernel: wlan0: associate with c8:9e:43:10:51:41 (try 2/3)
Feb 10 17:15:10 arch kernel: wlan0: associate with c8:9e:43:10:51:41 (try 3/3)
Feb 10 17:15:10 arch kernel: wlan0: association with c8:9e:43:10:51:41 timed out
Feb 10 17:15:10 arch wpa_supplicant[560]: BSSID c8:9e:43:10:51:41 ignore list count incremented to 2, ignoring for 10 seconds
Feb 10 17:15:10 arch wpa_supplicant[560]: wlan0: SME: Trying to authenticate with c8:9e:43:10:51:21 (SSID='inhabitant' freq=2412 MHz)
Feb 10 17:15:10 arch kernel: wlan0: authenticate with c8:9e:43:10:51:21 (local address=e0:0a:f6:3f:3d:21)
Feb 10 17:15:10 arch kernel: wlan0: send auth to c8:9e:43:10:51:21 (try 1/3)
Feb 10 17:15:10 arch wpa_supplicant[560]: wlan0: Trying to associate with c8:9e:43:10:51:21 (SSID='inhabitant' freq=2412 MHz)
Feb 10 17:15:10 arch kernel: wlan0: associate with c8:9e:43:10:51:21 (try 1/3)
Feb 10 17:15:10 arch kernel: wlan0: RX AssocResp from c8:9e:43:10:51:21 (capab=0x431 status=0 aid=5)
Feb 10 17:15:10 arch wpa_supplicant[560]: wlan0: Associated with c8:9e:43:10:51:21
Feb 10 17:15:10 arch wpa_supplicant[560]: wlan0: WPA: Key negotiation completed with c8:9e:43:10:51:21 [PTK=CCMP GTK=CCMP]
Feb 10 17:15:10 arch wpa_supplicant[560]: wlan0: CTRL-EVENT-CONNECTED - Connection to c8:9e:43:10:51:21 completed [id=0 id_str=]
Feb 10 17:15:38 arch kernel: wlan0: deauthenticating from c8:9e:43:10:51:21 by local choice (Reason: 3=DEAUTH_LEAVING)
Feb 10 17:15:38 arch wpa_supplicant[560]: wlan0: CTRL-EVENT-DISCONNECTED bssid=c8:9e:43:10:51:21 reason=3 locally_generated=1
Feb 10 17:15:38 arch wpa_supplicant[560]: wlan0: SME: Trying to authenticate with c8:9e:43:10:51:41 (SSID='inhabitant' freq=5180 MHz)
Feb 10 17:15:38 arch kernel: wlan0: authenticate with c8:9e:43:10:51:41 (local address=e0:0a:f6:3f:3d:21)
Feb 10 17:15:38 arch kernel: wlan0: send auth to c8:9e:43:10:51:41 (try 1/3)
Feb 10 17:15:39 arch kernel: wlan0: send auth to c8:9e:43:10:51:41 (try 2/3)
Feb 10 17:15:40 arch kernel: wlan0: send auth to c8:9e:43:10:51:41 (try 3/3)
Feb 10 17:15:40 arch wpa_supplicant[560]: wlan0: Trying to associate with c8:9e:43:10:51:41 (SSID='inhabitant' freq=5180 MHz)
Feb 10 17:15:40 arch kernel: wlan0: associate with c8:9e:43:10:51:41 (try 1/3)
Feb 10 17:15:40 arch kernel: wlan0: RX AssocResp from c8:9e:43:10:51:41 (capab=0x511 status=0 aid=1)
Feb 10 17:15:40 arch wpa_supplicant[560]: wlan0: Associated with c8:9e:43:10:51:41
Feb 10 17:15:40 arch wpa_supplicant[560]: wlan0: WPA: Key negotiation completed with c8:9e:43:10:51:41 [PTK=CCMP GTK=CCMP]
Feb 10 17:15:40 arch wpa_supplicant[560]: wlan0: CTRL-EVENT-CONNECTED - Connection to c8:9e:43:10:51:41 completed [id=0 id_str=]
Feb 10 17:15:40 arch kernel: wlan0: Limiting TX power to 20 (23 - 3) dBm as advertised by c8:9e:43:10:51:41

You're initially rejected by the c8:9e:43:10:51:41 AP
Then, after timing out, finally associate with c8:9e:43:10:51:21 at 17:15:10, send out a dhcp request but before that gets a reply, NM figures it'd rather try c8:9e:43:10:51:41 again what barely works on the last auth try and you associate with it at 17:15:40, send out a dhcp request and then the journal cuts off at 17:15:48

1. disable IPv6 again (just to clean up the log and not get a connected_global from there all the time)
2. lock the BSSID of the 2.4GHz AP (c8:9e:43:10:51:21), https://wiki.archlinux.org/title/Networ … ets_(WiFi)

Jujumba · 2024-02-10 17:08:30

seth wrote:

2. lock the BSSID of the 2.4GHz AP (c8:9e:43:10:51:21), https://wiki.archlinux.org/title/Networ … ets_(WiFi)

Sorry, what do you mean? Didn't find instruction on that in the link

Edit: Do you request output of journalctl -f ?

Last edited by Jujumba (2024-02-10 17:09:52)

seth · 2024-02-10 17:10:32

Do not connect to "inhabitant" but "c8:9e:43:10:51:21".

Jujumba · 2024-02-10 17:18:49

Booting with "ipv6.disable=1" results in timeout when connecting to the network

$ nmcli device wifi connect C8:9E:43:10:51:21 password passphrase
Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.).

Journal: https://pastebin.com/Pa6XgWAz

Last edited by Jujumba (2024-02-10 17:19:15)

seth · 2024-02-10 17:25:15

NM is running and happily trying to connect to "inhabitant" in that journal - remove or alter the connection profile.

Jujumba · 2024-02-10 17:30:54

seth wrote:

NM is running and happily trying to connect to "inhabitant" in that journal - remove or alter the connection profile.

Removed the connection with

$ nmcli connection inhabitant

And then rebooted with ipv6 disabled, though it's still unable to connect

$ nmcli device wifi connect C8:9E:43:10:51:21 password passphrase
Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.).

Journal: https://pastebin.com/hquZp1bL

Jujumba · 2024-02-10 17:32:35

Just noticed an interesting detail, after reboot with ipv6 enabled I was automatically "connected" to the network. But I had removed my network from the known-list, hadn't I?..

seth · 2024-02-10 20:36:09

I don't know what you had done, but

Feb 10 18:27:04 arch NetworkManager[515]: <info>  [1707586024.0188] Config: added 'ssid' value 'inhabitant'
Feb 10 18:27:04 arch wpa_supplicant[562]: wlan0: SME: Trying to authenticate with c8:9e:43:10:51:41 (SSID='inhabitant' freq=5180 MHz)
Feb 10 18:27:04 arch wpa_supplicant[562]: wlan0: Trying to associate with c8:9e:43:10:51:41 (SSID='inhabitant' freq=5180 MHz)
Feb 10 18:27:05 arch wpa_supplicant[562]: wlan0: SME: Trying to authenticate with c8:9e:43:10:51:21 (SSID='inhabitant' freq=2412 MHz)
Feb 10 18:27:05 arch wpa_supplicant[562]: wlan0: Trying to associate with c8:9e:43:10:51:21 (SSID='inhabitant' freq=2412 MHz)
Feb 10 18:27:05 arch NetworkManager[515]: <info>  [1707586025.8337] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "inhabitant"
Feb 10 18:27:51 arch NetworkManager[515]: <warn>  [1707586071.0773] device (wlan0): Activation: failed for connection 'inhabitant'
Feb 10 18:27:51 arch NetworkManager[515]: <info>  [1707586071.6213] policy: auto-activating connection 'inhabitant' (2f8cc2a9-5b54-4be2-bef3-af89eefcc666)
Feb 10 18:27:51 arch NetworkManager[515]: <info>  [1707586071.6221] device (wlan0): Activation: starting connection 'inhabitant' (2f8cc2a9-5b54-4be2-bef3-af89eefcc666)
Feb 10 18:27:51 arch NetworkManager[515]: <info>  [1707586071.6233] device (wlan0): Activation: (wifi) access point 'inhabitant' has security, but secrets are required.
Feb 10 18:27:51 arch NetworkManager[515]: <info>  [1707586071.6243] device (wlan0): Activation: (wifi) connection 'inhabitant' has security, and secrets exist.  No new secrets needed.
Feb 10 18:27:51 arch NetworkManager[515]: <info>  [1707586071.6244] Config: added 'ssid' value 'inhabitant'

you're most certainly adding a config for the SSID there…

Disable networkmanager, connect to the BSSID (c8:9e:43:10:51:21) manually - either using iwd (NOT! using its network configuration!) or wpa_supplicant.
Then run

sudo nmap --script broadcast-dhcp-discover

again, then

sudo dhcpcd -dB

Post the outputs of both.

Jujumba · 2024-02-10 21:08:33

seth wrote:

you're most certainly adding a config for the SSID there…

But I have connected using BSSID ;(

seth wrote:

either using iwd (NOT! using its network configuration!)

Do you mean not to use iwctl?

seth · 2024-02-10 21:21:39

I mean " don't use https://wiki.archlinux.org/title/Iwd#En … figuration "

Jujumba · 2024-02-10 21:35:43

seth wrote:

I mean " don't use https://wiki.archlinux.org/title/Iwd#En … figuration "

Got it, this option is already turned off

Jujumba · 2024-02-10 21:44:24

Uuuuum...

I don't what just happened, but it works now...

I've stopped (not disabled) NM and wpa_supplicant, then tried to connect via iwd, but before that I had checked status of the network. iwctl said that it's connected but no IP address was assigned (the message was "Is dhcp client configured?") so I decided to reboot instead of trying to connect, and it works now....

I think this effect will be lost after reboot, so here are some important things:

$ systemctl --type=service --state=running
  UNIT                     LOAD   ACTIVE SUB     DESCRIPTION                                   
  bluetooth.service        loaded active running Bluetooth service
  dbus-broker.service      loaded active running D-Bus System Message Bus
  getty@tty1.service       loaded active running Getty on tty1
  NetworkManager.service   loaded active running Network Manager
  polkit.service           loaded active running Authorization Manager
  rtkit-daemon.service     loaded active running RealtimeKit Scheduling Policy Service
  systemd-journald.service loaded active running Journal Service
  systemd-logind.service   loaded active running User Login Management
  systemd-udevd.service    loaded active running Rule-based Manager for Device Events and Files
  systemd-userdbd.service  loaded active running User Database Manager
  user@1000.service        loaded active running User Manager for UID 1000
  wpa_supplicant.service   loaded active running WPA supplicant

Legend: LOAD   → Reflects whether the unit definition was properly loaded.
        ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
        SUB    → The low-level unit activation state, values depend on unit type.

12 loaded units listed.

$ sudo nmap --script broadcast-dhcp-discover
Starting Nmap 7.94 ( https://nmap.org ) at 2024-02-10 22:42 CET
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 10.14 seconds

$ find /etc/systemd -name \*.service -type l -a -xtype f -printf %f\\n
xdg-user-dirs-update.service
pipewire-session-manager.service
wireplumber.service
dbus-org.bluez.service
NetworkManager.service
dbus-org.freedesktop.nm-dispatcher.service
getty@tty1.service
bluetooth.service
NetworkManager-wait-online.service

And journal: https://pastebin.com/LfyebB7y

Now I'm going to reboot and check whether or not it will work again.

Thanks a lot for your time and effort.

Edit: It seems that nmap still can't find dhcp server

Edit2: It works after reboot. THANKS !

But I'm still stumbled because of the reason. I think this issue may remind about itself later

Last edited by Jujumba (2024-02-10 21:49:31)

Jujumba · 2024-02-10 21:52:24

I guess it was coupled with iwd and NM running simultaneously, as I've stopped to use iwd as a backend of NM few steps earlier (now is stopped and disabled).

seth · 2024-02-10 21:53:45

Feb 10 22:39:13 arch wpa_supplicant[574]: wlan0: SME: Trying to authenticate with c8:9e:43:10:51:41 (SSID='inhabitant' freq=5180 MHz)
Feb 10 22:39:13 arch kernel: wlan0: authenticate with c8:9e:43:10:51:41 (local address=e0:0a:f6:3f:3d:21)
Feb 10 22:39:13 arch kernel: wlan0: send auth to c8:9e:43:10:51:41 (try 1/3)
Feb 10 22:39:13 arch wpa_supplicant[574]: wlan0: Trying to associate with c8:9e:43:10:51:41 (SSID='inhabitant' freq=5180 MHz)
Feb 10 22:39:13 arch kernel: wlan0: associate with c8:9e:43:10:51:41 (try 1/3)
Feb 10 22:39:13 arch kernel: wlan0: RX AssocResp from c8:9e:43:10:51:41 (capab=0x511 status=30 aid=0)
Feb 10 22:39:13 arch kernel: wlan0: c8:9e:43:10:51:41 rejected association temporarily; comeback duration 1000 TU (1024 ms)
Feb 10 22:39:14 arch kernel: wlan0: associate with c8:9e:43:10:51:41 (try 2/3)
Feb 10 22:39:14 arch kernel: wlan0: associate with c8:9e:43:10:51:41 (try 3/3)
Feb 10 22:39:14 arch kernel: wlan0: association with c8:9e:43:10:51:41 timed out
Feb 10 22:39:14 arch wpa_supplicant[574]: BSSID c8:9e:43:10:51:41 ignore list count incremented to 2, ignoring for 10 seconds
Feb 10 22:39:15 arch wpa_supplicant[574]: wlan0: SME: Trying to authenticate with c8:9e:43:10:51:21 (SSID='inhabitant' freq=2412 MHz)
Feb 10 22:39:15 arch kernel: wlan0: authenticate with c8:9e:43:10:51:21 (local address=e0:0a:f6:3f:3d:21)
Feb 10 22:39:15 arch kernel: wlan0: send auth to c8:9e:43:10:51:21 (try 1/3)
Feb 10 22:39:15 arch wpa_supplicant[574]: wlan0: Trying to associate with c8:9e:43:10:51:21 (SSID='inhabitant' freq=2412 MHz)
Feb 10 22:39:15 arch kernel: wlan0: associate with c8:9e:43:10:51:21 (try 1/3)
Feb 10 22:39:15 arch kernel: wlan0: RX AssocResp from c8:9e:43:10:51:21 (capab=0x431 status=0 aid=12)
Feb 10 22:39:15 arch wpa_supplicant[574]: wlan0: Associated with c8:9e:43:10:51:21
Feb 10 22:39:15 arch wpa_supplicant[574]: wlan0: WPA: Key negotiation completed with c8:9e:43:10:51:21 [PTK=CCMP GTK=CCMP]
Feb 10 22:39:15 arch wpa_supplicant[574]: wlan0: CTRL-EVENT-CONNECTED - Connection to c8:9e:43:10:51:21 completed [id=0 id_str=]
Feb 10 22:39:15 arch NetworkManager[522]: <info>  [1707601155.5329] dhcp4 (wlan0): state changed new lease, address=192.168.178.53

You're still trying the 5GHz network first, fail get associated on the 2.4GHz network but this time immediately receive a lease via DHCP.

sudo nmap -p67,68 -sU _gateway

Arch Linux

#51 2024-02-10 10:40:15

Re: iwd сonnects endlessly to the network

#52 2024-02-10 10:44:48

Re: iwd сonnects endlessly to the network

#53 2024-02-10 10:52:25

Re: iwd сonnects endlessly to the network

#54 2024-02-10 13:27:18

Re: iwd сonnects endlessly to the network

#55 2024-02-10 13:58:47

Re: iwd сonnects endlessly to the network

#56 2024-02-10 14:57:56

Re: iwd сonnects endlessly to the network

#57 2024-02-10 15:28:42

Re: iwd сonnects endlessly to the network

#58 2024-02-10 15:31:32

Re: iwd сonnects endlessly to the network

#59 2024-02-10 16:08:44

Re: iwd сonnects endlessly to the network

#60 2024-02-10 16:11:01

Re: iwd сonnects endlessly to the network

#61 2024-02-10 16:17:53

Re: iwd сonnects endlessly to the network

#62 2024-02-10 16:39:26

Re: iwd сonnects endlessly to the network

#63 2024-02-10 17:08:30

Re: iwd сonnects endlessly to the network

#64 2024-02-10 17:10:32

Re: iwd сonnects endlessly to the network

#65 2024-02-10 17:18:49

Re: iwd сonnects endlessly to the network

#66 2024-02-10 17:25:15

Re: iwd сonnects endlessly to the network

#67 2024-02-10 17:30:54

Re: iwd сonnects endlessly to the network

#68 2024-02-10 17:32:35

Re: iwd сonnects endlessly to the network

#69 2024-02-10 20:36:09

Re: iwd сonnects endlessly to the network

#70 2024-02-10 21:08:33

Re: iwd сonnects endlessly to the network

#71 2024-02-10 21:21:39

Re: iwd сonnects endlessly to the network

#72 2024-02-10 21:35:43

Re: iwd сonnects endlessly to the network

#73 2024-02-10 21:44:24

Re: iwd сonnects endlessly to the network

#74 2024-02-10 21:52:24

Re: iwd сonnects endlessly to the network

#75 2024-02-10 21:53:45

Re: iwd сonnects endlessly to the network

Board footer