12:37 p.m.
I'm using a Raspberry Pi 3 with the stretch distribution. Connman is at
V1.33 and wpa_supplicant is at V2.4. connmanctl technologies does not
show p2p. However iw list shows p2p go and p2p client support and I can
run wpa_cli and do a p2p_find command which shows p2p available devices.
Does anybody know what's going on here? Why won't connmanctl
technologies show p2p?
Carl
2:18 p.m.
Hi Carl,
On Wed, Aug 23, 2017 at 7:37 PM, Carl D. Blake
<carl.blake(a)pointmaker.com> wrote:
I'm using a Raspberry Pi 3 with the stretch distribution.
Connman is at
V1.33 and wpa_supplicant is at V2.4. connmanctl technologies does not
show p2p. However iw list shows p2p go and p2p client support and I can
run wpa_cli and do a p2p_find command which shows p2p available devices.
Well, that's strange.
Does anybody know what's going on here? Why won't
connmanctl
technologies show p2p?
Let's start from the very first checks. First of all, make sure wifi
technology is enabled, if it is disabled then any WiFi activity is
denied on your system and P2P is part of them. Therefore, ConnMan will
not even show you P2P as technology.
Now, if that was not the reason, let's check if wpa_supplicant is
correctly notifying ConnMan about the capabilities supported by your
system:
1. Check wpa_supplicant global capabilities by executing D-Bus call:
dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1
/fi/w1/wpa_supplicant1 org.freedesktop.DBus.Properties.GetAll
string:"fi.w1.wpa_supplicant1"
You should see something like:
[...]
dict entry(
string "Capabilities"
variant array [
[...]
string "p2p"
]
)
[...]
2. Check per interface capabilities. Change X with the value(s) you
got in (1) into "Interfaces" property.
dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1
/fi/w1/wpa_supplicant1/Interfaces/{X}
org.freedesktop.DBus.Properties.GetAll
string:"fi.w1.wpa_supplicant1.Interface"
Here, look for "Modes" property, you should see something like:
[...]
dict entry(
string "Modes"
variant array [
[...]
string "p2p"
]
)
[...]
For me those are the very first checks you should do, nothing else
comes to my mind for now. If everything is on point, we will probably
ask you to send us your ConnMan's logs with CONNMAN_SUPPLICANT_DEBUG
enabled to try to understand what is going on.
I hope this help you.
Best regards,
Jose Blanquicet
3:08 p.m.
Hi Jose,
On Wed, 2017-08-23 at 21:18 +0200, Jose Blanquicet wrote:
Hi Carl,
On Wed, Aug 23, 2017 at 7:37 PM, Carl D. Blake
<carl.blake(a)pointmaker.com> wrote:
> I'm using a Raspberry Pi 3 with the stretch distribution. Connman is at
> V1.33 and wpa_supplicant is at V2.4. connmanctl technologies does not
> show p2p. However iw list shows p2p go and p2p client support and I can
> run wpa_cli and do a p2p_find command which shows p2p available devices.
Well, that's strange.
> Does anybody know what's going on here? Why won't connmanctl
> technologies show p2p?
Let's start from the very first checks. First of all, make sure wifi
technology is enabled, if it is disabled then any WiFi activity is
denied on your system and P2P is part of them. Therefore, ConnMan will
not even show you P2P as technology.
The command:
connmanctl technologies
gives the following result:
/net/connman/technology/bluetooth
Name = Bluetooth
Type = bluetooth
Powered = False
Connected = False
Tethering = False
/net/connman/technology/wifi
Name = WiFi
Type = wifi
Powered = True
Connected = False
Tethering = False
Now, if that was not the reason, let's check if wpa_supplicant is
correctly notifying ConnMan about the capabilities supported by your
system:
1. Check wpa_supplicant global capabilities by executing D-Bus call:
dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1
/fi/w1/wpa_supplicant1 org.freedesktop.DBus.Properties.GetAll
string:"fi.w1.wpa_supplicant1"
You should see something like:
[...]
dict entry(
string "Capabilities"
variant array [
[...]
string "p2p"
]
)
[...]
This command shows string "p2p" in the "Capabilities" just as you
showed.
2. Check per interface capabilities. Change X with the value(s) you
got in (1) into "Interfaces" property.
dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1
/fi/w1/wpa_supplicant1/Interfaces/{X}
org.freedesktop.DBus.Properties.GetAll
string:"fi.w1.wpa_supplicant1.Interface"
Here, look for "Modes" property, you should see something like:
[...]
dict entry(
string "Modes"
variant array [
[...]
string "p2p"
]
)
[...]
I assume with this command that you want me to run this on each
interface as listed in the dict entry( string "Interfaces".
Unfortunately, there are no interfaces listed in this dict entry. It
shows:
dict entry(
string "Interfaces"
variant array [
]
)
Thoughts? Thank you for your detailed help.
For me those are the very first checks you should do, nothing else
comes to my mind for now. If everything is on point, we will probably
ask you to send us your ConnMan's logs with CONNMAN_SUPPLICANT_DEBUG
enabled to try to understand what is going on.
I hope this help you.
Best regards,
Jose Blanquicet
3:38 p.m.
Hi Carl,
On Wed, Aug 23, 2017 at 10:08 PM, Carl D. Blake
<carl.blake(a)pointmaker.com> wrote:
I assume with this command that you want me to run this on each
interface as listed in the dict entry( string "Interfaces".
Unfortunately, there are no interfaces listed in this dict entry. It
shows:
dict entry(
string "Interfaces"
variant array [
]
)
Thoughts? Thank you for your detailed help.
That's a problem. Are you even able to perform a wifi scan?
I think the problem here could be your wpa_supplicant configuration.
Check you are compiling wpa_supplicant with
CONFIG_CTRL_IFACE_DBUS_NEW=y and you are adding "-u" option when you
are launching it in order to enable DBus control interface.
Further details are given in "wpa_supplicant configuration" section of
ConnMan's README file.
Best regards,
Jose Blanquicet
4:23 p.m.
Hi Jose,
On Wed, 2017-08-23 at 22:38 +0200, Jose Blanquicet wrote:
Hi Carl,
On Wed, Aug 23, 2017 at 10:08 PM, Carl D. Blake
<carl.blake(a)pointmaker.com> wrote:
> I assume with this command that you want me to run this on each
> interface as listed in the dict entry( string "Interfaces".
> Unfortunately, there are no interfaces listed in this dict entry. It
> shows:
> dict entry(
> string "Interfaces"
> variant array [
> ]
> )
>
> Thoughts? Thank you for your detailed help.
That's a problem. Are you even able to perform a wifi scan?
No I can't do a wifi scan. The command:
connmanctl scan wifi
returns
Error /net/connman/technology/wifi: No carrier
I think the problem here could be your wpa_supplicant configuration.
Check you are compiling wpa_supplicant with
CONFIG_CTRL_IFACE_DBUS_NEW=y and you are adding "-u" option when you
are launching it in order to enable DBus control interface.
When I check what's running as wpa_supplicant I see 2 instances. One
has the flag -u. The other just has the flag -B. Looking through the
logs leads me to believe that dhcpcd is running wpa_supplicant with -B
and no -u flag. I'm checking further.
Further details are given in "wpa_supplicant configuration"
section of
ConnMan's README file.
Best regards,
Jose Blanquicet
4:45 p.m.
Hi Jose,
On Wed, 2017-08-23 at 14:23 -0700, Carl D. Blake wrote:
Hi Jose,
On Wed, 2017-08-23 at 22:38 +0200, Jose Blanquicet wrote:
> Hi Carl,
>
> On Wed, Aug 23, 2017 at 10:08 PM, Carl D. Blake
> <carl.blake(a)pointmaker.com> wrote:
> > I assume with this command that you want me to run this on each
> > interface as listed in the dict entry( string "Interfaces".
> > Unfortunately, there are no interfaces listed in this dict entry. It
> > shows:
> > dict entry(
> > string "Interfaces"
> > variant array [
> > ]
> > )
> >
> > Thoughts? Thank you for your detailed help.
>
> That's a problem. Are you even able to perform a wifi scan?
>
No I can't do a wifi scan. The command:
connmanctl scan wifi
returns
Error /net/connman/technology/wifi: No carrier
> I think the problem here could be your wpa_supplicant configuration.
> Check you are compiling wpa_supplicant with
> CONFIG_CTRL_IFACE_DBUS_NEW=y and you are adding "-u" option when you
> are launching it in order to enable DBus control interface.
>
When I check what's running as wpa_supplicant I see 2 instances. One
has the flag -u. The other just has the flag -B. Looking through the
logs leads me to believe that dhcpcd is running wpa_supplicant with -B
and no -u flag. I'm checking further.
That was it. dhcpcd had a /lib/dhcpcd/dhcpcd-hooks/10-wpa_supplicant
script which was running wpa_supplicant without -u. I added the -u flag
to the command line and rebooted. Now connman sees p2p as a technology,
I can scan wifi without errors, and I can make a p2p connection.
Hurray. Thank you for your help.
> Further details are given in "wpa_supplicant
configuration" section of
> ConnMan's README file.
>
> Best regards,
>
> Jose Blanquicet
_______________________________________________
connman mailing list
connman(a)lists.01.org
https://lists.01.org/mailman/listinfo/connman
1:35 a.m.
Good morning Carl,
On Wed, Aug 23, 2017 at 9:45 PM, Carl D. Blake
<carl.blake(a)pointmaker.com> wrote:
> > I think the problem here could be your wpa_supplicant
configuration.
> > Check you are compiling wpa_supplicant with
> > CONFIG_CTRL_IFACE_DBUS_NEW=y and you are adding "-u" option when you
> > are launching it in order to enable DBus control interface.
> >
I will ask to add this to the documentation.
> When I check what's running as wpa_supplicant I see 2
instances. One
> has the flag -u. The other just has the flag -B. Looking through the
> logs leads me to believe that dhcpcd is running wpa_supplicant with -B
> and no -u flag. I'm checking further.
>
That was it. dhcpcd had a /lib/dhcpcd/dhcpcd-hooks/10-wpa_supplicant
script which was running wpa_supplicant without -u. I added the -u flag
to the command line and rebooted.
If you are managing all your connections from ConnMan, you do not need
additional DHCP daemons. On the contrary, I would suggest you to not
lunch them or even better remove them from your system to save
resources. Moreover, if you do not need any particular configuration
for wpa_supplicat, you will not need an additional script to launch
it, ConnMan could take care of this, see README for further details.
Now connman sees p2p as a technology,
I can scan wifi without errors, and I can make a p2p connection.
Great. We have been working on P2P from a while but it is still
experimental so do not hesitate to share your suggestions,
improvements or report your issues if you have any.
Hurray. Thank you for your help.
You are welcome.
Best regards,
Jose Blanquicet
3:03 a.m.
On Thu, 2017-08-24 at 06:35 +0000, Jose Blanquicet wrote:
If you are managing all your connections from ConnMan, you do not
need additional DHCP daemons. On the contrary, I would suggest you to
not lunch them or even better remove them from your system to save
resources.
Actually, if other DHCP daemons are running on the same interface, the
usual problem is that no IP address is getting assigned to the
interface. And this causes quite a lot of head scratching, so I'm with
Jose here that all other DHCP daemons better be removed unless it is
known they are absolutely necessary. DHCP daemons have a tendency to
suddenly start running after software upgrades, usually since someone
forgot the disabling patch...
Cheers,
Patrik
1252
days inactive
1254
days old
7 comments
3 participants
participants (3)
-
Carl D. Blake -
Jose Blanquicet -
Patrik Flykt