You are not logged in.

Pages: 1 2 3 4

#1 2024-02-09 11:04:49

Jujumba
Member
Registered: 2024-02-09
Posts: 47

iwd сonnects endlessly to the network

Hello.

Issue sprung up recently, after setting mode of my wireless card to monitor, iwd was unable to connect to the network because dhcpcd was lacking. After resetting mode to managed and installing dhcpcd it worked, though for a short period. Now it's stuck and iwd can't connect to the network, "iwd station wlan0 show" says that it connects to the network...

Usually, disabling conflicting network services helps: in my case disabling NetworkManager, dhcpcd, dhcp and systemd-networkd didn't help.

What's even more interesting is that NetworkManager (which I currently use, that is I've disable iwd for now) actually able to connect to network, though some websites such as duckduckgo.com are unreachable (I suspect it's related to dns, see my /etc/resolve.conf below).


sudo dmesg output:

[    6.803741] ACPI Error: No handler for Region [ECSI] (00000000120de27a) [EmbeddedControl] (20230628/evregion-130)
[    6.803756] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20230628/exfldio-261)
[    6.803773] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20230628/psparse-529)
[    6.803790] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20230628/psparse-529)
[    6.803813] ACPI: \_SB_.UBTC: failed to evaluate _DSM c298836f-a47c-e411-ad36-631042b5008f (0x6)
[    6.803821] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2
[    6.828865] videodev: Linux video capture interface: v2.00
[    6.847976] input: MSFT0001:00 04F3:3140 Mouse as /devices/platform/AMDI0010:01/i2c-1/i2c-MSFT0001:00/0018:04F3:3140.0001/input/input9
[    6.848238] input: MSFT0001:00 04F3:3140 Touchpad as /devices/platform/AMDI0010:01/i2c-1/i2c-MSFT0001:00/0018:04F3:3140.0001/input/input10
[    6.848530] hid-multitouch 0018:04F3:3140.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 04F3:3140] on i2c-MSFT0001:00
[    6.885165] mousedev: PS/2 mouse device common for all mice
[    6.910775] usb 1-3: Found UVC 1.10 device Integrated Camera (04f2:b725)
[    6.915805] EXT4-fs (nvme0n1p6): mounted filesystem 3672fec8-84a9-4005-9295-6a18a4d8d10b r/w with ordered data mode. Quota mode: none.
[    6.917369] usbcore: registered new interface driver uvcvideo
[    6.918373] ath10k_pci 0000:01:00.0: enabling device (0000 -> 0002)
[    6.921110] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[    6.922812] snd_hda_intel 0000:03:00.1: enabling device (0000 -> 0002)
[    6.922979] snd_hda_intel 0000:03:00.1: Handle vga_switcheroo audio client
[    6.923202] snd_hda_intel 0000:03:00.6: enabling device (0000 -> 0002)
[    6.944738] snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[    6.946688] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:03:00.1/sound/card0/input11
[    6.946766] input: HD-Audio Generic HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:08.1/0000:03:00.1/sound/card0/input12
[    7.009772] usbcore: registered new interface driver btusb
[    7.021464] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[    7.032029] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC257: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[    7.032038] snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    7.032040] snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[    7.032042] snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
[    7.032044] snd_hda_codec_realtek hdaudioC1D0:    inputs:
[    7.032046] snd_hda_codec_realtek hdaudioC1D0:      Mic=0x19
[    7.032047] snd_hda_codec_realtek hdaudioC1D0:      Internal Mic=0x12
[    7.036932] kvm_amd: TSC scaling supported
[    7.036939] kvm_amd: Nested Virtualization enabled
[    7.036941] kvm_amd: Nested Paging enabled
[    7.036951] kvm_amd: Virtual VMLOAD VMSAVE supported
[    7.036952] kvm_amd: Virtual GIF supported
[    7.036953] kvm_amd: LBR virtualization supported
[    7.058719] MCE: In-kernel MCE decoding enabled.
[    7.159410] intel_rapl_common: Found RAPL domain package
[    7.159417] intel_rapl_common: Found RAPL domain core
[    7.186318] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 17aa:0827
[    7.186327] ath10k_pci 0000:01:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0
[    7.186637] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4.1-00309- api 6 features wowlan,ignore-otp,mfp crc32 0793bcf2
[    7.251706] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 d2863f91
[    7.290647] input: HD-Audio Generic Mic as /devices/pci0000:00/0000:00:08.1/0000:03:00.6/sound/card1/input13
[    7.290730] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:08.1/0000:03:00.6/sound/card1/input14
[    7.345187] ath10k_pci 0000:01:00.0: htt-ver 3.87 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[    7.420751] ath: EEPROM regdomain: 0x6c
[    7.420759] ath: EEPROM indicates we should expect a direct regpair map
[    7.420763] ath: Country alpha2 being used: 00
[    7.420765] ath: Regpair used: 0x6c
[    7.518368] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    7.518375] Bluetooth: BNEP filters: protocol multicast
[    7.518384] Bluetooth: BNEP socket layer initialized
[    7.519877] Bluetooth: MGMT ver 1.22
[    7.525589] NET: Registered PF_ALG protocol family
[    7.934114] ucsi_acpi: probe of USBC000:00 failed with error -5
[  141.171401] systemd-journald[341]: /var1/log/journal/a83629bcb55247e084752047b4fec961/user-1000.journal: Journal file uses a different sequence number ID, rotating.
[  169.548812] wlan0: authenticate with c9:9e:43:10:51:41 (local address=e0:0a:f6:3f:3d:21)
[  169.548825] wlan0: send auth to c9:9e:43:10:51:41 (try 1/3)
[  169.560596] wlan0: authenticated
[  169.567052] wlan0: associate with c9:9e:43:10:51:41 (try 1/3)
[  169.588968] wlan0: RX AssocResp from c9:9e:43:10:51:41 (capab=0x511 status=0 aid=11)
[  169.591855] wlan0: associated
[  169.667792] wlan0: Limiting TX power to 20 (23 - 3) dBm as advertised by c8:9e:43:10:51:41

