The SignalLevelAgent API is currently broken by the system bus's
security policy, which blocks iwd's outgoing method call messages. This
patch punches a hole for method calls on the
src/iwd-dbus.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/iwd-dbus.conf b/src/iwd-dbus.conf
index 4b3636e0..7fc2e68c 100644
@@ -11,6 +11,7 @@
+ <allow send_interface="net.connman.iwd.SignalLevelAgent"/>
There appears to be no method for having IWD disable DNS Updates
is there some method that is undocumented available?
I want to have IWD manage my connections and use the internal DHCP daemon
but I do not want systemd-resolved or resolveconf being updated
I run my own DNS daemon
The only solution I can think of to this issue is to disable iwd connection management entirely
though i would prefer not to
I'm encountering a couple of issues with the DHCP client in iwd
specifically when the network environment is flaky.
The major issue I have is when the iwd client is disconnected either
from a channel change or just a low signal. The DHCP client gets a new
lease when it connects but never asks for a lease renewal which
eventually means it loses it after the expiration. This paste shows
the logs of this happening https://pastebin.com/yGJbUmVR (I have
enabled IWD_DHCP_DEBUG=1 to get more data but I am still waiting for
it to happen again).
My plan is to see if I can reproduce the issue on a smaller scale (we
have ~130 clients running and it happens maybe twice a day) and once I
can reproduce I will update iwd and ell to see if that fixes it (I'm
using version 1.21 iwd and 0.47 ell). I looked through the new commits
since my versions and there was nothing explicitly about this but
c78ad1bb and b02c2034 look possibly related?
For now, I wonder if you know of an obvious place that a disconnect
might not be cleaning up the DHCP state fully which causes the T1
timer not to be set?
As for the second minor issue, it seems like iwd doesn't retry sending
a DHCPREQUEST once it's passed the T1 timer and in the RENEW state
which I believe it should based on
I have seen the first request being lost due to a bad signal and then
iwd didn't try again until T2 which is a more complete renewal. This
doesn't cause any interruption but does cause the lease to be removed
before being renewed.