Send connman mailing list submissions to
connman@lists.01.org
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
connman-requ...@lists.01.org
You can reach the person managing the list at
connman-ow...@lists.01.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: [PATCH v1 0/3] Change auto connect strategy for iwd (KeithG)
----------------------------------------------------------------------
Date: Fri, 20 Nov 2020 17:20:07 -0600
From: KeithG <ys3al...@gmail.com>
Subject: Re: [PATCH v1 0/3] Change auto connect strategy for iwd
To: Daniel Wagner <w...@monom.org>
Cc: connman@lists.01.org
Message-ID:
<cag17s_n_n0s_z6zctyuectmk9jehcvj0uo+owty1ipfv90j...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="000000000000752ba905b49216fe"
--000000000000752ba905b49216fe
Content-Type: text/plain; charset="UTF-8"
I applied these 3 patches for autoconnect and verified that when the router
is rebooted that the device (RaspberryPi running arch armv7) immediately
grabs an IP address when the SSID returns. The only problem is that when it
re-connects, it only grabs an IPv6 address and no IPv4. At startup, it
grabs an IPv4 and an IPv6 address, but when it reconnects it only connects
with IPv6.
I found a previous discussion where I ran into a similar thing with connman
(no ipv4 upon reconnect) and Daniel suggested reverting the e17f601cf4af
("gdhcp: Make DHCP client timeouts suspend aware") commit. I tried this as
well with the current head at 9d05df87.The result was that connman no
longer reconnects when the router is rebooted. No IPv6 nor IPv4 address. I
could log it if this may help. What parameters should I set for connman to
get a useful log of this?
KeithG
On Fri, Nov 20, 2020 at 9:44 AM Daniel Wagner <w...@monom.org> wrote:
> As reported by KeithG, ConnMan's auto connect doesn't work well with
> iwd. ConnMan disabled the autoconnect modus of iwd for all
> networks. This let iwd chill and slow down the scaning thus finding a
> network took pretty long. This series will set the auto_connect
> property for iwd's KnowNetworks when the corresponding ConnMan service
> has the AutoConnect set. In my simple setup it seems to work.
>
> Daniel Wagner (3):
> network: Add connman_network_set_autoconect()
> service: Propagade autoconnect mode to network
> iwd: Enable/disable auto_connect on known networks
>
> include/network.h | 4 +
> plugins/iwd.c | 258 ++++++++++++++++++++++++++++++----------------
> src/network.c | 8 ++
> src/service.c | 4 +
> 4 files changed, 184 insertions(+), 90 deletions(-)
>
> --
> 2.29.2
>
--000000000000752ba905b49216fe
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>I applied these 3 patches for autoconnect and verifie=
d that when the router is rebooted that the device (RaspberryPi running arc=
h armv7) immediately grabs an IP address when the SSID returns. The only pr=
oblem is that when it re-connects, it only grabs an IPv6 address and no IPv=
4. At startup, it grabs an IPv4 and an IPv6 address, but when it reconnects=
it only connects with IPv6. <br></div><div><br></div><div>I found a previo=
us discussion where I ran into a similar thing with connman (no ipv4 upon r=
econnect) and Daniel suggested reverting the=20
e17f601cf4af ("gdhcp: Make DHCP client timeouts suspend aware") =
commit. I tried this as well with the current head at 9d05df87.The result w=
as that connman no longer reconnects when the router is rebooted. No IPv6 n=
or IPv4 address. I could log it if this may help. What parameters should I =
set for connman to get a useful log of this?</div><div><br></div><div>Keith=
G<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Fri, Nov 20, 2020 at 9:44 AM Daniel Wagner <<a href=3D"mai=
lto:w...@monom.org">w...@monom.org</a>> wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">As reported by KeithG, ConnMan's auto=
connect doesn't work well with<br>
iwd. ConnMan disabled the autoconnect modus of iwd for all<br>
networks. This let iwd chill and slow down the scaning thus finding a<br>
network took pretty long. This series will set the auto_connect<br>
property for iwd's KnowNetworks when the corresponding ConnMan service<=
br>
has the AutoConnect set. In my simple setup it seems to work.<br>
<br>
Daniel Wagner (3):<br>
=C2=A0 network: Add connman_network_set_autoconect()<br>
=C2=A0 service: Propagade autoconnect mode to network<br>
=C2=A0 iwd: Enable/disable auto_connect on known networks<br>
<br>
=C2=A0include/network.h |=C2=A0 =C2=A04 +<br>
=C2=A0plugins/iwd.c=C2=A0 =C2=A0 =C2=A0| 258 ++++++++++++++++++++++++++++++=
----------------<br>
=C2=A0src/network.c=C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A08 ++<br>
=C2=A0src/service.c=C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A04 +<br>
=C2=A04 files changed, 184 insertions(+), 90 deletions(-)<br>
<br>
-- <br>
2.29.2<br>
</blockquote></div>
--000000000000752ba905b49216fe--
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- connman@lists.01.org
To unsubscribe send an email to connman-le...@lists.01.org
------------------------------
End of connman Digest, Vol 61, Issue 12
***************************************