/etc/resolve.conf (Note: When I was using iwd, /etc/resolve.conf was empty (!) )

# Generated by NetworkManager
nameserver fd00::de15:c8ff:fee4:8cb9
nameserver 2a01:3d8:411:1500:de15:c8ff:fee4:8cb9
$ 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-resolved.service  loaded active running Network Name Resolution
  systemd-timedated.service loaded active running Time & Date Service
  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.

14 loaded units listed.
$ sudo iwconfig wlan0                      
wlan0     IEEE 802.11  ESSID:"REDACTED"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: C9:9E:43:10:51:21   
          Bit Rate=117 Mb/s   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=58/70  Signal level=-52 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:73   Missed beacon:0

And most importantly, when I'm trying to connect using iwd:

$ journalctl  -x -b -p err..alert
Feb 09 12:37:59 arch kernel: amdgpu 0000:03:00.0: amdgpu: Secure display: Generic Failure.
Feb 09 12:37:59 arch kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Feb 09 12:38:00 arch kernel: ACPI Error: No handler for Region [ECSI] (00000000a8134d3d) [EmbeddedControl] (20230628/evregion-130)
Feb 09 12:38:00 arch kernel: ACPI Error: Region EmbeddedControl (ID=3) has no handler (20230628/exfldio-261)
Feb 09 12:38:00 arch kernel: ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20230628/psparse-529)
Feb 09 12:38:00 arch kernel: ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20230628/psparse-529)
Feb 09 12:38:00 arch kernel: ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2
Feb 09 12:38:33 arch kernel: ath10k_pci 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0008 address=0xff0721d0 flags=0x0070]
Feb 09 12:38:56 arch bluetoothd[518]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
Feb 09 12:39:28 arch kernel: ath10k_pci 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0008 address=0xfefd9850 flags=0x0070]
Feb 09 12:39:36 arch kernel: ath10k_pci 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0008 address=0xfe049950 flags=0x0070]
Feb 09 12:40:27 arch kernel: ath10k_pci 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0008 address=0xfec18250 flags=0x0070]
Feb 09 12:52:23 arch kernel: ath10k_pci 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0008 address=0xff23f4d0 flags=0x0070]

Last edited by Jujumba (2024-02-09 11:58:08)

Offline

#2 2024-02-09 14:39:27

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,034

Re: iwd сonnects endlessly to the network

Usually, disabling conflicting network services helps: in my case disabling NetworkManager, dhcpcd, dhcp and systemd-networkd didn't help.

$ systemctl --type=service --state=running
  UNIT                      LOAD   ACTIVE SUB     DESCRIPTION                                   
