Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Assignment Help, Essay Help and Dissertation Help
([email protected])
2. Re: [PATCH v1 0/3] Change auto connect strategy for iwd (KeithG)
----------------------------------------------------------------------
Date: Sat, 21 Nov 2020 11:17:12 -0000
From: [email protected]
Subject: Assignment Help, Essay Help and Dissertation Help
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Students often need assistance in their assignments. They look for quality
service providers and the best companies are Australian Assignment Help and
Student Life Saviour. They provide assistance in assignments in all subjects
and the services of Australian Assignment Help in nursing subject can be
availed at: https://australianassignmenthelp.com/nursing-assignment-help and
the services of Student Life Saviour in Canada at:
http://studentlifesaviour.com/ca
------------------------------
Date: Sat, 21 Nov 2020 08:40:10 -0600
From: KeithG <[email protected]>
Subject: Re: [PATCH v1 0/3] Change auto connect strategy for iwd
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Message-ID:
<CAG17S_Mbo+mQ02X0ycZCA-QP=8md7hje7vtrkwupdqk3c00...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="000000000000cc63fd05b49ef094"
--000000000000cc63fd05b49ef094
Content-Type: text/plain; charset="UTF-8"
Doing a bit more digging.
I am testing this by connecting on wlan0 only. My test is to verify I am
connected then restart the radio on my router and watch and see if the
device will reconnect when the SSID returns.
Applying these patches to the 'stable' 1.38, I get both an IPv4 and IPv6
address at startup, but do not get a reconnect on either IPv4 or IPv6.
Applying these patches to the current git HEAD 9d05df87I, I get IPv4 and
IPv6 at startup and get an immediate reconnect. The router shows that it
has an IPv4 and IPv6 address but the device only shows an IPv6 address.
When I try to ping it from another device on the LAN, I can ping the IPv6
but not the IPv4. Interestingly, if I take the wlan0 down then back up, I
get the same behavior, I only get an IPv6 address. The whole IPv4 subsystem
is down. /run/connman/resolv.conf only shows an IPv6 address for the DNS
server. If I restart connman at this point, it will grab the IPv4 address.
It appears to be very close to working. If you need a log, please let me
know what to put in the connman start command and I will provide it.
If I revert the e17f601cf4af ("gdhcp: Make DHCP client timeouts suspend
aware") commit to the current git HEAD, I get both IPv4 and IPv6 at
startup, but no reconnect on either IPv4 or IPv6. Restarting connman will
not cause a reconnect. I can reconnect by taking the wlan0 down then back
up. (ifconfig wlan0 down; ifconfig wlan0 up). When it reconnects it does so
on both IPv4 and IPv6.
Thanks,
KeithG
On Fri, Nov 20, 2020 at 5:20 PM KeithG <[email protected]> wrote:
> 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 <[email protected]> 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
>>
>
--000000000000cc63fd05b49ef094
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Doing a bit more digging. <br></div><div>I am testing=
this by connecting on wlan0 only. My test is to verify I am connected then=
restart the radio on my router and watch and see if the device will reconn=
ect when the SSID returns.<br></div><div><br></div><div>Applying these patc=
hes to the 'stable' 1.38, I get both an IPv4 and IPv6 address at st=
artup, but do not get a reconnect on either IPv4 or IPv6.</div><div><br></d=
iv><div>Applying these patches to the current git HEAD=20
9d05df87I, I get IPv4 and IPv6 at startup and get an immediate reconnect. T=
he router shows that it has an IPv4 and IPv6 address but the device only sh=
ows an IPv6 address. When I try to ping it from another device on the LAN, =
I can ping the IPv6 but not the IPv4. Interestingly, if I take the wlan0 do=
wn then back up, I get the same behavior, I only get an IPv6 address. The w=
hole IPv4 subsystem is down. /run/connman/resolv.conf only shows an IPv6 ad=
dress for the DNS server.=C2=A0
If I restart connman at this point, it will grab the IPv4 address.=20
It appears to be very close to working. If you need a log, please let me k=
now what to put in the connman start command and I will provide it.<br></di=
v><div><br></div><div>If I revert the=20
e17f601cf4af ("gdhcp: Make DHCP client timeouts suspend aware") =
commit to the current git HEAD, I get both IPv4 and IPv6 at startup, but no=
reconnect on either IPv4 or IPv6. Restarting connman will not cause a reco=
nnect. I can reconnect by taking the wlan0 down then back up. (ifconfig wla=
n0 down; ifconfig wlan0 up). When it reconnects it does so on both IPv4 and=
IPv6.</div><div><br></div><div>Thanks,</div><div><br></div><div>KeithG<br>=
</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Fri, Nov 20, 2020 at 5:20 PM KeithG <<a href=3D"mailto:ys3al35l=
@gmail.com">[email protected]</a>> wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex"><div dir=3D"ltr"><div>I applied these 3 patch=
es for autoconnect and verified that when the router is rebooted that the d=
evice (RaspberryPi running arch armv7) immediately grabs an IP address when=
the SSID returns. The only problem is that when it re-connects, it only gr=
abs an IPv6 address and no IPv4. At startup, it grabs an IPv4 and an IPv6 a=
ddress, but when it reconnects it only connects with IPv6. <br></div><div><=
br></div><div>I found a previous discussion where I ran into a similar thin=
g with connman (no ipv4 upon reconnect) 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:[email protected]" target=3D"_blank">[email protected]</a>> wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(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>
</blockquote></div>
--000000000000cc63fd05b49ef094--
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 61, Issue 13
***************************************
