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 675677 - handle Bluetooth connections initiated from the remote end
handle Bluetooth connections initiated from the remote end
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: general
git master
Other Linux
: Normal enhancement
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2012-05-08 13:23 UTC by Dan Winship
Modified: 2012-07-26 13:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dan Winship 2012-05-08 13:23:15 UTC
(from https://bugzilla.redhat.com/show_bug.cgi?id=633339)

Steven Haigh 2010-09-13 11:34:25 EDT

Description of problem:
When connecting to my mobile phone using bluetooth & Internet Sharing on my
phone, bnep0 comes up but does not get an IP address via DHCP. Running dhclient
manually makes the connection work - however this should be handled via
NetworkManager.

Version-Release number of selected component (if applicable):
NetworkManager-glib-0.8.1-6.git20100831.fc14.i686
NetworkManager-0.8.1-6.git20100831.fc14.i686
NetworkManager-gnome-0.8.1-6.git20100831.fc14.i686

How reproducible:
Every time.

Steps to Reproduce:
1. Use a HTC Windows Mobile Phone & set up Internet Sharing.
2. Pair PC to phone via bluetooth
3. Connect to PC form phone with Internet Sharing app.
4. run: ifconfig bnep0 - note no IP address assigned.

Actual results:
no IP address on bnep0 interface.

Expected results:
As no interface is configured for bnep0, NetworkManager should see that bnep0
has been created, then run dhclient to get an address via DHCP.

Additional info:

--------

Comment 4 Steven Haigh 2010-09-23 05:06:17 EDT

Interestingly enough - I tried this with F13 + updates-testing.

In /var/log/messages I saw this:

Sep 23 18:58:03 eeepc bluetoothd[1306]: link_key_request
(sba=1C:4B:D6:0C:35:6E, dba=00:23:76:C1:28:5B)
Sep 23 18:58:03 eeepc bluetoothd[1306]: link_key_request
(sba=1C:4B:D6:0C:35:6E, dba=00:23:76:C1:28:5B)
Sep 23 18:58:04 eeepc bluetoothd[1306]: Added new connection: bnep0
Sep 23 18:58:04 eeepc NetworkManager[1121]: <warn>
/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-1/5-1:1.0/bluetooth/hci0/hci0:12/bnep0:
couldn't determine device driver; ignoring...
Sep 23 18:58:05 eeepc avahi-daemon[1130]: Registering new address record for
fe80::1e4b:d6ff:fe0c:356e on bnep0.*.
Sep 23 18:58:07 eeepc ntpd[1326]: Listen normally on 7 bnep0
fe80::1e4b:d6ff:fe0c:356e UDP 123

This means if NetworkManager can be told about the device driver settings to
allow the PAN connection to work, it may be trivial to correct this.

Reconnecting my PAN connection, I looked in the above directory and the file
uevent shows:
DEVTYPE=bluetooth
INTERFACE=bnep0
IFINDEX=7
Comment 1 Pavel Simerda 2012-07-26 13:11:41 UTC
I guess NetworkManager just doesn't know that it should run dhclient?
Comment 2 Pavel Simerda 2012-07-26 13:13:38 UTC
Closing for now, as the original report is pretty old.