…
  NetworkManager.service    loaded active running Network Manager
…
  wpa_supplicant.service    loaded active running WPA supplicant

There's a running wpa_supplicant, likely invoked by NM.
If you wan to use iwd along NM, see https://wiki.archlinux.org/title/Networ … Fi_backend - do NOT enable the service.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2024-02-09 16:32:57

Jujumba
Member
Registered: 2024-02-09
Posts: 47

Re: iwd сonnects endlessly to the network

seth wrote:

Usually, disabling conflicting network services helps: in my case disabling NetworkManager, dhcpcd, dhcp and systemd-networkd didn't help.

$ systemctl --type=service --state=running
  UNIT                      LOAD   ACTIVE SUB     DESCRIPTION                                   
…
  NetworkManager.service    loaded active running Network Manager
…
  wpa_supplicant.service    loaded active running WPA supplicant

There's a running wpa_supplicant, likely invoked by NM.
If you wan to use iwd along NM, see https://wiki.archlinux.org/title/Networ … Fi_backend - do NOT enable the service.

Thanks for you suggestion.

I've chosen iwd as a backend and rebooted my system, but issue still persists sad

iwd still tries to connect to my network

iwd]# station wlan0 show
                                 Station: wlan0                                
--------------------------------------------------------------------------------
  Settable  Property              Value                                          
--------------------------------------------------------------------------------
            Scanning              no                                               
            State                 connecting                                       
            Connected network     redacted                                       
            IPv6 address        2a11:3d8:411:1500:e20a:f6ff:fe3f:3d21

But I've managed to connect using nmcli as in a previous time, though nothing has changed. Preventing iwd to connect leaves me with to internet at all sad

Some outputs:

$ sudo cat /etc/NetworkManager/conf.d/wifi_backend.conf 
 [device]
wifi.backend=iwd
$ 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
  iwd.service              loaded active running Wireless 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-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
  upower.service           loaded active running Daemon for power management
  user@1000.service        loaded active running User Manager for UID 1000
$ 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
iwd.service
dbus-org.freedesktop.nm-dispatcher.service
getty@tty1.service
bluetooth.service
NetworkManager-wait-online.service

Last edited by Jujumba (2024-02-09 16:46:11)

Offline

#4 2024-02-09 16:48:56

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,231

Re: iwd сonnects endlessly to the network

Disable iwd.service it will and should be brought up by NetworkManager

Offline

#5 2024-02-09 17:07:18

Jujumba
Member
Registered: 2024-02-09
Posts: 47

Re: iwd сonnects endlessly to the network

V1del wrote:

Disable iwd.service it will and should be brought up by NetworkManager

Unfortunately it didn't help sad

