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. Current connman master has difficulty getting ipv4 address
(KeithG)
2. Re: connman wifi disconnect problem (KeithG)
----------------------------------------------------------------------
Date: Fri, 2 Oct 2020 13:03:32 -0500
From: KeithG <[email protected]>
Subject: Current connman master has difficulty getting ipv4 address
To: [email protected]
Message-ID:
<CAG17S_NQLE+iCD9=n60efo6bmtyx2b503gc08-x-j696q_-...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="00000000000001e53905b0b3f4ed"
--00000000000001e53905b0b3f4ed
Content-Type: text/plain; charset="UTF-8"
I have built the latest connman from the git repo . I am running it with
iwd and I have noticed that it is reluctant to grab an IPv4 address on the
wifi interface. It appears to get an ipv6 and I can connect to it, but not
from it. The ethernet interface seems unaffected as it always grabs an IP
address. Noticed on arch linux x86_64 as well as on Raspberry Pi. Am I the
only one seeing this? The release version of 1.38 does not seem to suffer
from this.
Also, I notice that whenever connman is started, it soft blocks the
bluetooth radio. I am not using bluetooth as a network interface, but for a
keyboard and audio. Is there some setting in connman main.conf that should
be set to counter this? As it is, I add an ExecPost to the service file to
unblock bluetooth, but wondering if there is something else I should/could
do.
Keith
--00000000000001e53905b0b3f4ed
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>I have built the latest connman from the git repo . I=
am running it with iwd and I have noticed that it is reluctant to grab an =
IPv4 address on the wifi interface. It appears to get an ipv6 and I can con=
nect to it, but not from it. The ethernet interface seems unaffected as it =
always grabs an IP address. Noticed on arch linux x86_64 as well as on Rasp=
berry Pi. Am I the only one seeing this? The release version of 1.38 does n=
ot seem to suffer from this. <br></div><div><br></div><div>Also, I notice t=
hat whenever connman is started, it soft blocks the bluetooth radio. I am n=
ot using bluetooth as a network interface, but for a keyboard and audio. Is=
there some setting in connman main.conf that should be set to counter this=
? As it is, I add an ExecPost to the service file to unblock bluetooth, but=
wondering if there is something else I should/could do. <br></div><div><br=
></div><div>Keith<br></div></div>
--00000000000001e53905b0b3f4ed--
------------------------------
Date: Fri, 2 Oct 2020 13:08:58 -0500
From: KeithG <[email protected]>
Subject: Re: connman wifi disconnect problem
To: Daniel Wagner <[email protected]>
Cc: "Ryll, Jan (GED-SDD2)" <[email protected]>, "[email protected]"
<[email protected]>
Message-ID:
<CAG17S_Mi+N=LJ9=9=Ws=niryuldvdme+t0dsp8jpssm2ba-...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="00000000000073329105b0b4079b"
--00000000000073329105b0b4079b
Content-Type: text/plain; charset="UTF-8"
Daniel,
I finally figured it out. With connman 1.38, I get it to reconnect if I
down the interface *and* if I reboot the router.
What I noticed when looking at the logs was that after the disconnect,
nothing was telling iwd to reconnect. iwd wasn't nor was connman. it just
sat there. I looked again at the /etc/connman/main.conf and noticed that
there was a setting:
BackgroundScanning = true
I uncommented this line and now it manages the interface as designed. I do
not know why it took me so long to figure this out, but it now connects.
Does this mean it always periodically scans? If so, it may be nice to only
do this if it is not connected.
Thanks for your patience with me.
Keith
On Thu, Oct 1, 2020 at 7:27 PM KeithG <[email protected]> wrote:
> Daniel et al
>
> Still at this. I gave up on the RPI for now and am working on 2 laptops
> with full blown Arch desktop. One laptop has a broadcom card and the other
> an intel. I get the same result on both. If I let NetworkManager/iwd manage
> the network the laptops reconnect as soon as the SSID reappears. Same if I
> let systemd-networkd control it. If I let connman manage the network,
> though, it will never reconnect to the SSID. This is with connman 1.37 and
> 1.38. and 1.38.r21. If I turn off the interface: 'ifconfig wlan0 down' then
> back 'up', the laptop disconnects then reconnects immediately. If I turn
> off the radio on the router, though, it never reconnects by itself. If I
> type 'connmanctl services' I get a single service listed as opposed to a
> list of a bunch of SSIDs. If I wait, it sometimes will eventually populate
> that list and even list the 'known network' but will not connect. On these
> laptops, I have been able to get it to reconnect if I type 'iwctl station
> wlan0 scan' as well. If this does not work, it will connect if I bring the
> interface down then back up.
>
> The attached logs are simultaneous from a 'connected on the wlan' state.
> From here I powered down the radio on the router then powered it back up.
> From the logs, it looks like it disconnects then ceases scanning. It waited
> in this state for many minutes (15?) As soon as I typed 'iwctl station
> wlan0 scan' it connects and I am back online.Which component is supposed to
> initiate the scan when it is offline? This was on the laptop with the
> broadcom card and no ethernet conneccted.
>
> The Arch package is built according to this package:
> https://github.com/archlinux/svntogit-community/tree/packages/connman/trunk
>
> Keith
>
>
>
>
> On Thu, Oct 1, 2020 at 2:29 AM Daniel Wagner <[email protected]> wrote:
>
>> On Wed, Sep 30, 2020 at 08:40:28PM -0500, KeithG wrote:
>> > I am at a loss as to how to help resolve this and really want to help
>> get
>> > it resolved.
>> > It appears that connman1.38 will initiate a scan via 'connmanctl scan
>> wifi'
>> > even though it does not report that it has scanned. The git version
>> > (1.38.r23) will report on the cli that it has scanned. So, that is an
>> > improvement.
>>
>> 6b391cfd294d ("iwd: Synchronize station scanning property with scan
>> state") fixed this. Please next time if something doesn't work update
>> first to the development version to replicate the problem. This avoids
>> wasting time for everyone.
>>
>> > If I use either 1.38 (the current Arch Linux package) or build it from
>> git,
>> > I cannot ge tthe Rpi or my laptop to reconnect when the ssid is rebooted
>> > even though the 'services' for the SSID
>> > show that it is 'autoconnect' and monitor-connman shows that is 'ses'
>> it.
>> > Is there some main.conf setting that I have wrong?
>> >
>> > main.conf:
>> > FallbackNameservers = 8.8.8.8,8.8.4.4
>> > DefaultAutoConnectTechnologies = ethernet,wifi
>> > AllowHostnameUpdates = false
>> > AlwaysConnectedTechnologies = ethernet,wifi
>> > AutoConnectRoamingServices = true
>> >
>> > As I said previously, the only modifications to the build of the connman
>> > package under Arch are that it adds that dbus 'Agent' bits and also
>> that it
>> > deletes the tmpfiles.d in the package that calls out a /var/run
>> directory
>> > because Arch uses /run/. Other than that it is built under Arch as it is
>> > called out in the git to be built.
>>
>> This should be fine. Don't think this is a problem.
>>
>> > From my testing, ./monitor-connman seems to 'see' the ssid return, but
>> will
>> > not reconnect after the router is rebooted.
>> >
>> > If I use systemd-networkd and iwd, it reconnects every time. With
>> connman
>> > and iwd, I get no reconnect over a reboot.
>>
>> I've redone my test with
>>
>> AlwaysConnectedTechnologies = ethernet,wifi
>> SingleConnectedTechnology = false
>>
>> and pulling the ethernet cable and disabling/enabling the wifi
>> network. ConnMan reconnected to both networks.
>>
>
--00000000000073329105b0b4079b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Daniel,</div><div><br></div><div>I finally figured it=
out. With connman 1.38, I get it to reconnect if I down the interface *and=
* if I reboot the router. <br></div><div><br></div><div>What I noticed when=
looking at the logs was that after the disconnect, nothing was telling iwd=
to reconnect. iwd wasn't nor was connman. it just sat there. I looked =
again at the /etc/connman/main.conf and noticed that there was a setting:</=
div><div>
BackgroundScanning =3D true <br></div><div><br></div><div>I uncommented thi=
s line and now it manages the interface as designed. I do not know why it t=
ook me so long to figure this out, but it now connects. Does this mean it a=
lways periodically scans? If so, it may be nice to only do this if it is no=
t connected.</div><div><br></div><div>Thanks for your patience with me.<br>=
</div><div><br></div><div>Keith<br></div></div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 1, 2020 at 7:27 PM Kei=
thG <<a href=3D"mailto:[email protected]";>[email protected]</a>> wr=
ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D=
"ltr"><div>Daniel et al</div><div><br></div><div>Still at this. I gave up o=
n the RPI for now and am working on 2 laptops with full blown Arch desktop.=
One laptop has a broadcom card and the other an intel. I get the same resu=
lt on both. If I let NetworkManager/iwd manage the network the laptops reco=
nnect as soon as the SSID reappears. Same if I let systemd-networkd control=
it. If I let connman manage the network, though, it will never reconnect t=
o the SSID. This is with connman 1.37 and 1.38. and 1.38.r21. If I turn off=
the interface: 'ifconfig wlan0 down' then back 'up', the l=
aptop disconnects then reconnects immediately. If I turn off the radio on t=
he router, though, it never reconnects by itself. If I type 'connmanctl=
services' I get a single service listed as opposed to a list of a bunc=
h of SSIDs. If I wait, it sometimes will eventually populate that list and =
even list the 'known network' but will not connect. On these laptop=
s, I have been able to get it to reconnect if I type 'iwctl station wla=
n0 scan' as well. If this does not work, it will connect if I bring the=
interface down then back up.</div><div><br></div><div>
The attached logs are simultaneous from a 'connected on the wlan' s=
tate. From here I powered down the radio on the router then powered it back=
up. From the logs, it looks like it disconnects then ceases scanning. It w=
aited in this state for many minutes (15?) As soon as I typed 'iwctl st=
ation wlan0 scan' it connects and I am back online.Which component is s=
upposed to initiate the scan when it is offline? This was on the laptop wit=
h the broadcom card and no ethernet conneccted. <br></div><div><br></div><d=
iv>The Arch package is built according to this package:</div><div><a href=
=3D"https://github.com/archlinux/svntogit-community/tree/packages/connman/t=
runk" target=3D"_blank">https://github.com/archlinux/svntogit-community/tre=
e/packages/connman/trunk</a></div><div><br></div><div>Keith<br></div><div><=
br></div><div><br></div><div><br></div></div><br><div class=3D"gmail_quote"=
><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 1, 2020 at 2:29 AM Danie=
l Wagner <<a href=3D"mailto:[email protected]"; target=3D"_blank">wagi@monom=
.org</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">On Wed, Sep 30, 2020 at 08:40:28PM -0500, KeithG wrote:<br>
> I am at a loss as to how to help resolve this and really want to help =
get<br>
> it resolved.<br>
> It appears that connman1.38 will initiate a scan via 'connmanctl s=
can wifi'<br>
> even though it does not report that it has scanned. The git version<br=
>
> (1.38.r23) will report on the cli that it has scanned. So, that is an<=
br>
> improvement.<br>
<br>
6b391cfd294d ("iwd: Synchronize station scanning property with scan<br=
>
state") fixed this. Please next time if something doesn't work upd=
ate<br>
first to the development version to replicate the problem. This avoids<br>
wasting time for everyone.<br>
<br>
> If I use either 1.38 (the current Arch Linux package) or build it from=
git,<br>
> I cannot ge tthe Rpi or my laptop to reconnect when the ssid is reboot=
ed<br>
> even though the 'services' for the SSID<br>
> show that it is 'autoconnect' and monitor-connman shows that i=
s 'ses' it.<br>
> Is there some main.conf setting that I have wrong?<br>
> <br>
> main.conf:<br>
> FallbackNameservers =3D 8.8.8.8,8.8.4.4<br>
> DefaultAutoConnectTechnologies =3D ethernet,wifi<br>
> AllowHostnameUpdates =3D false<br>
> AlwaysConnectedTechnologies =3D ethernet,wifi<br>
> AutoConnectRoamingServices =3D true<br>
> <br>
> As I said previously, the only modifications to the build of the connm=
an<br>
> package under Arch are that it adds that dbus 'Agent' bits and=
also that it<br>
> deletes the tmpfiles.d in the package that calls out a /var/run direct=
ory<br>
> because Arch uses /run/. Other than that it is built under Arch as it =
is<br>
> called out in the git to be built.<br>
<br>
This should be fine. Don't think this is a problem.<br>
<br>
> From my testing, ./monitor-connman seems to 'see' the ssid ret=
urn, but will<br>
> not reconnect after the router is rebooted.<br>
> <br>
> If I use systemd-networkd and iwd, it reconnects every time. With conn=
man<br>
> and iwd, I get no reconnect over a reboot.<br>
<br>
I've redone my test with<br>
<br>
=C2=A0 AlwaysConnectedTechnologies =3D ethernet,wifi<br>
=C2=A0 SingleConnectedTechnology =3D false<br>
<br>
and pulling the ethernet cable and disabling/enabling the wifi<br>
network. ConnMan reconnected to both networks.<br>
</blockquote></div>
</blockquote></div>
--00000000000073329105b0b4079b--
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 60, Issue 2
**************************************
