On 10/23/2014 05:27 AM, Patrik Flykt wrote:
A commit message shedding some light on what this patch tries to do is
quite necessary. PANU support is already there, so is this patch about
connecting to a GN instead of a NAP? If this is about tethering, there
is not much point in announcing a GN when one can do NAP.
It is about connecting to GN instead of NAP. I wanted to connect to my
MacBook via Bluetooth, but it turns out that it provides the GN role.
From
<https://www.bluetooth.org/en-us/specification/assigned-numbers/service-discovery>,
PAN has 3 roles...
PANU 0x1115 Personal Area Networking Profile (PAN)
NOTE: Used as both Service Class Identifier and Profile Identifier for
PANU role. Service Class / Profile
NAP 0x1116 Personal Area Networking Profile (PAN)
NOTE: Used as both Service Class Identifier and Profile Identifier for
NAP role. Service Class / Profile
GN 0x1117 Personal Area Networking Profile (PAN)
NOTE: Used as both Service Class Identifier and Profile Identifier for
GN role. Service Class / Profile
The org.bluez.Network1 interface has support for all three, but connman
currently ignores all but NAP. There doesn't seem any reason not to be
able to connect to all three.
With this patch, I am able to connect to my MacBook. I also have an
Android phone that provides the NAP role, so I have been able to confirm
that I did not break NAP. I don't have any devices that use the PANU
role though, so I haven't been able to test that.
If the patch looks OK other than the commit message, I will fix it and
resubmit.
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