After stopping and disabling iwd and rebooting my system then, everything remained as was (iwd still appears in "systemctl --type=service --state=running"'s output).

I still can reach some sites, but half of the Internet is inaccessible to me:(

Offline

#6 2024-02-09 17:12:06

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,727

Re: iwd сonnects endlessly to the network

That often happens when you have an autoconfigured IPv6 address via SLAAC, but no IPv4. What does `ip a` show?

Offline

#7 2024-02-09 17:14:49

Jujumba
Member
Registered: 2024-02-09
Posts: 47

Re: iwd сonnects endlessly to the network

Scimmia wrote:

That often happens when you have an autoconfigured IPv6 address via SLAAC, but no IPv4. What does `ip a` show?

Thanks for your interest.

Here it is:

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e0:0a:f6:3f:3d:21 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::e20a:f6ff:fe3f:3d21/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever

Offline

#8 2024-02-09 17:58:01

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,034

Re: iwd сonnects endlessly to the network

Please post your complete system journal for a boot after failing to get a lease:

sudo journalctl -b

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2024-02-09 18:23:37

Jujumba
Member
Registered: 2024-02-09
Posts: 47

Re: iwd сonnects endlessly to the network

seth wrote:

Please post your complete system journal for a boot after failing to get a lease:

sudo journalctl -b

I've uploaded it to pastebin

https://pastebin.com/ZJ6YEjRU

Last edited by Jujumba (2024-02-09 18:32:44)

Offline

#10 2024-02-09 18:31:40

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,727

Re: iwd сonnects endlessly to the network

So you have NM set to use dhcpcd and you have iwd set up to configure the network? Is that correct?

You probably don't want either of those things

Offline

#11 2024-02-09 18:47:39

Jujumba
Member
Registered: 2024-02-09
Posts: 47

Re: iwd сonnects endlessly to the network

Scimmia wrote:

So you have NM set to use dhcpcd and you have iwd set up to configure the network? Is that correct?

You probably don't want either of those things

Thanks. I've even forgotten that I set NM to use dhcpcd at some point.

Removed it from etc/NetworkManager/conf.d/dhcp-client.conf, but issue still persists sad

Offline

#12 2024-02-09 20:11:53

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,034

Re: iwd сonnects endlessly to the network

Feb 09 19:20:38 arch iwd[554]: [DHCPv4] l_dhcp_client_start:1204 Entering state: DHCP_STATE_SELECTING

You then probably still have https://wiki.archlinux.org/title/Iwd#Ne … figuration ?

Scimmia wrote:

You probably don't want either of those things

And you most certainly to not want https://wiki.archlinux.org/title/Iwd#Ne … figuration if you're using NM.

After fixing that, please post an updated journal in case the problem still exists.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2024-02-09 20:30:52

Jujumba
Member
Registered: 2024-02-09
Posts: 47

Re: iwd сonnects endlessly to the network

seth wrote:

Feb 09 19:20:38 arch iwd[554]: [DHCPv4] l_dhcp_client_start:1204 Entering state: DHCP_STATE_SELECTING

You then probably still have https://wiki.archlinux.org/title/Iwd#Ne … figuration ?

Scimmia wrote:

You probably don't want either of those things

And you most certainly to not want https://wiki.archlinux.org/title/Iwd#Ne … figuration if you're using NM.

After fixing that, please post an updated journal in case the problem still exists.

I've deleted configuration file associated with my network (if , after that connection completely disappeared so I tried to reconnect:

$ nmcli device wifi connect network password passphrase
Error: Connection activation failed: Secrets were required, but not provided.

Forgetting network and reconnecting worked out. However, nothing has changed sad

Here link to updated journal: https://pastebin.com/SZAKN5xa

Thanks a lot in advance

Last edited by Jujumba (2024-02-09 20:34:38)

Offline

#14 2024-02-09 20:33:36

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,034

Re: iwd сonnects endlessly to the network

Sorry, wrong link.
This here: https://wiki.archlinux.org/title/Iwd#En … figuration
Disable that

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#15 2024-02-09 20:39:03

Jujumba
Member
Registered: 2024-02-09
Posts: 47

Re: iwd сonnects endlessly to the network

seth wrote:

Sorry, wrong link.
This here: https://wiki.archlinux.org/title/Iwd#En … figuration
Disable that

Thank you, I've set it to false and iwd managed to connect to the network, though issue persists.

Perhaps I should disable NM and use iwd as before, because now iwd acts normally

Offline

#16 2024-02-09 20:42:15

Jujumba
Member
Registered: 2024-02-09
Posts: 47

Re: iwd сonnects endlessly to the network

Jujumba wrote:
seth wrote:

Sorry, wrong link.
This here: https://wiki.archlinux.org/title/Iwd#En … figuration
Disable that

Thank you, I've set it to false and iwd managed to connect to the network, though issue persists.

Perhaps I should disable NM and use iwd as before, because now iwd acts normally

Just checked, on its own iwd can't provide a connection to the network at all, NM has to be running

Offline

#17 2024-02-09 20:42:58

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,034

Re: iwd сonnects endlessly to the network

though issue persists

Please post an updated journal.

Perhaps I should disable NM and use iwd as before, because now iwd acts normally

You can use whatever suits you to configure the network, but what does the above mean?
W/o that setting, iwd will get you a carrier, but no lease - you'll still need some dhcp client for that.
dhcpcd, NM or dhcpcd through NM doesn't matter beyond personal preferences, though.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#18 2024-02-09 20:56:03

Jujumba
Member
Registered: 2024-02-09
Posts: 47

Re: iwd сonnects endlessly to the network

seth wrote:

though issue persists

Please post an updated journal.

Perhaps I should disable NM and use iwd as before, because now iwd acts normally

You can use whatever suits you to configure the network, but what does the above mean?
W/o that setting, iwd will get you a carrier, but no lease - you'll still need some dhcp client for that.
dhcpcd, NM or dhcpcd through NM doesn't matter beyond personal preferences, though.

I mean to switch to dhcpcd + iwd as it was before since now iwd can connect to the network, but as it turned out this combination doesn't work completely sad

Sorry for journal, here it is: https://pastebin.com/cqTXFgKr

Offline

#19 2024-02-09 21:06:45

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,034

Re: iwd сonnects endlessly to the network

Feb 09 21:50:50 arch NetworkManager[519]: <info>  [1707511850.4698] manager: NetworkManager state is now CONNECTING
Feb 09 21:50:50 arch NetworkManager[519]: <info>  [1707511850.4699] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 09 21:50:51 arch NetworkManager[519]: <info>  [1707511851.9083] device (wlan0): new IWD device state is connected
Feb 09 21:50:51 arch NetworkManager[519]: <info>  [1707511851.9086] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Feb 09 21:50:51 arch NetworkManager[519]: <info>  [1707511851.9100] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 21:50:53 arch NetworkManager[519]: <info>  [1707511853.3134] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 21:50:53 arch NetworkManager[519]: <info>  [1707511853.3143] policy: set 'inhabitant' (wlan0) as default for IPv6 routing and DNS
Feb 09 21:50:53 arch NetworkManager[519]: <info>  [1707511853.5213] dhcp6 (wlan0): state changed new lease
Feb 09 21:50:54 arch NetworkManager[519]: <info>  [1707511854.7973] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Feb 09 21:50:54 arch NetworkManager[519]: <info>  [1707511854.7997] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Feb 09 21:50:54 arch NetworkManager[519]: <info>  [1707511854.7999] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Feb 09 21:50:54 arch NetworkManager[519]: <info>  [1707511854.8001] manager: NetworkManager state is now CONNECTED_SITE
Feb 09 21:50:54 arch NetworkManager[519]: <info>  [1707511854.8003] device (wlan0): Activation: successful, device activated.
Feb 09 21:50:59 arch systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Feb 09 21:50:59 arch NetworkManager[519]: <info>  [1707511859.9110] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.5017] audit: op="connection-update" uuid="2f87b444-b921-46c0-9a38-15f0693d057d" name="inhabitant" args="connection.timestamp" pid=1105 uid=1000 result="success"
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.5047] device (wlan0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.5048] manager: NetworkManager state is now DISCONNECTING
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.5053] device (wlan0): disconnecting for new activation request.
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.5053] audit: op="connection-activate" uuid="2f87b444-b921-46c0-9a38-15f0693d057d" name="inhabitant" pid=1105 uid=1000 result="success"
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6372] device (wlan0): new IWD device state is disconnecting
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6375] device (wlan0): new IWD device state is disconnected
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6376] device (wlan0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6382] dhcp4 (wlan0): canceled DHCP transaction
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6382] dhcp4 (wlan0): state changed no lease
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6384] dhcp6 (wlan0): canceled DHCP transaction
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6384] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6385] dhcp6 (wlan0): state changed no lease
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6675] manager: NetworkManager state is now DISCONNECTED

