Bluez PAN profile does not support the Group Network scenario

Bug #1547556 reported by Jon Hoffman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I can configure and set up a Bluetooth PAN using the NAP scenario however we would like to use the GN (Group Network) scenario working. It does not appear that Bluez properly supports this in the PAN profile. I have been able to recreate the problem with three bluetooth devices (broadcomm BCM20702, Realtek RTL8723 and a Cambridge Silicon Radio Bluetooth dongle), two Bluez versions (5.35 and 5.23) and the stock kernel that comes with Ubuntu 15.10 and also a custom 4.4 kernel that I built. I have also attempted to connect several devices (Raspberry Pi, another Ubuntu computer, iOS device and Windows 10 device) and they all have the same issue

The expected behavior is when we configure the PAN profile to function in the Group Network scenario that other devices will be able to connect like the NAP scenario. Once the connection is made the two devices will be able to communicate with IPv4 and IPv6. What is happening is the NAP scenario the connection works as expected but when we use the GN scenario the connection is not established.

I have had several e-mails on the Bluez user list where it was confirmed that at least one other individual has the same issue. I have also see the issue mentioned on blogs and stackoverflow questions. As an example this blog (see the end of the post): http://blog.fraggod.net/2015/03/28/bluetooth-pan-network-setup-with-bluez-5x.html
and this stackoverflow question: http://stackoverflow.com/questions/32520581/bluez-pan-gn-server-connection-refused-when-nap-server-is-down

Rather than putting information about the various configurations that I used and the results from my hcidumps I am providing links to the e-mails in the bluez mailing list with all of the information (I a liable to forget something if I try to put it all in here). I hope it is alright to provide links rather than the detailed information. Here are the links:

http://marc.info/?l=linux-bluetooth&m=145504188107174&w=2
http://marc.info/?l=linux-bluetooth&m=145511143325928&w=2
http://marc.info/?l=linux-bluetooth&m=145519999122671&w=2
http://marc.info/?l=linux-bluetooth&m=145529283519026&w=2
http://marc.info/?l=linux-bluetooth&m=145530430223540&w=2
http://marc.info/?l=linux-bluetooth&m=145555004005066&w=2
http://marc.info/?l=linux-bluetooth&m=145582072316051&w=2

Thanks,

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Please upgrade to the latest version and re-test.

Changed in bluez (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

Changed in bluez (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.