Start iwd only after dbus

Start iwd only after dbus

[dapolinario]

[-- Attachment #1: Type: text/plain, Size: 315 bytes --]

When iwd is not synchronized to start after dbus, NetworkManager often does not identify that the service is already running and does not manage the wireless interface.

I suggest adding the line "After=dbus.service" in "iwd.service" in the [Unit] section, so NetworkManager always identifies that iwd is working.

Re: Start iwd only after dbus

[Paul Menzel]

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]


Dear dapolinario,


Am 02.06.20 um 05:35 schrieb dapolinario(a)gmail.com:
> When iwd is not synchronized to start after dbus, NetworkManager
> often does not identify that the service is already running and does
> not manage the wireless interface.
> 
> I suggest adding the line "After=dbus.service" in "iwd.service" in
> the [Unit] section, so NetworkManager always identifies that iwd is
> working.
Did that fix that issue for you permanently?

How is iwd started? By NetworkManager over D-Bus or by systemd, because 
it was installed into it?

There is NetworkManager issue *iwd backend gets activated but NM 
considers the device unavailable* [1] about problems when iwd gets 
started by NM.


Kind regards,

Paul


[1]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/101

Re: Start iwd only after dbus

[Daniel Apolinario]

[-- Attachment #1: Type: text/plain, Size: 527 bytes --]

Hello!

> How is iwd started? By NetworkManager over D-Bus or by systemd, because 
> it was installed into it?
Iwd is started by NetworkManager over D-Bus instead of systemd.

> There is NetworkManager issue *iwd backend gets activated but NM 
> considers the device unavailable* [1] about problems when iwd gets 
> started by NM.
Yes, this fix solves my problem and the referenced NetworkManager issue. I performed several tests and every time the interface was available for NetworkManager.

Kind regards

Daniel