21:50:51 you're connected and start a dhcp request on IPv4/6
21:50:53 you get IPv6 routing
21:50:54 NetworkManager considers you CONNECTED_SITE
21:50:59 NetworkManager considers you CONNECTED_GLOBAL (ie. could ping the test domain)
21:51:04 You disconnect

=> try to disable IPv6, https://wiki.archlinux.org/title/IPv6#Disable_IPv6
And then please scan for a dhcpcd server, "sudo nmap --script broadcast-dhcp-discover" (you need a carrier but no lease for that)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#20 2024-02-09 21:18:39

Jujumba
Member
Registered: 2024-02-09
Posts: 47

Re: iwd сonnects endlessly to the network

seth wrote:
Feb 09 21:50:50 arch NetworkManager[519]: <info>  [1707511850.4698] manager: NetworkManager state is now CONNECTING
Feb 09 21:50:50 arch NetworkManager[519]: <info>  [1707511850.4699] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 09 21:50:51 arch NetworkManager[519]: <info>  [1707511851.9083] device (wlan0): new IWD device state is connected
Feb 09 21:50:51 arch NetworkManager[519]: <info>  [1707511851.9086] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Feb 09 21:50:51 arch NetworkManager[519]: <info>  [1707511851.9100] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 21:50:53 arch NetworkManager[519]: <info>  [1707511853.3134] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 21:50:53 arch NetworkManager[519]: <info>  [1707511853.3143] policy: set 'inhabitant' (wlan0) as default for IPv6 routing and DNS
Feb 09 21:50:53 arch NetworkManager[519]: <info>  [1707511853.5213] dhcp6 (wlan0): state changed new lease
Feb 09 21:50:54 arch NetworkManager[519]: <info>  [1707511854.7973] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Feb 09 21:50:54 arch NetworkManager[519]: <info>  [1707511854.7997] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Feb 09 21:50:54 arch NetworkManager[519]: <info>  [1707511854.7999] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Feb 09 21:50:54 arch NetworkManager[519]: <info>  [1707511854.8001] manager: NetworkManager state is now CONNECTED_SITE
Feb 09 21:50:54 arch NetworkManager[519]: <info>  [1707511854.8003] device (wlan0): Activation: successful, device activated.
Feb 09 21:50:59 arch systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Feb 09 21:50:59 arch NetworkManager[519]: <info>  [1707511859.9110] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.5017] audit: op="connection-update" uuid="2f87b444-b921-46c0-9a38-15f0693d057d" name="inhabitant" args="connection.timestamp" pid=1105 uid=1000 result="success"
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.5047] device (wlan0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.5048] manager: NetworkManager state is now DISCONNECTING
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.5053] device (wlan0): disconnecting for new activation request.
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.5053] audit: op="connection-activate" uuid="2f87b444-b921-46c0-9a38-15f0693d057d" name="inhabitant" pid=1105 uid=1000 result="success"
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6372] device (wlan0): new IWD device state is disconnecting
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6375] device (wlan0): new IWD device state is disconnected
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6376] device (wlan0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6382] dhcp4 (wlan0): canceled DHCP transaction
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6382] dhcp4 (wlan0): state changed no lease
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6384] dhcp6 (wlan0): canceled DHCP transaction
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6384] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6385] dhcp6 (wlan0): state changed no lease
Feb 09 21:51:04 arch NetworkManager[519]: <info>  [1707511864.6675] manager: NetworkManager state is now DISCONNECTED

