You shouldn't mix networkmanagers. If you intend to use iwd directly disable and stop NetworkManager and use iwd exclusively. If you want to keep using networkmanager actually use networkmanager and disable iwd. Networkmanager has a commandline tool in nmcli/nmtui
Mixing networkmanagers that fight for the same interface is the primary cause for issues like these.
yep this seems to have fixed the issue, I didn't know iwd was a network manager, instead just a way to cnnect to the internet, and further didn't know about nmcli and nmtui. Thank you very good sir
]]>find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
Also post a complete system journal covering such connection losses ("sudo journalctl -b | curl -F 'f:1=<-' ix.io" for the current boot)
]]>Mixing networkmanagers that fight for the same interface is the primary cause for issues like these.
]]>I'm on kernel 5.15.2-arch1-1 and I'm using arch obviously.
Also It would automatically reconnect if I didnt use iwd but iwd makes it quicker. I'm also using NetworkManager
I checked systemctl status of NetworkManager.service when the internet cut out and it didn't say anything that would suggest there is something wrong.
Yeah, if anyone knows a fix, it would be much appreciated this is quite an annoying bug
]]>