On 3/18/21 12:46 PM, haaber wrote:
> On 3/3/21 5:19 PM, 'qtpie' via qubes-users wrote:
>> Due to mysterious, unsolvable Wifi issues, I decided to replace the
>> wpa_supplicant wifi daemon with iwd.
> -- snip --
>> $ dnf remove wpa_supplicant
>> $ echo -e "[device] \nwifi.backend=iwd" | tee -a
>> /etc/NetworkManager/NetworkManager.conf
>> $ systemctl enable iwd.service
>> $ systemctl start iwd.service
>
> interesting. I tried that in my debian-minimal-net but I cannot start
> iwd with systemctl. Errors similar to here
>
> https://bbs.archlinux.org/viewtopic.php?id=250220
>
> but the proposed "solution" does not work. The thread suggests
>
> sudo cp /usr/lib/systemd/system/iwd.service /etc/systemd/system/
>
> but that file does simply not exist, so I cannot copy it. So I stopped
> that experiment for the moment. Maybe @unman has a suggestion for a
> well-working debian-based 'minimal' solution without networkmanager
> and/or wpa_applicant ? Best,
>
>
For those who want to stick to NetworkManager, II found out that the
$ systemctl enable iwd.service
$ systemctl start iwd.service
from my initial post, should not be necessary and can cause conflict.
Because NetworkManager is supposed to handle starting iwd, after iwd is
added to the NetworkManager config file.
That networkmanager does not handle iwd correctly, is a known issue with
NetworkManager. We can only wait for it to get updated with future
Fedora releases I guess.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/101
I am now also curious about non-networkmanager alternatives and their
usability though.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/73c466a3-2c9e-6227-343b-be8197d2b618%40disroot.org.