21:50:51 you're connected and start a dhcp request on IPv4/6
21:50:53 you get IPv6 routing
21:50:54 NetworkManager considers you CONNECTED_SITE
21:50:59 NetworkManager considers you CONNECTED_GLOBAL (ie. could ping the test domain)
21:51:04 You disconnect

=> try to disable IPv6, https://wiki.archlinux.org/title/IPv6#Disable_IPv6
And then please scan for a dhcpcd server, "sudo nmap --script broadcast-dhcp-discover" (you need a carrier but no lease for that)

Disabled ipv6 on all interfaces (?) and restarted systemd-sysctl.service, but nothing sad

Journal: https://pastebin.com/9vy7Urib


Sorry, I've forgotten to add nmap's output:

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

Last edited by Jujumba (2024-02-09 21:22:16)

Offline

#21 2024-02-09 21:22:29

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,034

Re: iwd сonnects endlessly to the network

Feb 09 22:13:04 arch NetworkManager[518]: <info>  [1707513184.5680] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf) (etc: dhcp-client.conf, wifi-backend.conf, wifi-powersave.conf, wifi_backend.conf)
Feb 09 22:13:04 arch NetworkManager[518]: <info>  [1707513184.6486] dhcp: init: Using DHCP client 'internal'
Feb 09 22:13:07 arch NetworkManager[518]: <info>  [1707513187.2290] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 22:13:16 arch NetworkManager[518]: <info>  [1707513196.7390] dhcp4 (wlan0): canceled DHCP transaction
Feb 09 22:13:16 arch NetworkManager[518]: <info>  [1707513196.7391] dhcp4 (wlan0): state changed no lease
Feb 09 22:13:18 arch NetworkManager[518]: <info>  [1707513198.2431] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 22:14:03 arch NetworkManager[518]: <info>  [1707513243.1058] dhcp4 (wlan0): canceled DHCP transaction
Feb 09 22:14:03 arch NetworkManager[518]: <info>  [1707513243.1058] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 22:14:03 arch NetworkManager[518]: <info>  [1707513243.1059] dhcp4 (wlan0): state changed no lease
Feb 09 22:14:10 arch NetworkManager[518]: <info>  [1707513250.7139] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 22:14:12 arch NetworkManager[518]: <info>  [1707513252.0913] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Feb 09 22:14:12 arch NetworkManager[518]: <info>  [1707513252.3001] dhcp6 (wlan0): state changed new lease
ip a
the wiki wrote:

