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: [PATCH 2/2] ofono: store context apn value (Daniel Wagner)
2. Re: Connman apparently not working on my embedded target
(Mauro Condarelli)
3. Re: Connman apparently not working on my embedded target
(Michael Nazzareno Trimarchi)
4. Re: Turn off connman-vpn (KeithG)
----------------------------------------------------------------------
Date: Thu, 5 Mar 2020 09:45:47 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: [PATCH 2/2] ofono: store context apn value
To: nick83ola <[email protected]>
Cc: connman <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi Nicola,
On Wed, Mar 04, 2020 at 10:40:54AM +0000, nick83ola wrote:
> What I want to achieve with this and with another patch that I'm
> working on is to be able to set the apn settings in connman via dbus.
> And I wanted to ask:
> - is possible for connman technologies to define custom dbus properties?
Sure, it's possible but you need to extend the current code. There is
no code in place for plugins or scribtable API extensions.
> like the passphrase for wifi or the context settings (apn name,
> username, password) for the modem network.
> - How is the best way to achieve this? It needs modification in the
> technology ?
I think I would extend the agent API to handle this. In this way you
would have the same mechanism as for WiFi. And such a solution could
be added upstream.
> DO you have any example for this?
Have a look at the agent code. Though it's a bit WiFi centric.
Thanks,
Daniel
------------------------------
Date: Thu, 5 Mar 2020 10:26:35 +0100
From: Mauro Condarelli <[email protected]>
Subject: Re: Connman apparently not working on my embedded target
To: Michael Nazzareno Trimarchi <[email protected]>, Daniel
Wagner <[email protected]>
Cc: connman <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Hi Michael,
On 3/5/20 9:27 AM, Michael Nazzareno Trimarchi wrote:
> Hi
>
> On Thu, Mar 5, 2020 at 9:24 AM Daniel Wagner <[email protected]> wrote:
>> Hi Mauro,
>>
>>> # [ 7082.009030] ------------[ cut here ]------------
>>> [ 7082.013743] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:443
>>> 0x8037056c
>>> [ 7082.020887] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 0 timed
>>> out
>>> [ 7082.027937] Modules linked in: mt7603e mt76 mac80211 cfg80211 mtk_eth
>>> ehci_platform ehci_hcd usbcore usb_common
>>> [ 7082.038206] CPU: 0 PID: 0 Comm: swapper Not tainted 5.6.0-rc4 #2
>>> [ 7082.044291] Stack : 00000000 8004e5fc 80490000 80415810 00000000
>>> 00000000 00000000 00000000
>>> [ 7082.052772] 00000000 00000000 00000000 00000000 00000000
>>> 00000001 87c0bd78 80490000
>>> [ 7082.061249] 87c0be10 00000000 00000000 00000000 00000038
>>> 80407ca4 000000d8 00000000
>>> [ 7082.069728] 203a6d6d 87c0bbdc 80510000 70617773 80490000
>>> 00000000 00000009 00000009
>>> [ 7082.078208] 80480560 87c0bf0c 8037046c 00000122 00000003
>>> 802a7cbc 00000001 001d7f1f
>>> [ 7082.086688] ...
>>> [ 7082.089165] Call Trace:
>>> [ 7082.089177] [<8004e5fc>] 0x8004e5fc
>>> [ 7082.095185] [<80407ca4>] 0x80407ca4
>>> [ 7082.098720] [<8037046c>] 0x8037046c
>>> [ 7082.102254] [<802a7cbc>] 0x802a7cbc
>>> [ 7082.105788] [<8000aa38>] 0x8000aa38
>>> [ 7082.109321] [<8000aa40>] 0x8000aa40
>>> [ 7082.112856] [<8001d69c>] 0x8001d69c
>>> [ 7082.116390] [<8037056c>] 0x8037056c
>>> [ 7082.119924] [<8037056c>] 0x8037056c
>>> [ 7082.123456] [<8001d710>] 0x8001d710
>>> [ 7082.126993] [<8037056c>] 0x8037056c
>>> [ 7082.130527] [<80070274>] 0x80070274
>>> [ 7082.134064] [<80060254>] 0x80060254
>>> [ 7082.137596] [<8037046c>] 0x8037046c
>>> [ 7082.141129] [<8006040c>] 0x8006040c
>>> [ 7082.144665] [<80060c14>] 0x80060c14
>>> [ 7082.148199] [<8000d84c>] 0x8000d84c
>>> [ 7082.151732] [<800638e8>] 0x800638e8
>>> [ 7082.155267] [<80060c88>] 0x80060c88
>>> [ 7082.158801] [<804d0000>] 0x804d0000
>>> [ 7082.162334] [<8040e0e0>] 0x8040e0e0
>>> [ 7082.165875] [<80020740>] 0x80020740
>>> [ 7082.169409] [<80005910>] 0x80005910
>>> [ 7082.172939]
>>> [ 7082.174449] ---[ end trace c89d8f4203b47d1a ]---
>> This is a bug in the driver. Not much we can do in ConnMan.
>>
>>> [ 7082.179141] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
>>> [ 7082.185770] mtk_soc_eth 10100000.ethernet eth0: Link is Down
>>> [ 7082.206411] mtk_soc_eth 10100000.ethernet eth0: configuring for
>>> fixed/mii link mode
>>> [ 7082.229320] mtk_soc_eth 10100000.ethernet eth0: Link is Up -
>>> 100Mbps/Full - flow control rx/tx
>>> [ 7984.005249] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
>>> [ 7984.011860] mtk_soc_eth 10100000.ethernet eth0: Link is Down
>>> [ 7984.027073] mtk_soc_eth 10100000.ethernet eth0: configuring for
>>> fixed/mii link mode
>>> [ 7984.045472] mtk_soc_eth 10100000.ethernet eth0: Link is Up -
>>> 100Mbps/Full - flow control rx/tx
>>> [ 8884.002287] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
>>> [ 8884.008898] mtk_soc_eth 10100000.ethernet eth0: Link is Down
>>> [ 8884.024123] mtk_soc_eth 10100000.ethernet eth0: configuring for
>>> fixed/mii link mode
>>> [ 8884.042515] mtk_soc_eth 10100000.ethernet eth0: Link is Up -
>>> 100Mbps/Full - flow control rx/tx
>>> [ 9783.999653] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
>>> [ 9784.006276] mtk_soc_eth 10100000.ethernet eth0: Link is Down
>>> [ 9784.021499] mtk_soc_eth 10100000.ethernet eth0: configuring for
>>> fixed/mii link mode
>>> [ 9784.039883] mtk_soc_eth 10100000.ethernet eth0: Link is Up -
>>> 100Mbps/Full - flow control rx/tx
> https://lkml.org/lkml/2019/12/30/161
>
> Please refer here is you have this problem and the phy is the same.
> The up and down can be
> connected to a wrong reset of it
>
> Michael
>
Could You elaborate, please?
I do not believe I have the same PHY (my SoC is a Mediatek mips MT7628,
not an NxP ARM one); I also *suspect* problem is due to specific SoC
architecture sporting an internal 5-port Ethernet switch connected
to the MAC; this means MAC *always* sees a connection, even when
cable is disconnected (because disconnection is on "the other side" of
the switch).
I could be very wrong though, since I'm no expert on this.
Any hint would be *very* welcome.
Thanks in Advance
Mauro
------------------------------
Date: Thu, 5 Mar 2020 10:29:08 +0100
From: Michael Nazzareno Trimarchi <[email protected]>
Subject: Re: Connman apparently not working on my embedded target
To: Mauro Condarelli <[email protected]>
Cc: Daniel Wagner <[email protected]>, connman <[email protected]>
Message-ID:
<caof5uwmjjuxmwhxev4onnyno2er8cqscppbaizins4yzq41...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi
On Thu, Mar 5, 2020 at 10:26 AM Mauro Condarelli <[email protected]> wrote:
>
> Hi Michael,
>
> On 3/5/20 9:27 AM, Michael Nazzareno Trimarchi wrote:
> > Hi
> >
> > On Thu, Mar 5, 2020 at 9:24 AM Daniel Wagner <[email protected]> wrote:
> >> Hi Mauro,
> >>
> >>> # [ 7082.009030] ------------[ cut here ]------------
> >>> [ 7082.013743] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:443
> >>> 0x8037056c
> >>> [ 7082.020887] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 0
> >>> timed out
> >>> [ 7082.027937] Modules linked in: mt7603e mt76 mac80211 cfg80211 mtk_eth
> >>> ehci_platform ehci_hcd usbcore usb_common
> >>> [ 7082.038206] CPU: 0 PID: 0 Comm: swapper Not tainted 5.6.0-rc4 #2
> >>> [ 7082.044291] Stack : 00000000 8004e5fc 80490000 80415810 00000000
> >>> 00000000 00000000 00000000
> >>> [ 7082.052772] 00000000 00000000 00000000 00000000 00000000
> >>> 00000001 87c0bd78 80490000
> >>> [ 7082.061249] 87c0be10 00000000 00000000 00000000 00000038
> >>> 80407ca4 000000d8 00000000
> >>> [ 7082.069728] 203a6d6d 87c0bbdc 80510000 70617773 80490000
> >>> 00000000 00000009 00000009
> >>> [ 7082.078208] 80480560 87c0bf0c 8037046c 00000122 00000003
> >>> 802a7cbc 00000001 001d7f1f
> >>> [ 7082.086688] ...
> >>> [ 7082.089165] Call Trace:
> >>> [ 7082.089177] [<8004e5fc>] 0x8004e5fc
> >>> [ 7082.095185] [<80407ca4>] 0x80407ca4
> >>> [ 7082.098720] [<8037046c>] 0x8037046c
> >>> [ 7082.102254] [<802a7cbc>] 0x802a7cbc
> >>> [ 7082.105788] [<8000aa38>] 0x8000aa38
> >>> [ 7082.109321] [<8000aa40>] 0x8000aa40
> >>> [ 7082.112856] [<8001d69c>] 0x8001d69c
> >>> [ 7082.116390] [<8037056c>] 0x8037056c
> >>> [ 7082.119924] [<8037056c>] 0x8037056c
> >>> [ 7082.123456] [<8001d710>] 0x8001d710
> >>> [ 7082.126993] [<8037056c>] 0x8037056c
> >>> [ 7082.130527] [<80070274>] 0x80070274
> >>> [ 7082.134064] [<80060254>] 0x80060254
> >>> [ 7082.137596] [<8037046c>] 0x8037046c
> >>> [ 7082.141129] [<8006040c>] 0x8006040c
> >>> [ 7082.144665] [<80060c14>] 0x80060c14
> >>> [ 7082.148199] [<8000d84c>] 0x8000d84c
> >>> [ 7082.151732] [<800638e8>] 0x800638e8
> >>> [ 7082.155267] [<80060c88>] 0x80060c88
> >>> [ 7082.158801] [<804d0000>] 0x804d0000
> >>> [ 7082.162334] [<8040e0e0>] 0x8040e0e0
> >>> [ 7082.165875] [<80020740>] 0x80020740
> >>> [ 7082.169409] [<80005910>] 0x80005910
> >>> [ 7082.172939]
> >>> [ 7082.174449] ---[ end trace c89d8f4203b47d1a ]---
> >> This is a bug in the driver. Not much we can do in ConnMan.
> >>
> >>> [ 7082.179141] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
> >>> [ 7082.185770] mtk_soc_eth 10100000.ethernet eth0: Link is Down
> >>> [ 7082.206411] mtk_soc_eth 10100000.ethernet eth0: configuring for
> >>> fixed/mii link mode
> >>> [ 7082.229320] mtk_soc_eth 10100000.ethernet eth0: Link is Up -
> >>> 100Mbps/Full - flow control rx/tx
> >>> [ 7984.005249] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
> >>> [ 7984.011860] mtk_soc_eth 10100000.ethernet eth0: Link is Down
> >>> [ 7984.027073] mtk_soc_eth 10100000.ethernet eth0: configuring for
> >>> fixed/mii link mode
> >>> [ 7984.045472] mtk_soc_eth 10100000.ethernet eth0: Link is Up -
> >>> 100Mbps/Full - flow control rx/tx
> >>> [ 8884.002287] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
> >>> [ 8884.008898] mtk_soc_eth 10100000.ethernet eth0: Link is Down
> >>> [ 8884.024123] mtk_soc_eth 10100000.ethernet eth0: configuring for
> >>> fixed/mii link mode
> >>> [ 8884.042515] mtk_soc_eth 10100000.ethernet eth0: Link is Up -
> >>> 100Mbps/Full - flow control rx/tx
> >>> [ 9783.999653] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
> >>> [ 9784.006276] mtk_soc_eth 10100000.ethernet eth0: Link is Down
> >>> [ 9784.021499] mtk_soc_eth 10100000.ethernet eth0: configuring for
> >>> fixed/mii link mode
> >>> [ 9784.039883] mtk_soc_eth 10100000.ethernet eth0: Link is Up -
> >>> 100Mbps/Full - flow control rx/tx
> > https://lkml.org/lkml/2019/12/30/161
> >
> > Please refer here is you have this problem and the phy is the same.
> > The up and down can be
> > connected to a wrong reset of it
> >
> > Michael
> >
> Could You elaborate, please?
>
> I do not believe I have the same PHY (my SoC is a Mediatek mips MT7628,
> not an NxP ARM one); I also *suspect* problem is due to specific SoC
> architecture sporting an internal 5-port Ethernet switch connected
> to the MAC; this means MAC *always* sees a connection, even when
> cable is disconnected (because disconnection is on "the other side" of
> the switch).
Yes some phy needs to be proprer initialize so it means that if this
is not done in the correct way the up/down
situation can happen. This is happen on kernel level and not a problem
of user space. I was having the same
problem on some architecture that I fix. The patch point to the
problem and the way I fix. I don't say to you to
fix in that way, I have just ask to check if the problem is the phy
initiliazionion
Michael
>
> I could be very wrong though, since I'm no expert on this.
>
> Any hint would be *very* welcome.
>
> Thanks in Advance
> Mauro
--
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO - Founder Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
| [`as] http://www.amarulasolutions.com |
------------------------------
Date: Thu, 5 Mar 2020 10:20:52 -0600
From: KeithG <[email protected]>
Subject: Re: Turn off connman-vpn
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Message-ID:
<cag17s_mgr5gqozbtfwmisegfr46eqdlj0nnbhn2bgwmvoyx...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="0000000000005f532e05a01dec1c"
--0000000000005f532e05a01dec1c
Content-Type: text/plain; charset="UTF-8"
Daniel,
I read all of this, but it seemed that the defaults were to connect all of
them. I changed the settings in /etc/connman/main.conf and it seems to work.
It would nice if connmanctl could deal without connman-vpn, but I'll wait
for a fix. In the meantime, I'll leave it on to keep the connmanctl
responses clean..
Thanks!
Gearhead
On Wed, Mar 4, 2020 at 2:09 AM Daniel Wagner <[email protected]> wrote:
> Hi Gearhead,
>
> On Tue, Mar 03, 2020 at 01:40:25PM -0600, KeithG wrote:
> > Is there a way to turn this off? I am trying to convert form
> > netctl/ifplug/wpa_supplicant to connman/iwd and notice that connman-vpn
> is
> > always running.
>
> connman-vpnd is not started by connmand. systemd or some startup
> scripts start connman-vpnd.
>
> > This is for an audio appliance, so vpn is not needed. Is
> > there a configuration setting to turn this off short of compiling from
> > scratch? I have tried to mask the service but then I get errors when I
> try
> > to run connmanctl.
>
> You don't need connman-vpnd to run. connmanctl seems not be able to
> deal with the situation when connman-vpnd is not running though. This
> is a bug in connmanctl.
>
> > Also, I have to run the connman connect wifi_... to connect to my wifi AP
> > at boot. Is this normal. It has an ethernet cable connected and gets an
> IP
> > from there. I do not have it set to use only one interface but to get it
> to
> > connect, I have to run a script at startup to get it to connect to both
> > interfaces.
>
> The default behavior of ConnMan is to connect only one interface. You
> can tweak the behavior with the global config, e.g
>
> DefaultAutoConnectTechnologies
> DefaultFavoriteTechnologies
> AlwaysConnectedTechnologies
> PreferredTechnologies
>
> See man connman.config for more details on it.
>
> Thanks,
> Daniel
>
--0000000000005f532e05a01dec1c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Daniel,</div><div><br></div><div>I read all of this, =
but it seemed that the defaults were to connect all of them. I changed the =
settings in /etc/connman/main.conf and it seems to work.</div><div><br></di=
v><div>It would nice if connmanctl could deal without connman-vpn, but I=
9;ll wait for a fix. In the meantime, I'll leave it on to keep the conn=
manctl responses clean..<br></div><div><br></div><div>Thanks!</div><div><br=
></div><div>Gearhead<br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Wed, Mar 4, 2020 at 2:09 AM Daniel Wagner =
<<a href=3D"mailto:[email protected]";>[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">Hi Gearhead,<br>
<br>
On Tue, Mar 03, 2020 at 01:40:25PM -0600, KeithG wrote:<br>
> Is there a way to turn this off? I am trying to convert form<br>
> netctl/ifplug/wpa_supplicant to connman/iwd and notice that connman-vp=
n is<br>
> always running.<br>
<br>
connman-vpnd is not started by connmand. systemd or some startup<br>
scripts start connman-vpnd.<br>
<br>
> This is for an audio appliance, so vpn is not needed. Is<br>
> there a configuration setting to turn this off short of compiling from=
<br>
> scratch? I have tried to mask the service but then I get errors when I=
try<br>
> to run connmanctl.<br>
<br>
You don't need connman-vpnd to run. connmanctl seems not be able to<br>
deal with the situation when connman-vpnd is not running though. This<br>
is a bug in connmanctl.<br>
<br>
> Also, I have to run the connman connect wifi_... to connect to my wifi=
AP<br>
> at boot. Is this normal. It has an ethernet cable connected and gets a=
n IP<br>
> from there. I do not have it set to use only one interface but to get =
it to<br>
> connect, I have to run a script at startup to get it to connect to bot=
h<br>
> interfaces.<br>
<br>
The default behavior of ConnMan is to connect only one interface. You<br>
can tweak the behavior with the global config, e.g<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 DefaultAutoConnectTechnologies<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 DefaultFavoriteTechnologies<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 AlwaysConnectedTechnologies<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 PreferredTechnologies<br>
<br>
See man connman.config for more details on it.<br>
<br>
Thanks,<br>
Daniel<br>
</blockquote></div>
--0000000000005f532e05a01dec1c--
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 53, Issue 8
**************************************
