It looks like bluetooth PAN does work under Networkmanager. This is a bit confusing as in the past, the DUN profile was used by Networkmanager to initiate a network connection through the phone. My proposed fix is to make a USE flag to enable or disable this functionality - I would like at some point to also allow DUN profiles if NM will eventually reintegrate it, but for now, PAN works.
My test build I added a "bluez4" IUSE in my test ebuild, and used a $(use_enable bluez4) instead of hardcoding --enable-bluez4 - which is kind of weird why it should be hardcoded with --enable-bluez4 as bluez5 tends to be installed for other reasons.
Perhaps the better solution is to detect whether bluez4 or bluez5 is installed and use whichever bluez is available; this would be a bit more involved unfortunately and may be easier just to put the bluez4 USE flag in.
Steps to Reproduce:
1. Enable bnep bluetooth network in kernel.
2. Run Networkmanager/nm-tool in Gnome with a paired, PAN enabled cellular phone nearby
No PAN available.
Should be able to detect PAN and offer networking through PAN
0.9.10.1_pre20141101 enables DUN with the bluetooth USE flag
(In reply to Pacho Ramos from comment #1)
> 0.9.10.1_pre20141101 enables DUN with the bluetooth USE flag
Does this mean that PAN requires the bluetooth use flag to be unset? (I can't get a PAN device to show up; I have bluetooth as a global use flag.)
I should have marked this as verified/fixed as recent versions of NM have PAN enabled as expected. I just recently looked at the ebuild and it still looks a little wonky to me but does its job (forcing people to use bluez5, but that's ok I suppose, then again not sure if the NM devs are enforcing that anyway).
You do need USE=bluetooth to enable PAN.
I don't know about the status of bluetooth-DUN however; I haven't been able to use it since bluez4.