After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 612871 - NM doesn't handle bluetooth bnep0 interface
NM doesn't handle bluetooth bnep0 interface
Status: RESOLVED DUPLICATE of bug 613598
Product: NetworkManager
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2010-03-14 15:06 UTC by abyss.7
Modified: 2010-04-04 21:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description abyss.7 2010-03-14 15:06:14 UTC
The NetworkManager - as it is for now (14/03/10) - doesn't handle the bnep0 interface. The interface is created by bluez-4.61 daemon. It emulates the ethernet connection between my desktop PC (linux) and my notebook (winxp).

The following message can be found in the logs after a bluetooth connection:

>>>>>>>>>>>>
Mar 14 17:48:39 [dbus-daemon] Reloaded configuration
                - Last output repeated twice -
Mar 14 17:48:51 [bluetoothd] link_key_request (sba=00:15:83:19:B3:42, dba=00:11:67:CC:19:B8)
Mar 14 17:48:52 [bluetoothd] Added new connection: bnep0
Mar 14 17:48:52 [NetworkManager] <WARN>  device_creator(): /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-5/2-5.1/2-5.1:1.0/bluetooth/hci0/hci0:42/bnep0: couldn't determine device driver; ignoring..._
<<<<<<<<<<<<

Steps to reproduce:
1) Linux: start bluetoothd daemon.
2) WinXP: connect to my desktop PC via PAN service.

Actual results:
NetworkManager-applet shows nothing about the new interface.

Expected results:
NetworkManager-applet shows the new interface and allows to create manual or automatic connections via it.
Comment 1 Dan Williams 2010-04-04 21:11:30 UTC
We'll track this one in the duplicate; essentially add support for NAP connection sharing so other devices can connect to your computer.

*** This bug has been marked as a duplicate of bug 613598 ***