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: Wifi Tethering (Daniel Wagner)
2. Re: Wifi Tethering (Daniel Wagner)
3. Re: connmanctl services --all? (Daniel Wagner)
4. Re: Request for help for Input/Output error creating BNEP
(Daniel Wagner)
5. Re: iwd scan integration (Daniel Wagner)
6. Re: Wired 802.1x via WPA_Supplicant (Daniel Wagner)
7. Re: Compatibility with Avahi question (Daniel Wagner)
8. Re: WiFi Scan not possible while Tethering -> "Device or resource busy"
(Daniel Wagner)
9. Re: Need help getting an ethernet connection (Daniel Wagner)
----------------------------------------------------------------------
Date: Sun, 24 May 2020 18:31:24 +0200
From: Daniel Wagner <[email protected]>
Subject: Re: Wifi Tethering
To: KeithG <[email protected]>
Cc: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
On 28.04.20 14:33, KeithG wrote:
> The pcap is here:
> https://drive.google.com/open?id=18G8cM5Ob88YENZ6WCWJjhBDREol7vW-9
The iwmon refuses to read this file, because it's of type
PCAP_TYPE_NETLINK. The tool expects it to be of type PCAP_TYPE_LINUX_SLL
[1].
I haven't look at what 'tcpdump -i nlmon' is supposed to do but it
doens't seem to work for me neithery. I've tried in on my system
(following the instructions) and I also get a trace file of type
PCAP_TYPE_NETLINK.
Changing the type check in monitor/main.c overcomes this problem:
--- a/monitor/main.c
+++ b/monitor/main.c
@@ -788,7 +788,7 @@ int main(int argc, char *argv[])
goto done;
}
- if (pcap_get_type(pcap) != PCAP_TYPE_LINUX_SLL) {
+ if (pcap_get_type(pcap) != PCAP_TYPE_NETLINK) {
fprintf(stderr, "Invalid packet format\n");
exit_status = EXIT_FAILURE;
} else
With this small hack, I decoded your trace. And there is no 802.11 entry
in it. Only routing and link setup packets.
I'd expected to see something like:
< Request: Get Wiphy (0x01) len 4 [ack,0x300]
16.731871
Split Wiphy Dump: true
> Result: New Wiphy (0x03) len 148 [multi]
16.731945
Wiphy: 0 (0x00000000)
Wiphy Name: phy0
Generation: 1 (0x00000001)
Wiphy Retry Short: 7 (0x07)
Wiphy Retry Long: 4 (0x04)
Wiphy Frag Threshold: 4294967295 (0xffffffff)
Wiphy RTS Threshold: 4294967295 (0xffffffff)
Wiphy Coverage Class: 0 (0x00)
Max Number Scan SSIDs: 4 (0x04)
Max Num Sched Scan SSIDs: 0 (0x00)
Max Scan IE Length: 2257 (0x08d1)
Max Sched Scan IE Len: 0 (0x0000)
Max Match Sets: 0 (0x00)
Reserved: len 4
01 00 00 00 ....
Reserved: len 4
ff ff ff ff ....
Reserved: len 4
00 00 00 00 ....
Support IBSS RSN: true
Support Mesh Auth: true
TDLS Support: true
TDLS External Setup: true
But there is nothing. This looks wrong to me. But now we are clearly in
iwd's domain and not ConnMan anymore.
Thanks,
Daniel
[1] http://www.tcpdump.org/linktypes/LINKTYPE_LINUX_SLL.html
------------------------------
Date: Sun, 24 May 2020 18:33:06 +0200
From: Daniel Wagner <[email protected]>
Subject: Re: Wifi Tethering
To: KeithG <[email protected]>
Cc: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi Keith,
On Tue, May 05, 2020 at 05:53:40PM -0500, KeithG wrote:
> I am on Arch Linux on my Pi and the latest version of iwd just came out and
> I tried this again. I get the same response. I cannot make a connection.
> Something tells me that I am doing something very simple wrong.
> Current iwd is 1.7 and connman is 1.38. I have built the kernel with the
> iwmon module and more of the functions of iwd now show up correctly, now. I
> do not know if it is because Arch finally went to 5.4 kernel from 4.19, but
> anyway it does look different:
After decoding your trace I think you need first to figure out why iwd doesn't
work for you. You don't need ConnMan to for this. Just you the iwctrl tool
to setup you network and try to get it working without ConnMan.
Thanks,
Daniel
------------------------------
Date: Sun, 24 May 2020 18:35:44 +0200
From: Daniel Wagner <[email protected]>
Subject: Re: connmanctl services --all?
To: Nuno Gonçalves <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-1
Hi Nuno,
On Thu, Apr 30, 2020 at 11:14:37AM +0100, Nuno Gonçalves wrote:
> Hi,
>
> I find myself wanting to obtain the connman service configuration when
> there is a only 1 or 2 services.
>
> It would be nice if there would be a option to dump all services state,
> like connmanctl dump or connmanctl services --all.
Do you mean what you get for 'connman services SERVICE_NAME'?
> Any comments before I would invest time in such a patch?
Sounds reasonable. Please go ahead :)
Thanks,
Daniel
------------------------------
Date: Sun, 24 May 2020 18:40:43 +0200
From: Daniel Wagner <[email protected]>
Subject: Re: Request for help for Input/Output error creating BNEP
To: Bnà Marco <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-1
Hi,
[please no html emails, just plain text emails]
On Wed, May 06, 2020 at 05:26:34PM +0000, Bnà Marco wrote:
> Hi all and thanks in advance to everyone that would like to help me.
>
> My problem is related to the attempt to automatically establish a BNEP from a
> board ARM with Yocto and Bluez to a Windows PC.
> The pairing is established successfully but I'm unable to finalize bnep
> creation with "connmanctl connect bluetooth_mac1_mac2".
> Here is the attached log of the error.
May 4 23:28:18 imx7-var-som bluetoothd[359]: bnep: failed
May 4 23:28:18 imx7-var-som bluetoothd[359]: connect failed Input/output error
May 4 23:28:18 imx7-var-som connmand[336]:
../connman-1.35/plugins/bluetooth.c:pan_connect_cb() network 0x1e58bd8
org.bluez.Error.Failed
>From a quick glance, I'd say you need to enable more verbose logging in BlueZ
and may it tells a bit more what's wrong.
Is the bnep module loaded?
Thanks,
Daniel
------------------------------
Date: Sun, 24 May 2020 18:55:23 +0200
From: Daniel Wagner <[email protected]>
Subject: Re: iwd scan integration
To: KeithG <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Thu, May 07, 2020 at 06:15:21PM -0500, KeithG wrote:
> Is anyone working on iwd scan integration? Currently, if iwd is installed
> and wpa_supplicant is not, "connmanctl scan" just hangs and requires ctrl c
> to get the prompt back. An error and a return would be useful.
> Regards,
Scanning is supported with iwd. connmanctl scan is probably waiting for iwd
to respond with the scanning=0 signal. If iwd doesn't send out this signal
then this will hang. You can use the monitor-iwd script. You should see
$ monitor-iwd
{Station} [/net/connman/iwd/0/6] Scanning = False
{Station} [/net/connman/iwd/0/6] Scanning = True
{Station} [/net/connman/iwd/0/6] Scanning = False
{Station} [/net/connman/iwd/0/6] Scanning = True
{Station} [/net/connman/iwd/0/6] Scanning = False
------------------------------
Date: Sun, 24 May 2020 19:02:43 +0200
From: Daniel Wagner <[email protected]>
Subject: Re: Wired 802.1x via WPA_Supplicant
To: Ryan Smith <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi Ryan,
On Sun, May 10, 2020 at 04:39:57AM -0000, Ryan Smith wrote:
> I messaged a while back about connecting to a wired 802.1x connection via
> connman. I was able to make a rudimentary integration using ead as the
> supplicant. This worked. However, ead has a version requirement for the Linux
> kernel that is >= 4.20 for EAP-TLS. Unfortunately, the device I am targeting
> does not have a new enough kernel available. I am investigating the
> feasibility of using wpa_supplicant for the wired 802.1x connection similar
> to how it is done for the wifi plugin. The device does not require
> simultaneous use of WiFi and Ethernet. We are setting
> SingleConnectedTechnology=true. The device is fixed in place and has no need
> to roam. It can be configured to connect to WiFi or Ethernet (and hopefully
> 802.1x).
My take on this is, update your kernel. Using old vendor kernels is just a waste
of time.
And even if you can't update, backporting the EAP-TLS support is not that
hard either.
> I have started an integration, using the wifi plugin as a pattern. I am
> creating a new plugin (and disabling the ethernet one). It looks like the
> g_supplicant code (and probably wpa_supplicant) only allows one user. Is
> there a way to switch between the two of them, or is this a no go?
Hmm, not sure what the problem is. I assume you are registering your plugin
using the ETHERNET type? What to you mean to switch between two? Do you mean you
want to use the wifi plugin at the same time? In this case I propably use
iwd to steer the wifi device and use wpa_supplicant just for the ethernet
device.
Thanks,
Daniel
------------------------------
Date: Sun, 24 May 2020 19:11:20 +0200
From: Daniel Wagner <[email protected]>
Subject: Re: Compatibility with Avahi question
To: KeithG <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi Keith,
On Sun, May 10, 2020 at 05:37:59PM -0500, KeithG wrote:
> My next trick it to try systemd-resolved with iwd and see if it is any
> better.
>
> Basically: Is there any basic incompatibility with avahi and connman?
I can't remember the status here. I though it kind of works but as you figured
out something seems to be broken.
> I see
> that connman can turn on mDNS on a per connection basis, but it is only
> compatible with systemd-resolved according to this:Connman Config
> <https://kernel.googlesource.com/pub/scm/network/connman/connman/+/master/doc/config-format.txt>.
> Is there a reason for this?
IIRC, the systemd-resolved intergration was provided by the Intel folks. I
suppose the figured out that avahi doesn't work for them either.
Thanks,
Daniel
------------------------------
Date: Sun, 24 May 2020 19:13:21 +0200
From: Daniel Wagner <[email protected]>
Subject: Re: WiFi Scan not possible while Tethering -> "Device or
resource busy"
To: "Ryll, Jan (GED-SDD2)" <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi Jan,
On Mon, May 11, 2020 at 03:56:42PM +0000, Ryll, Jan (GED-SDD2) wrote:
> I have 2 clients connected to this access point.
>
> Then I want to scan for other WiFi networks. This fails with -> "Device or
> resource busy"
> Execution of "iwlist scan" find networks at same time. Why it not work with
> connman scan?
I don't know. You need to look at the log and figure out at which level the
'Device or resource busy' is reported back.
Thanks,
Daniel
------------------------------
Date: Sun, 24 May 2020 19:15:47 +0200
From: Daniel Wagner <[email protected]>
Subject: Re: Need help getting an ethernet connection
To: Alex Ryan <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Wed, May 13, 2020 at 04:18:23PM -0700, Alex Ryan wrote:
> https://unix.stackexchange.com/questions/586494/how-do-i-get-an-ethernet-connection-with-automotive-grade-linux-halibut-8-0-0
It seems you are running udhcpc at the same time. ConnMan does DHCP itself. So
you need to disable the udhcpc daemon when running ConnMan.
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 55, Issue 12
***************************************
