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:
NM has full support for Bluetooth DUN and PAN now: http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/ try it that way. Just pair from the PC to the phone, it should show a checkbox for 'internet connection sharing' on the last step, check that, and NM should then be able to dial up via your phone.
Thanks Adam, I spent some more time on this today and I did get it to work when initiating a connection via NM. The buggy part I have found though is that if the device initiates the connection - it is ignored completely. When using the Internet Sharing application on most Windows Mobile phones, you are requested to pick the device from the phone you wish to connect to - this adds security - as you are not just offering the service and accepting anyone that hooks up. This is where the bug occurs - as bnep0 does come up and I can see it with in the shell via ifconfig etc - but NM does not have a clue that it has started.
Okay, gotcha. This is essentially a feature request, then. Editing summary appropriately. Dan, can you look into this case? I know you may have a bit of trouble with access to an appropriate device, though...I have one which does much the same as Steven's (I believe I've actually mentioned this case to you before, though I didn't get the rationale as Steven explains, which makes much more sense of it), so I can probably get you any info needed if you ping me on IRC.
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
What kind of WinMo phone do you have? And what happens when the pairing process is compelete from the bluetooth applet? Does NetworkManager give you any indication of internet access through the phone?
We don't support PAN or DUN when pairing is initiated from the device itself, or when the service is enabled after pairing. This is a problem in gnome-bluetooth's UI, rather than a problem in NetworkManager. gnome-bluetooth needs to have a properties window for paired devices, which would list the plugins available for that device type, as well as the ability to update services offered by the device.
(In reply to comment #6) > We don't support PAN or DUN when pairing is initiated from the device itself, > or when the service is enabled after pairing. > > This is a problem in gnome-bluetooth's UI, rather than a problem in > NetworkManager. gnome-bluetooth needs to have a properties window for paired > devices, which would list the plugins available for that device type, as well > as the ability to update services offered by the device. Scratch that, your problem doesn't have anything to do with that.
Well, IMHO there are multiple issues at play here. 1) NetworkManager has no clue what to do with an incoming PAN request. It sees the connection come up and says "wtf, ignore". Ideally, NM should try to grab a DHCP address then fail back to "wtf, ignore". This would really solve my problem in one step. 2) To make gnome a more useful place, then yes, gnome-bluetooth needs the capacity to edit bluetooth pairings and get some kind of information from the paired device without deleting and repairing. It is basic functionality - but at the moment it is missing.
filed upstream as https://bugzilla.gnome.org/show_bug.cgi?id=675677