Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, 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: Any C / C++ test program available? (JH)
2. Re: Failed to create storage directory: No such file or
directory (JH)
3. Re: connmanctl scan wifi: Error /net/connman/technology/wifi:
Not implemented ([email protected])
4. crash of connmand ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Wed, 27 Mar 2019 19:49:41 +1100
From: JH <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: connman <[email protected]>
Subject: Re: Any C / C++ test program available?
Message-ID:
<CAA=hcwsvd+thy63a7eqn9bc+ucg7-3uaigmsot4_34le4bo...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Thanks Daniel for pointing me where to start, great helps.
Kind regards,
- jupiter
On 3/27/19, Daniel Wagner <[email protected]> wrote:
> Hi,
>
> On Sun, Mar 24, 2019 at 09:24:01PM +1100, JH wrote:
>> Hi,
>>
>> The Git source has a test directory but they are all Python test
>> programs, are there any C / C++ test programs available for:
>>
>> (1) Set up WiFi connection based on input of SSID and password.
>>
>> (2) Get current connected network interface at configuration of
>> SingleConnectedTechnology = true
>>
>> (3) Monitor network signal strength for WiFi and cellular.
>
> I think a good starting point are the existing UI. check the list of
> frontends on Arch's wiki:
>
> https://wiki.archlinux.org/index.php/ConnMan
>
> Thanks,
> Daniel
>
------------------------------
Message: 2
Date: Wed, 27 Mar 2019 22:11:45 +1100
From: JH <[email protected]>
To: Jussi Laakkonen <[email protected]>
Cc: Daniel Wagner <[email protected]>, connman <[email protected]>
Subject: Re: Failed to create storage directory: No such file or
directory
Message-ID:
<CAA=hcwqkmt88x3p8drutd6zsza8gpm6gjj5iqbaj3f4nn98...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi Jussi,
I am sorry, I am still learning ConnMan. I original installed ConnMan
Ubuntu package v 1.35, it failed to run scan WiFi (posted to another
email), so I thought to try the latest git source, to compile it in
Ubuntu 18.04, but I did not run make install to set up configure files
in /etc, all /etc configure files could be linked to the Ubuntu
ConnMan 1.35. I would say it is my fault to have mixed versions, my
apology.
I am going to build ConnMan on Yocto and to run it on imx6 board, that
will have a clean environment. Will see if there is any issue or not.
Sorry about it.
Thank you.
- jupiter
On 3/27/19, Jussi Laakkonen <[email protected]> wrote:
> Hi Daniel and JH,
>
>
> On 3/27/19 9:46 AM, Daniel Wagner wrote:
>> Hi,
>>
>> On Tue, Mar 19, 2019 at 09:44:25PM +1100, JH wrote:
>>> connmand[25650]: ./src/iptables.c:__connman_iptables_append() -t
>>> mangle -A connman-INPUT -j CONNMARK --restore-mark
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x0000000000000000 in ?? ()
>>> (gdb) backtrace
>>> #0 0x0000000000000000 in ?? ()
>>> #1 0x00007ffff7669080 in xtables_find_target ()
>>> from /usr/lib/x86_64-linux-gnu/libxtables.so.12
>>> #2 0x00007ffff766949b in ?? () from
>>> /usr/lib/x86_64-linux-gnu/libxtables.so.12
>>> #3 0x00007ffff7669152 in xtables_find_target ()
>>> from /usr/lib/x86_64-linux-gnu/libxtables.so.12
>>> #4 0x00005555555dc77a in prepare_target (
>>> target_name=0x555555842a90 "CONNMARK", table=0x555555867840)
>>> at ./src/iptables.c:1574
>>> #5 parse_rule_spec (table=<optimised out>, ctx=0x555555867f80)
>>> at ./src/iptables.c:1993
>>> #6 0x00005555555dd1d8 in __connman_iptables_append (
>>> table_name=table_name@entry=0x5555558419c0 "mangle",
>>> chain=chain@entry=0x555555842c10 "connman-INPUT",
>>> rule_spec=rule_spec@entry=0x555555862460 "-j CONNMARK
>>> --restore-mark")
>>> at ./src/iptables.c:2196
>>> #7 0x00005555555e7094 in insert_managed_rule (
>>> rule_spec=0x555555862460 "-j CONNMARK --restore-mark",
>>> chain_name=<optimised out>, table_name=0x5555558419c0 "mangle")
>>> at ./src/firewall.c:180
>>> #8 __connman_firewall_enable (ctx=ctx@entry=0x555555841820)
>>> at ./src/firewall.c:336
>>> ---Type <return> to continue, or q <return> to quit---
>>> #9 0x00005555555d4a68 in init_firewall ()
>>> at ./src/session.c:219
>>> #10 0x00005555555d6cd5 in init_firewall ()
>>> at ./src/session.c:1740
>>> #11 __connman_session_init ()
>>> at ./src/session.c:1734
>>> #12 0x0000555555572270 in main (argc=<optimised out>, argv=<optimised
>>> out>)
>>> at ./src/main.c:670
>>
>>
>> iptables is a bit tricky, especially error handling. I am not 100%
>> convienced this code works right. But I don't want to touch it
>> either. Too many gray haires already. The last brave soul to touch it
>> was Jussi and I think he spend a lot of time hunting stuff.
>>
>> If possible try to use the nftable backend instead of the iptables,
>> because there we have proper APIs to use.
>>
>> That said, I see ConnMan was able to remove the old rules and fails
>> adding the CONNMARK rule to the mangle table. Is the CONNMARK and
>> mangle table available?
>>
>> Thanks,
>> Daniel
>
> To JH:
>
> Which version of ConnMan are you using? According to the line numbers in
> the GDB output the version you have does not include the improved error
> handling for iptables, see [1],[2].
>
> And I think these are requried to be enabled in kernel configs to use
> CONNMARK target and match:
> CONFIG_NETFILTER_XT_CONNMARK
> CONFIG_NETFILTER_XT_TARGET_CONNMARK
> CONFIG_NETFILTER_XT_MATCH_CONNMARK
> CONFIG_NET_ACT_CONNMARK (not sure if this is needed)
>
> I hope adding those to kernel configs helps with this issue.
>
>
> To Daniel:
>
> Yes, finding out these things with iptables takes time :) We have now
> iptables 1.8.2 in use and as of now it seems that patch I mentioned in
> [2] is no longer necessary. It applied only for iptables 1.6.1 (and most
> likely, for 1.6.x).
>
> Sincerely,
> Jussi Laakkonen
>
>
> [1]
> https://git.kernel.org/pub/scm/network/connman/connman.git/commit/?id=b209d1ac4048d5fdfc480113f9fdaa005667a10e
> [2]
> https://git.kernel.org/pub/scm/network/connman/connman.git/tree/src/iptables.c#n2682
>
>
> [3] https://lists.01.org/pipermail/connman/2019-January/023146.html
>
------------------------------
Message: 3
Date: Wed, 27 Mar 2019 18:41:09 +0100
From: <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Subject: Re: connmanctl scan wifi: Error /net/connman/technology/wifi:
Not implemented
Message-ID: <20190327184109.557867ee@huit>
Content-Type: text/plain; charset=US-ASCII
Hi Daniel,
thanks a lot for your quick diagnostics and feedback!!
Is there an alternative (agent) that I could be using?
I am wondering how do others do? (how do you do?): Why is no one else
complaining?
Is it because they all use wpa_supplicant?
Or is there another possible agent? (systemd's netctl maybe ??)
And how does Jolla do?
Curious mind :)
Tormen
--
On Wed, 27 Mar 2019
08:38:40 +0100 Daniel Wagner <[email protected]> wrote:
> Hi Tormen,
>
> On Tue, Mar 26, 2019 at 08:09:26PM +0100, [email protected] wrote:
> > Hi,
> >
> > I have a problem to make wifi work within connman.
> >
> > I tried to google, tried, googled, tried, but can't get around
> > it :/ ... so I really hope someone can give me a hint.
>
> No worries. I know that feeling.
>
> > 'connmanctl scan wifi' always gives me a
> > Error /net/connman/technology/wifi: Not implemented
> >
> > I am currently using iwd, it's running. iwd can access wifi
> > and scan all good [1].
> > Just connman seems to have a problem connecting to it.
> >
> > [1] for instance all of this works fine:
> > 'sudo iw wlan0'
> > 'iwctl device list'
> > 'iwctl station wlan0 scan'
> > 'iwctl station wlan0 get-networks'
> >
> > I had first tried wpa_supplicant... and am now using iwd
> > (supposedly iwd is a bit more stable / better ?!)
>
> iwd is far easier to use from ConnMan's perspective. The only problem
> is that I haven't updated the plugin for a while.
>
> > Both showed the same symtptoms and problems.
> >
> > I then stopped iwd and connman (via systemctl).
> > Then I started logging journalctl right before
> > starting iwd via systemctl.
> > --> see journalctl.log
> > http://sprunge.us/hJog0I
>
> I see that ConnMan detects the iwd service on D-Bus. But that's about
> it. There is no interaction. I suppose that is a API issue. The plugin
> needs to be updated to a recent version of iwd.
>
> > PS:
> > My goal is actually to use cmst later.
> > For now within cmst the "Rescan" button is grayed out.
> > (most likely because the connection to the wifi agent is broken)
>
> And the scan feature needs to be added as well.
>
> I'll update the plugin if no one else is stepping up. But don't expect
> me to be done with it in few days :)
>
> Thanks,
> Daniel
------------------------------
Message: 4
Date: Wed, 27 Mar 2019 18:47:20 +0100
From: <[email protected]>
To: [email protected]
Subject: crash of connmand
Message-ID: <20190327184720.6910a90c@huit>
Content-Type: text/plain; charset=US-ASCII
Hi again,
well in my short time with connmand I got it already to crash for me.
Must be my good influence that tends to bring out the best of
software ;)
Please find the output of connmand -n -d here:
http://sprunge.us/zyKJkl
And a journalctl of a 2nd crash here:
http://sprunge.us/766omR
I don't remember the exact circumstances, so for now that's all I got.
Please let me know if there is anything else I can do to assist.
Tormen
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 41, Issue 28
***************************************
