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. Re: connman wifi disconnect problem (KeithG)
2. Re: connman wifi disconnect problem (Daniel Wagner)
3. Re: connman wifi disconnect problem ([email protected])
4. Re: [PATCH v2] ipconfig: cleanup ipdevice gateway fields
([email protected])
5. Re: ipv6 test web page down ([email protected])
6. Re: [PATCH 5/6] vpn-provider: Support split routing option for VPN
providers
([email protected])
7. Re: The Best MBA Essay Writing Service ([email protected])
----------------------------------------------------------------------
Date: Tue, 6 Oct 2020 09:01:54 -0500
From: KeithG <[email protected]>
Subject: Re: connman wifi disconnect problem
To: Daniel Wagner <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID:
<cag17s_m4sqae57chxvvpdjp4aw29gyy4br1y-rwd0mng6zl...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="00000000000041fa1405b1010b84"
--00000000000041fa1405b1010b84
Content-Type: text/plain; charset="UTF-8"
On Tue, Oct 6, 2020 at 1:29 AM Daniel Wagner <[email protected]> wrote:
> On Mon, Oct 05, 2020 at 08:57:47AM -0500, KeithG wrote:
> > As for the eth0 up and down, it looks like it is being controlled by
> > connman. At least journalctl thinks so:
> >
> > Oct 05 08:18:53 rune64 connmand[4313]: eth0 {update} flags 36866 <DOWN>
> > Oct 05 08:18:53 rune64 connmand[4313]: eth0 {newlink} index 3 address
> > B8:27:EB:07:99:85 mtu 1500
> > Oct 05 08:18:53 rune64 connmand[4313]: eth0 {newlink} index 3 operstate 2
> > <DOWN>
> > Oct 05 08:18:53 rune64 connmand[4313]: eth0 {update} flags 36867 <UP>
> > Oct 05 08:18:53 rune64 connmand[4313]: eth0 {newlink} index 3 address
> > B8:27:EB:07:99:85 mtu 1500
> > Oct 05 08:18:53 rune64 connmand[4313]: eth0 {newlink} index 3 operstate 2
> > <DOWN>
> > Oct 05 08:34:20 rune64 connmand[4313]: eth0 {update} flags 36866 <DOWN>
> > Oct 05 08:34:20 rune64 connmand[4313]: eth0 {newlink} index 3 address
> > B8:27:EB:07:99:85 mtu 1500
> > Oct 05 08:34:20 rune64 connmand[4313]: eth0 {newlink} index 3 operstate 2
> > <DOWN>
> > Oct 05 08:34:20 rune64 connmand[4313]: eth0 {update} flags 36867 <UP>
> > Oct 05 08:34:20 rune64 connmand[4313]: eth0 {newlink} index 3 address
> > B8:27:EB:07:99:85 mtu 1500
> > Oct 05 08:34:20 rune64 connmand[4313]: eth0 {newlink} index 3 operstate 2
> > <DOWN>
> >
> > Spams the log with this.
>
> No, this doesn't mean it's controlled by ConnMan. ConnMan just logs the
> state of the interfaces. If there are no other log entries when running
> with 'connmand -n -d src/service.c' saying let's connnect/disconnect,
> then it's something else enabling/disabling the interface.
>
Daniel,
I think I found what is spamming the log. It isn't connman, but a script we
are running to check the interfaces. I have disabled that and will watch it
some more.
As I see it, there are still 3 strange things going on:
1) the latest git will not grab an ipv4 address. I will revert that commit
and try this again. Probably have time later this week.
2) the IPv6 online check still always fails (though it has a valid ipv4 and
ipv6 address) I can connect to ipv6 addresses via ping/curl/wget and I can
connect to it via ssh with its ipv6 address. I currently disable the online
check and the link shows as AR and not AO.
Oct 05 18:41:10 rune64 connmand[185]: Failed to find URL:
http://ipv6.connman.net/online/status.html
Oct 06 06:32:46 rune64 connmand[43232]:
src/service.c:__connman_service_online_check_failed() service 0x55902cbb10
type IPv6 interval 6
Oct 06 06:32:46 rune64 connmand[43232]:
src/service.c:connman_service_ref_debug() 0x55902cbb10 ref 4 by
src/service.c:6205:__connman_service_online_check_failed()
Oct 06 06:33:23 rune64 connmand[43232]:
src/service.c:connman_service_unref_debug() 0x55902cbb10 ref 3 by
src/service.c:6160:redo_wispr()
Oct 06 06:33:23 rune64 connmand[43232]: src/service.c:redo_wispr() Retrying
IPv6 WISPr for 0x55902cbb10 spg3
Oct 06 06:35:32 rune64 connmand[43232]:
src/service.c:__connman_service_online_check_failed() service 0x55902cbb10
type IPv6 interval 7
Oct 06 06:35:32 rune64 connmand[43232]:
src/service.c:connman_service_ref_debug() 0x55902cbb10 ref 4 by
src/service.c:6205:__connman_service_online_check_failed()
Oct 06 06:36:22 rune64 connmand[43232]:
src/service.c:connman_service_unref_debug() 0x55902cbb10 ref 3 by
src/service.c:6160:redo_wispr()
Oct 06 06:36:22 rune64 connmand[43232]: src/service.c:redo_wispr() Retrying
IPv6 WISPr for 0x55902cbb10 spg3
Oct 06 06:38:32 rune64 connmand[43232]:
src/service.c:__connman_service_online_check_failed() service 0x55902cbb10
type IPv6 interval 8
Oct 06 06:38:32 rune64 connmand[43232]:
src/service.c:connman_service_ref_debug() 0x55902cbb10 ref 4 by
src/service.c:6205:__connman_service_online_check_failed()
Oct 06 06:39:37 rune64 connmand[43232]:
src/service.c:connman_service_unref_debug() 0x55902cbb10 ref 3 by
src/service.c:6160:redo_wispr()
Oct 06 06:39:37 rune64 connmand[43232]: src/service.c:redo_wispr() Retrying
IPv6 WISPr for 0x55902cbb10 spg3
3) (most confounding) I am using a setting for wpa_supplicant which seems
to work to get iwd to reconnect when the router goes down then back up.
This setting is supposed to only work with wpa_supplicant. I am leery of
calling this 'fixed' on my end as it is not supposed to work.
On this, I wonder if it would reconnect if connman actually forced the iwd
config setting to AutoConnect=true. Currently when connman is controlling
iwd, the iwd config looks like this:
[Security]
PreSharedKey=xxxxxx
Passphrase=password
[Settings]
AutoConnect=false
I cannot edit the AutoConnect to be 'true' because connman is controlling
it and resets it every time I try to edit it. But, without the
BacgroundScan setting in main.conf, iwd never gets a trigger to scan after
it has lost the connection and, therefore will never reconnect when the
SSID reappears. When I use systemd-networkd and iwd, I can edit this iwd
setting to true and it always reconnects. wpa_supplicant is not installed.
Keith
--00000000000041fa1405b1010b84
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Oct 6, 2020 at 1:29 AM Daniel Wag=
ner <<a href=3D"mailto:[email protected]";>[email protected]</a>> wrote:<br>=
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">On Mon, Oct 05, 2020 at 08:57:47AM -0500, KeithG wrote:<br>
> As for the eth0 up and down, it looks like it is being controlled by<b=
r>
> connman. At least journalctl thinks so:<br>
> <br>
> Oct 05 08:18:53 rune64 connmand[4313]: eth0 {update} flags 36866 <D=
OWN><br>
> Oct 05 08:18:53 rune64 connmand[4313]: eth0 {newlink} index 3 address<=
br>
> B8:27:EB:07:99:85 mtu 1500<br>
> Oct 05 08:18:53 rune64 connmand[4313]: eth0 {newlink} index 3 operstat=
e 2<br>
> <DOWN><br>
> Oct 05 08:18:53 rune64 connmand[4313]: eth0 {update} flags 36867 <U=
P><br>
> Oct 05 08:18:53 rune64 connmand[4313]: eth0 {newlink} index 3 address<=
br>
> B8:27:EB:07:99:85 mtu 1500<br>
> Oct 05 08:18:53 rune64 connmand[4313]: eth0 {newlink} index 3 operstat=
e 2<br>
> <DOWN><br>
> Oct 05 08:34:20 rune64 connmand[4313]: eth0 {update} flags 36866 <D=
OWN><br>
> Oct 05 08:34:20 rune64 connmand[4313]: eth0 {newlink} index 3 address<=
br>
> B8:27:EB:07:99:85 mtu 1500<br>
> Oct 05 08:34:20 rune64 connmand[4313]: eth0 {newlink} index 3 operstat=
e 2<br>
> <DOWN><br>
> Oct 05 08:34:20 rune64 connmand[4313]: eth0 {update} flags 36867 <U=
P><br>
> Oct 05 08:34:20 rune64 connmand[4313]: eth0 {newlink} index 3 address<=
br>
> B8:27:EB:07:99:85 mtu 1500<br>
> Oct 05 08:34:20 rune64 connmand[4313]: eth0 {newlink} index 3 operstat=
e 2<br>
> <DOWN><br>
> <br>
> Spams the log with this.<br>
<br>
No, this doesn't mean it's controlled by ConnMan. ConnMan just logs=
the<br>
state of the interfaces. If there are no other log entries when running<br>
with 'connmand -n -d src/service.c' saying let's connnect/disco=
nnect,<br>
then it's something else enabling/disabling the interface.<br></blockqu=
ote><div>Daniel,</div><div><br></div><div>I think I found what is spamming =
the log. It isn't connman, but a script we are running to check the int=
erfaces. I have disabled that and will watch it some more. <br></div><div><=
br></div><div>As I see it, there are still 3 strange things going on:</div>=
<div>1) the latest git will not grab an ipv4 address. I will revert that co=
mmit and try this again. Probably have time later this week.<br></div><div>=
<br></div><div>2) the IPv6 online check still always fails (though it has a=
valid ipv4 and ipv6 address) I can connect to ipv6 addresses via ping/curl=
/wget and I can connect to it via ssh with its ipv6 address. I currently di=
sable the online check and the link shows as AR and not AO.<br></div><div><=
br></div><div>Oct 05 18:41:10 rune64 connmand[185]: Failed to find URL:<a h=
ref=3D"http://ipv6.connman.net/online/status.html";>http://ipv6.connman.net/=
online/status.html</a></div><div><br></div><div>Oct 06 06:32:46 rune64 conn=
mand[43232]: src/service.c:__connman_service_online_check_failed() service =
0x55902cbb10 type IPv6 interval 6<br>Oct 06 06:32:46 rune64 connmand[43232]=
: src/service.c:connman_service_ref_debug() 0x55902cbb10 ref 4 by src/servi=
ce.c:6205:__connman_service_online_check_failed()<br>Oct 06 06:33:23 rune64=
connmand[43232]: src/service.c:connman_service_unref_debug() 0x55902cbb10 =
ref 3 by src/service.c:6160:redo_wispr()<br>Oct 06 06:33:23 rune64 connmand=
[43232]: src/service.c:redo_wispr() Retrying IPv6 WISPr for 0x55902cbb10 sp=
g3<br>Oct 06 06:35:32 rune64 connmand[43232]: src/service.c:__connman_servi=
ce_online_check_failed() service 0x55902cbb10 type IPv6 interval 7<br>Oct 0=
6 06:35:32 rune64 connmand[43232]: src/service.c:connman_service_ref_debug(=
) 0x55902cbb10 ref 4 by src/service.c:6205:__connman_service_online_check_f=
ailed()<br>Oct 06 06:36:22 rune64 connmand[43232]: src/service.c:connman_se=
rvice_unref_debug() 0x55902cbb10 ref 3 by src/service.c:6160:redo_wispr()<b=
r>Oct 06 06:36:22 rune64 connmand[43232]: src/service.c:redo_wispr() Retryi=
ng IPv6 WISPr for 0x55902cbb10 spg3<br>Oct 06 06:38:32 rune64 connmand[4323=
2]: src/service.c:__connman_service_online_check_failed() service 0x55902cb=
b10 type IPv6 interval 8<br>Oct 06 06:38:32 rune64 connmand[43232]: src/ser=
vice.c:connman_service_ref_debug() 0x55902cbb10 ref 4 by src/service.c:6205=
:__connman_service_online_check_failed()<br>Oct 06 06:39:37 rune64 connmand=
[43232]: src/service.c:connman_service_unref_debug() 0x55902cbb10 ref 3 by =
src/service.c:6160:redo_wispr()<br>Oct 06 06:39:37 rune64 connmand[43232]: =
src/service.c:redo_wispr() Retrying IPv6 WISPr for 0x55902cbb10 spg3</div><=
div><br></div><div>3) (most confounding) I am using a setting for wpa_suppl=
icant which seems to work to get iwd to reconnect when the router goes down=
then back up. This setting is supposed to only work with wpa_supplicant. I=
am leery of calling this 'fixed' on my end as it is not supposed t=
o work. <br></div><div><br></div><div>On this, I wonder if it would reconne=
ct if connman actually forced the iwd config setting to AutoConnect=3Dtrue.=
Currently when connman is controlling iwd, the iwd config looks like this:=
</div><div><br></div><div>[Security]<br>PreSharedKey=3Dxxxxxx<br>Passphrase=
=3Dpassword<br><br>[Settings]<br>AutoConnect=3Dfalse</div><div><br></div><d=
iv>I cannot edit the AutoConnect to be 'true' because connman is co=
ntrolling it and resets it every time I try to edit it. But, without the Ba=
cgroundScan setting in main.conf, iwd never gets a trigger to scan after it=
has lost the connection and, therefore will never reconnect when the SSID =
reappears. When I use systemd-networkd and iwd, I can edit this iwd setting=
to true and it always reconnects. wpa_supplicant is not installed.=C2=A0</=
div><div><br></div><div>Keith<br></div></div></div>
--00000000000041fa1405b1010b84--
------------------------------
Date: Wed, 7 Oct 2020 08:15:37 +0200
From: Daniel Wagner <[email protected]>
Subject: Re: connman wifi disconnect problem
To: KeithG <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Tue, Oct 06, 2020 at 09:01:54AM -0500, KeithG wrote:
> As I see it, there are still 3 strange things going on:
> 1) the latest git will not grab an ipv4 address. I will revert that commit
> and try this again. Probably have time later this week.
Yes, please. It's the only commit which modified anything around DHCP.
> 2) the IPv6 online check still always fails (though it has a valid ipv4 and
> ipv6 address) I can connect to ipv6 addresses via ping/curl/wget and I can
> connect to it via ssh with its ipv6 address. I currently disable the online
> check and the link shows as AR and not AO.
I've still not setup an IPv6 network for testing, thus it's hard to test.
> 3) (most confounding) I am using a setting for wpa_supplicant which seems
> to work to get iwd to reconnect when the router goes down then back up.
> This setting is supposed to only work with wpa_supplicant. I am leery of
> calling this 'fixed' on my end as it is not supposed to work.
Are you referring to BackgroundScanning? This doesn't do anything for
iwd. There is literally no code in ConnMan's core nor in the iwd plugin
looking at this variable.
> On this, I wonder if it would reconnect if connman actually forced the iwd
> config setting to AutoConnect=true. Currently when connman is controlling
> iwd, the iwd config looks like this:
>
> [Security]
> PreSharedKey=xxxxxx
> Passphrase=password
>
> [Settings]
> AutoConnect=false
>
> I cannot edit the AutoConnect to be 'true' because connman is controlling
> it and resets it every time I try to edit it. But, without the
> BacgroundScan setting in main.conf, iwd never gets a trigger to scan after
> it has lost the connection and, therefore will never reconnect when the
> SSID reappears. When I use systemd-networkd and iwd, I can edit this iwd
> setting to true and it always reconnects. wpa_supplicant is not installed.
As I explained, ConnMan is disabling iwd's AutoConnect. When to connect
to a network is ConnMan's decision not iwd.
ConnMan doesn't need to tell iwd when to scan. The BackgroundScanning
knob was added to ConnMan because wpa_supplicant is only doing have of
the job. Please have a look at one of Marcel Holtmann's iwd
presentation, e.g.
https://www.youtube.com/watch?v=QIqT2obSPDk
------------------------------
Date: Wed, 07 Oct 2020 06:23:55 -0000
From: [email protected]
Subject: Re: connman wifi disconnect problem
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Custom psychology research writing services have become very popular among
students seeking Psychology Assignment Writing Services and psychology essay
writing services.
https://researchpapers247.com/psychology-assignment-writing-services-2/
------------------------------
Date: Wed, 07 Oct 2020 06:24:19 -0000
From: [email protected]
Subject: Re: [PATCH v2] ipconfig: cleanup ipdevice gateway fields
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
There is a reliable Healthcare Assignment Writing Service that is very popular
for students in search of healthcare coursework writing services and nursing
essay writing help services.
https://researchpapers247.com/healthcare-assignment-writing-service/
------------------------------
Date: Wed, 07 Oct 2020 06:24:40 -0000
From: [email protected]
Subject: Re: ipv6 test web page down
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
There are many theology & religion coursework writing services and Religious
Research Writing Services to choose from for those stuck with their religion
assignment writing services and theology essay writing help services.
https://researchpapers247.com/religious-research-writing-services/
------------------------------
Date: Wed, 07 Oct 2020 06:25:07 -0000
From: [email protected]
Subject: Re: [PATCH 5/6] vpn-provider: Support split routing option
for VPN providers
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Medical coursework writing service seekers have been on the rise lately since
most learners need Medical Research Paper Services, nursing research writing
services and medical essay writing services.
https://researchpapers247.com/medical-research-paper-services/
------------------------------
Date: Wed, 07 Oct 2020 06:25:27 -0000
From: [email protected]
Subject: Re: The Best MBA Essay Writing Service
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Seeking psychology research writing services are very common nowadays since
there are very many students in need of Psychology Coursework Writing Services
and psychology assignment writing services.
https://researchpapers247.com/psychology-coursework-writing-service/
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 60, Issue 6
**************************************
