| Summary: | Bluetooth wizard should register GSM modem to network-manager | ||
|---|---|---|---|
| Product: | [Unmaintained] solid | Reporter: | Ferry <ferry.toth> |
| Component: | bluetooth-wizard | Assignee: | Alex Fiestas <afiestas> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | bjoernv, darkbasic4, froller, lamarque, sling-shot, wrar, wstephenson |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Ferry
2010-12-25 01:00:08 UTC
Now the only option is to use gnome-bluetooth AND network-manager-gnome. Bluedevil doesn't have any DUN support and only nm-applet provides a gnome-bluetooth plugin (which in turn knows only about nm-applet). Hi This is planned for the next version of NetworManagement, so we'll have this feature soon enough :p Thanks for the wish. Is there any experimental support in bluedevil git/knetworkmanager git? This bluetooth modem thing is very weird.
1. If I do this as root (or normal user) with my cellphone:
evolucao # dbus-send --system --print-reply --dest=org.bluez
/org/bluez/25735/hci0/dev_<cell phone bluetooth MAC> org.bluez.Serial.Connect
string:dun
method return sender=:1.119 -> dest=:1.245 reply_serial=2
string "/dev/rfcomm0"
The entry /dev/rfcomm0 is not created although the reply says it should have
been created.
2. If I use qdbusviewer as normal user it creates the /dev/rfcomm0 entry and it
works with wvdial but ModemManager ignores /dev/rfcomm0 with no message in
/var/log/messages, just ignores.
3. If I do this as root:
INFO=$(LC_ALL=C sdptool search DUN | awk '/Searching for DUN on / { print $5 }
/Channel:/ { print " "$NF }')
MAC=$(echo $INFO | awk '{ print $1 }')
CHANNEL=$(echo $INFO | awk '{ print $2 }')
mknod --mode=666 /dev/rfcomm0 c 216 0
rfcomm connect 0 $MAC $CHANNEL
It works with both wvdial and ModemManager, and conseguently with Plasma NM. I
can connect with my cellphone and browse the Internet normally. The last weird
thing is that even though everything is working ModemManager does not get the
access technology used, Edge in this case.
*** Bug 266539 has been marked as a duplicate of this bug. *** *** Bug 270965 has been marked as a duplicate of this bug. *** Git commit ada07c830485fcda17d12c90d38f1b9f8b06a584 by Lamarque V. Souza. Committed on 24/04/2011 at 06:01. Pushed by lvsouza into branch 'master'. Updates for bluetooth tethering support. Full support only in KDE SC 4.7.0 because Plasma NM needs Solid 4.7.0 to detect bluetooth network interfaces. In the mean time Plasma NM will treat bluetooth network interfaces as gsm network interfaces. I still need to implement bluetooth tethering for Cdma phones and Gsm/Cdma) Panu. Without Solid 4.7.0 Plasma NM will not list the bluetooth interface nor the bluetooth connection, so the only way to connect is setting the bluetooth connection to autoconnect. There will be no notifications from knotify either without Solid 4.7.0 and of course interface details tab will not work because the interface is not listed. BUG: 203584 CCBUG: 261191 FIXED-IN: 4.7.0 M +28 -7 applet/interfacedetailswidget.cpp M +4 -2 applet/nmpopup.cpp M +3 -0 backends/NetworkManager/remoteconnection.cpp M +2 -1 kded/service.cpp M +4 -0 libs/internals/uiutils.cpp M +9 -3 libs/service/gsmnetworkinterfaceactivatableprovider.cpp M +3 -0 libs/service/networkinterfaceactivatableprovider.cpp M +4 -1 libs/service/networkinterfacemonitor.cpp http://commits.kde.org/networkmanagement/ada07c830485fcda17d12c90d38f1b9f8b06a584 Soon Bluedevil will be updated to automatically call the wizard. Until then you can use networkmanagement_configshell command to register a bluetooth DUN (dial-up network) connection using the steps in here: http://lamarque-lvs.blogspot.com/2011/04/plasma-nm-bluetooth-tethering.html This is done now since BlueDevil 1.2 and NetworkManagement 0.9-beta Thanks for reporting and giving feedback ! |