Disable functionality
Adding ipv6.disable=1 to the kernel line disables the whole IPv6 stack, which is likely what you want if you are experiencing issues.

You'll have to reboot for that.
Did nmap find any dhcp servers?

Edit: "no" - there's no dhcp server in the segment. Do you expect there to be one?
On a formal note, please don't full-quote w/o reason. You're bloating the thread.

Last edited by seth (2024-02-09 21:24:15)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#22 2024-02-09 21:32:16

Jujumba
Member
Registered: 2024-02-09
Posts: 47

Re: iwd сonnects endlessly to the network

seth wrote:

You'll have to reboot for that.

Yes, I've rebooted after that


seth wrote:

Did nmap find any dhcp servers?
Edit: "no" - there's no dhcp server in the segment. Do you expect there to be one?
On a formal note, please don't full-quote w/o reason. You're bloating the thread.

I think yes, if NM's dhcp server counts up then one certainly should be there

seth wrote:

On a formal note, please don't full-quote w/o reason. You're bloating the thread.

Sorry

Once again, thanks a lot in advance

Edit: journal if it will help: https://pastebin.com/mWcCY186

Last edited by Jujumba (2024-02-09 21:35:54)

Offline

#23 2024-02-09 21:38:24

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,034

Re: iwd сonnects endlessly to the network

The dhcp *server* is something that provides you with an IP, it's typically part of a consumer router/switch/modem combo.

Feb 09 22:27:59 arch kernel: Segment Routing with IPv6
Feb 09 22:27:59 arch kernel: RPL Segment Routing with IPv6
Feb 09 22:27:59 arch kernel: In-situ OAM (IOAM) with IPv6
Feb 09 22:28:00 arch systemd-sysctl[361]: Couldn't write '1' to 'ipv6/disable', ignoring: No such file or directory
Feb 09 22:28:33 arch NetworkManager[517]: <info>  [1707514113.7547] policy: set 'inhabitant' (wlan0) as default for IPv6 routing and DNS
Feb 09 22:29:06 arch NetworkManager[517]: <info>  [1707514146.4106] policy: set 'inhabitant' (wlan0) as default for IPv6 routing and DNS

And will you please follow the wiki, disable the IPv6 stack and reboot?
You've not disabled it at all.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#24 2024-02-09 22:06:10

Jujumba
Member
Registered: 2024-02-09
Posts: 47

Re: iwd сonnects endlessly to the network

seth wrote:
Feb 09 22:27:59 arch kernel: Segment Routing with IPv6
Feb 09 22:27:59 arch kernel: RPL Segment Routing with IPv6
Feb 09 22:27:59 arch kernel: In-situ OAM (IOAM) with IPv6
Feb 09 22:28:00 arch systemd-sysctl[361]: Couldn't write '1' to 'ipv6/disable', ignoring: No such file or directory
Feb 09 22:28:33 arch NetworkManager[517]: <info>  [1707514113.7547] policy: set 'inhabitant' (wlan0) as default for IPv6 routing and DNS
Feb 09 22:29:06 arch NetworkManager[517]: <info>  [1707514146.4106] policy: set 'inhabitant' (wlan0) as default for IPv6 routing and DNS

And will you please follow the wiki, disable the IPv6 stack and reboot?
You've not disabled it at all.

Sorry, I didn't pay enough attention. I've changed my GRUB_CMDLINE_LINUX_DEFAULT variable in /etc/default/grub as wiki suggests, now it looks like this:

GRUB_CMDLINE_LINUX_DEFAUL="loglevel=3 quiet ipv6.disable_ipv6=1"
# Other code is omitted, trust me, this variable is not reassigned later...

After reboot nothing changed.

Journal: https://pastebin.com/iEZWqL4y

Last edited by Jujumba (2024-02-09 22:06:50)

Offline

#25 2024-02-09 22:11:23

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,034

Re: iwd сonnects endlessly to the network

After reboot nothing changed.

Because

Feb 09 23:00:57 arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=2b0108ed-3d86-42a4-bb67-394625563fb8 rw loglevel=3 quiet

You didn't run grub-mkconfig, you can also transiently edit the commandline at the grub menu, no need to permanently alter the system configuration.

seth wrote:

there's no dhcp server in the segment. Do you expect there to be one?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1 2 3 4

Board footer

Powered by FluxBB