Re: GSM modem via Bluetooth?
On Tue, 2011-01-11 at 17:49 +, Bastien Nocera wrote: > On Thu, 2011-01-06 at 13:16 -0600, Dan Williams wrote: > > > I spend some time on this over the holidays to figure out what it would > > take for manually started rfcomm ports to show up as Bluetooth modems > > and be configurable without the BT wizard. > > You'll still need to pair the device at some point anyway. > > > The short answer is that > > yes, this is possible, though it's somewhat icky. But even if NM > > exported the device as a Bluetooth modem, you'll still need connection > > details (APN, username, password) before you can ask NM to connect the > > device. > > Exactly. > > > I'll look into further cleaning up the proof-of-concept patches I did > > and see if they can be merged in some form in the near future. > > I think that this is probably best left alone until someone implements > Bluetooth line discipline in pppd and the Linux kernel directly, so that > reliance on rfcomm, or creation of "serial ports" through bluetoothd is > unneeded. > > If you want to be able to use the /dev/rfcomm devices directly, I'd > recommend making this "hard" to setup, so that people don't try and use > it as the main way to create a connection to their device, rather as a > debugging method (wrong Bluetooth port used for example). > > Creating an rfcomm device, making sure it stays across reboots, and > making sure it points to the right port (which has absolutely no > guarantees of staying the same across enabling/disabling the feature on > the device), is a sure way to break things, and requires root access. It's more for KDE, which doesn't have a bluetooth wizard that does the same thing as the Gnome applet. Ideally, KDE should get that functionality, but making already-paired-but-unconfigured devices show up as NM bluetooth devices would let the kde bits at least configure the device. I don't think it's very useful to have a raw rfcomm port show up as non-bluetooth device though (ie, a USB 3G stick) because then you have to start up the rfcomm port every single time manually. That sucks, and the real fix there is to either (1) get a bluetooth wizard if you don't have one, or (2) modify the applet you're using to be able to create new BT DUN configs if NM presents the device. The patches I did would do #2, which could also be useful in Gnome if you didn't check the boxes at the end of pairing for some reason. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: GSM modem via Bluetooth?
On Tue, 2011-01-11 at 20:36 +0300, Andrey Borzenkov wrote: > On Thu, Jan 6, 2011 at 10:16 PM, Dan Williams wrote: > > > > I spend some time on this over the holidays to figure out what it would > > take for manually started rfcomm ports to show up as Bluetooth modems > > and be configurable without the BT wizard. The short answer is that > > yes, this is possible, though it's somewhat icky. But even if NM > > exported the device as a Bluetooth modem, you'll still need connection > > details (APN, username, password) before you can ask NM to connect the > > device. > > > > That's correct; and as soon as connection was no more ignored by NM I > was able to use knetworkmanager to configure it. So now I have fully > functional connection definition. I'm guessing it would be easier to setup once NM takes care of creating connections in a way that doesn't require a particular backing store. So you'd set it up using the GNOME Bluetooth wizard, and have access to the same connection in KNetworkManager (or at least until the KDE Bluetooth bits gain the ability to do something similar). Cheers ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: GSM modem via Bluetooth?
On Thu, 2011-01-06 at 13:16 -0600, Dan Williams wrote: > I spend some time on this over the holidays to figure out what it would > take for manually started rfcomm ports to show up as Bluetooth modems > and be configurable without the BT wizard. You'll still need to pair the device at some point anyway. > The short answer is that > yes, this is possible, though it's somewhat icky. But even if NM > exported the device as a Bluetooth modem, you'll still need connection > details (APN, username, password) before you can ask NM to connect the > device. Exactly. > I'll look into further cleaning up the proof-of-concept patches I did > and see if they can be merged in some form in the near future. I think that this is probably best left alone until someone implements Bluetooth line discipline in pppd and the Linux kernel directly, so that reliance on rfcomm, or creation of "serial ports" through bluetoothd is unneeded. If you want to be able to use the /dev/rfcomm devices directly, I'd recommend making this "hard" to setup, so that people don't try and use it as the main way to create a connection to their device, rather as a debugging method (wrong Bluetooth port used for example). Creating an rfcomm device, making sure it stays across reboots, and making sure it points to the right port (which has absolutely no guarantees of staying the same across enabling/disabling the feature on the device), is a sure way to break things, and requires root access. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: GSM modem via Bluetooth?
On Thu, Jan 6, 2011 at 10:16 PM, Dan Williams wrote: > > I spend some time on this over the holidays to figure out what it would > take for manually started rfcomm ports to show up as Bluetooth modems > and be configurable without the BT wizard. The short answer is that > yes, this is possible, though it's somewhat icky. But even if NM > exported the device as a Bluetooth modem, you'll still need connection > details (APN, username, password) before you can ask NM to connect the > device. > That's correct; and as soon as connection was no more ignored by NM I was able to use knetworkmanager to configure it. So now I have fully functional connection definition. > I'll look into further cleaning up the proof-of-concept patches I did > and see if they can be merged in some form in the near future. > Thank you! ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: GSM modem via Bluetooth?
On Wed, 2010-11-24 at 09:06 +0300, Andrey Borzenkov wrote:
> On Wed, Nov 24, 2010 at 6:55 AM, Dan Williams wrote:
> > On Sat, 2010-11-20 at 23:28 +0300, Andrey Borzenkov wrote:
> >> On Sat, Nov 20, 2010 at 1:24 AM, Dan Williams wrote:
> >> > On Thu, 2010-11-04 at 15:33 +0300, Andrey Borzenkov wrote:
> >> >> I have Nokia E51 and am using KDE with bluedevil; Modemmanager 0.4 and
> >> >> NM 0.8.2-rc1. I can browse phone and transfer files, but modemmanager
> >> >> does not display any available device when BT is activated. Is it
> >> >> supposed to work at all and if yes, what is requires to get it
> >> >> working? Pointers to documentation is appreciated. Thank you!
> >> >
> >> > Getting this working first requires adding a "connection" for the
> >> > device, since we can't scan for it. Once the connection is added and
> >> > known to NM, it'll show up in the menu and you can choose it. While it
> >> > doesn't help you immediately with bluedevil, this is how we did the
> >> > gnome side of things:
> >> >
> >> > http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/
> >> >
> >>
> >> Yes, I know this but it does not really help to make it running using
> >> "Bordmittel".
> >>
> >> OK, I have phone that exports DUN:
> >>
> >> {pts/1}% sdptool search DUN
> >> Inquiring ...
> >> Searching for DUN on 00:24:03:BE:1A:29 ...
> >> Service Name: Dial-Up Networking
> >> Service RecHandle: 0x100c5
> >> Service Class ID List:
> >> "Dialup Networking" (0x1103)
> >> Protocol Descriptor List:
> >> "L2CAP" (0x0100)
> >> "RFCOMM" (0x0003)
> >> Channel: 4
> >> Language Base Attr List:
> >> code_ISO639: 0x454e
> >> encoding:0x6a
> >> base_offset: 0x100
> >> Profile Descriptor List:
> >> "Dialup Networking" (0x1103)
> >> Version: 0x0100
> >>
> >> As I understand, I need serial port that is used by ModemManager. I
> >> now create serial port for the phone:
> >>
> >> {pts/0}% sudo rfcomm bind 00:24:03:BE:1A:29 4
> >> {pts/0}% ll /dev/rfcomm0
> >> crw-rw 1 root dialout 216, 0 Ноя 20 23:22 /dev/rfcomm0
> >>
> >> But this port is ignored by ModemManager:
> >>
> >> {pts/0}% dbus-send --print-reply --system
> >> --dest=org.freedesktop.ModemManager /org/freedesktop/ModemManager
> >> org.freedesktop.ModemManager.EnumerateDevices
> >> method return sender=:1.10 -> dest=:1.315 reply_serial=2
> >>array [
> >>]
> >>
> >> So what is missing in this case? Thank you!
> >
> > You don't actually need to create the rfcomm port yourself. NM will
> > create that on-the-fly when starting up DUN for the device. Since we
> > cannot scan for devices with Bluetooth (takes way too long and
> > interrupts existing connections) NM requires that a 'connection' already
> > be defined for a phone before you can use it; that connection stores
> > various config we want to know before connecting (like the BT address!).
> >
>
> Yes, that was the missing bit; it is not documented anywhere clear
> that such connection is required.
>
> > Here's how it works for GNOME desktops:
> >
>
> And for those who do not use Gnome?
>
> Anyway, I had to use "rfcomm connect", not "rfcomm bind"; rfcomm
> connect creates BT connection to phone that is happily recognized by
> MM now and exported for NM use. But now NM was ignoring it :)
>
> For testing I commented out the bits
> /* If it was a Bluetooth modem and no bluetooth device claimed
> it, ignore
> * it. The rfcomm port (and thus the modem) gets created
> automatically
> * by the Bluetooth code during the connection process.
> */
>
> if (driver && !strcmp (driver, "bluetooth")) {
> nm_log_info (LOGD_MB, "ignoring modem '%s' (no
> associated Bluetooth device)", ip_iface);
> return;
> }
>
> and was able to finally connect without any obvious problems.
>
> What is the reason for this "ignorance" :) ? If I understand
> correctly, we are ignoring rfcomm because we are going to create it
> ourselves. But by this logic if there is no pre-existing connection,
> we will *not* create any rcomm in the first place. And if any
> connection was defined for it, it would have claimed device before and
> we would not reach this place at all. So if we are here, we see serial
> connection to BT modem ready for us; why not let user to just use it?
I spend some time on this over the holidays to figure out what it would
take for manually started rfcomm ports to show up as Bluetooth modems
and be configurable without the BT wizard. The short answer is that
yes, this is possible, though it's somewhat icky. But even if NM
exported the device as a Bluetooth modem, you'll still need connection
details (APN, username, password) before you can ask NM to connect the
device.
I'll look into further cleaning up the proof-of-concept patches I did
and see if they can be merged in some form in the near future.
Dan
___
networkmanager-list mailing list
networkmanager-l
Re: GSM modem via Bluetooth?
Op woensdag 24-11-2010 om 09:06 uur [tijdzone +0300], schreef Andrey
Borzenkov:
> On Wed, Nov 24, 2010 at 6:55 AM, Dan Williams wrote:
> > On Sat, 2010-11-20 at 23:28 +0300, Andrey Borzenkov wrote:
> >> On Sat, Nov 20, 2010 at 1:24 AM, Dan Williams wrote:
> >> > On Thu, 2010-11-04 at 15:33 +0300, Andrey Borzenkov wrote:
> >> >> I have Nokia E51 and am using KDE with bluedevil; Modemmanager 0.4 and
> >> >> NM 0.8.2-rc1. I can browse phone and transfer files, but modemmanager
> >> >> does not display any available device when BT is activated. Is it
> >> >> supposed to work at all and if yes, what is requires to get it
> >> >> working? Pointers to documentation is appreciated. Thank you!
> >> >
> >> > Getting this working first requires adding a "connection" for the
> >> > device, since we can't scan for it. Once the connection is added and
> >> > known to NM, it'll show up in the menu and you can choose it. While it
> >> > doesn't help you immediately with bluedevil, this is how we did the
> >> > gnome side of things:
> >> >
> >> > http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/
> >> >
> >>
> >> Yes, I know this but it does not really help to make it running using
> >> "Bordmittel".
> >>
> >> OK, I have phone that exports DUN:
> >>
> >> {pts/1}% sdptool search DUN
> >> Inquiring ...
> >> Searching for DUN on 00:24:03:BE:1A:29 ...
> >> Service Name: Dial-Up Networking
> >> Service RecHandle: 0x100c5
> >> Service Class ID List:
> >> "Dialup Networking" (0x1103)
> >> Protocol Descriptor List:
> >> "L2CAP" (0x0100)
> >> "RFCOMM" (0x0003)
> >> Channel: 4
> >> Language Base Attr List:
> >> code_ISO639: 0x454e
> >> encoding:0x6a
> >> base_offset: 0x100
> >> Profile Descriptor List:
> >> "Dialup Networking" (0x1103)
> >> Version: 0x0100
> >>
> >> As I understand, I need serial port that is used by ModemManager. I
> >> now create serial port for the phone:
> >>
> >> {pts/0}% sudo rfcomm bind 00:24:03:BE:1A:29 4
> >> {pts/0}% ll /dev/rfcomm0
> >> crw-rw 1 root dialout 216, 0 Ноя 20 23:22 /dev/rfcomm0
> >>
> >> But this port is ignored by ModemManager:
> >>
> >> {pts/0}% dbus-send --print-reply --system
> >> --dest=org.freedesktop.ModemManager /org/freedesktop/ModemManager
> >> org.freedesktop.ModemManager.EnumerateDevices
> >> method return sender=:1.10 -> dest=:1.315 reply_serial=2
> >>array [
> >>]
> >>
> >> So what is missing in this case? Thank you!
> >
> > You don't actually need to create the rfcomm port yourself. NM will
> > create that on-the-fly when starting up DUN for the device. Since we
> > cannot scan for devices with Bluetooth (takes way too long and
> > interrupts existing connections) NM requires that a 'connection' already
> > be defined for a phone before you can use it; that connection stores
> > various config we want to know before connecting (like the BT address!).
> >
>
> Yes, that was the missing bit; it is not documented anywhere clear
> that such connection is required.
>
> > Here's how it works for GNOME desktops:
> >
>
> And for those who do not use Gnome?
I have the same problem. How do I get a connection in Kubuntu?
Installing gnome-bluetooth and following Dan's blog I don't get the
'Access the Internet using your mobile phone' checkbox.
What now?
Ferry
> Anyway, I had to use "rfcomm connect", not "rfcomm bind"; rfcomm
> connect creates BT connection to phone that is happily recognized by
> MM now and exported for NM use. But now NM was ignoring it :)
>
> For testing I commented out the bits
> /* If it was a Bluetooth modem and no bluetooth device claimed
> it, ignore
> * it. The rfcomm port (and thus the modem) gets created
> automatically
> * by the Bluetooth code during the connection process.
> */
>
> if (driver && !strcmp (driver, "bluetooth")) {
> nm_log_info (LOGD_MB, "ignoring modem '%s' (no
> associated Bluetooth device)", ip_iface);
> return;
> }
>
> and was able to finally connect without any obvious problems.
>
> What is the reason for this "ignorance" :) ? If I understand
> correctly, we are ignoring rfcomm because we are going to create it
> ourselves. But by this logic if there is no pre-existing connection,
> we will *not* create any rcomm in the first place. And if any
> connection was defined for it, it would have claimed device before and
> we would not reach this place at all. So if we are here, we see serial
> connection to BT modem ready for us; why not let user to just use it?
> ___
> networkmanager-list mailing list
> networkmanager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: GSM modem via Bluetooth?
On Wed, Nov 24, 2010 at 6:55 AM, Dan Williams wrote:
> On Sat, 2010-11-20 at 23:28 +0300, Andrey Borzenkov wrote:
>> On Sat, Nov 20, 2010 at 1:24 AM, Dan Williams wrote:
>> > On Thu, 2010-11-04 at 15:33 +0300, Andrey Borzenkov wrote:
>> >> I have Nokia E51 and am using KDE with bluedevil; Modemmanager 0.4 and
>> >> NM 0.8.2-rc1. I can browse phone and transfer files, but modemmanager
>> >> does not display any available device when BT is activated. Is it
>> >> supposed to work at all and if yes, what is requires to get it
>> >> working? Pointers to documentation is appreciated. Thank you!
>> >
>> > Getting this working first requires adding a "connection" for the
>> > device, since we can't scan for it. Once the connection is added and
>> > known to NM, it'll show up in the menu and you can choose it. While it
>> > doesn't help you immediately with bluedevil, this is how we did the
>> > gnome side of things:
>> >
>> > http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/
>> >
>>
>> Yes, I know this but it does not really help to make it running using
>> "Bordmittel".
>>
>> OK, I have phone that exports DUN:
>>
>> {pts/1}% sdptool search DUN
>> Inquiring ...
>> Searching for DUN on 00:24:03:BE:1A:29 ...
>> Service Name: Dial-Up Networking
>> Service RecHandle: 0x100c5
>> Service Class ID List:
>> "Dialup Networking" (0x1103)
>> Protocol Descriptor List:
>> "L2CAP" (0x0100)
>> "RFCOMM" (0x0003)
>> Channel: 4
>> Language Base Attr List:
>> code_ISO639: 0x454e
>> encoding: 0x6a
>> base_offset: 0x100
>> Profile Descriptor List:
>> "Dialup Networking" (0x1103)
>> Version: 0x0100
>>
>> As I understand, I need serial port that is used by ModemManager. I
>> now create serial port for the phone:
>>
>> {pts/0}% sudo rfcomm bind 00:24:03:BE:1A:29 4
>> {pts/0}% ll /dev/rfcomm0
>> crw-rw 1 root dialout 216, 0 Ноя 20 23:22 /dev/rfcomm0
>>
>> But this port is ignored by ModemManager:
>>
>> {pts/0}% dbus-send --print-reply --system
>> --dest=org.freedesktop.ModemManager /org/freedesktop/ModemManager
>> org.freedesktop.ModemManager.EnumerateDevices
>> method return sender=:1.10 -> dest=:1.315 reply_serial=2
>> array [
>> ]
>>
>> So what is missing in this case? Thank you!
>
> You don't actually need to create the rfcomm port yourself. NM will
> create that on-the-fly when starting up DUN for the device. Since we
> cannot scan for devices with Bluetooth (takes way too long and
> interrupts existing connections) NM requires that a 'connection' already
> be defined for a phone before you can use it; that connection stores
> various config we want to know before connecting (like the BT address!).
>
Yes, that was the missing bit; it is not documented anywhere clear
that such connection is required.
> Here's how it works for GNOME desktops:
>
And for those who do not use Gnome?
Anyway, I had to use "rfcomm connect", not "rfcomm bind"; rfcomm
connect creates BT connection to phone that is happily recognized by
MM now and exported for NM use. But now NM was ignoring it :)
For testing I commented out the bits
/* If it was a Bluetooth modem and no bluetooth device claimed
it, ignore
* it. The rfcomm port (and thus the modem) gets created automatically
* by the Bluetooth code during the connection process.
*/
if (driver && !strcmp (driver, "bluetooth")) {
nm_log_info (LOGD_MB, "ignoring modem '%s' (no
associated Bluetooth device)", ip_iface);
return;
}
and was able to finally connect without any obvious problems.
What is the reason for this "ignorance" :) ? If I understand
correctly, we are ignoring rfcomm because we are going to create it
ourselves. But by this logic if there is no pre-existing connection,
we will *not* create any rcomm in the first place. And if any
connection was defined for it, it would have claimed device before and
we would not reach this place at all. So if we are here, we see serial
connection to BT modem ready for us; why not let user to just use it?
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: GSM modem via Bluetooth?
On Sat, 2010-11-20 at 23:28 +0300, Andrey Borzenkov wrote:
> On Sat, Nov 20, 2010 at 1:24 AM, Dan Williams wrote:
> > On Thu, 2010-11-04 at 15:33 +0300, Andrey Borzenkov wrote:
> >> I have Nokia E51 and am using KDE with bluedevil; Modemmanager 0.4 and
> >> NM 0.8.2-rc1. I can browse phone and transfer files, but modemmanager
> >> does not display any available device when BT is activated. Is it
> >> supposed to work at all and if yes, what is requires to get it
> >> working? Pointers to documentation is appreciated. Thank you!
> >
> > Getting this working first requires adding a "connection" for the
> > device, since we can't scan for it. Once the connection is added and
> > known to NM, it'll show up in the menu and you can choose it. While it
> > doesn't help you immediately with bluedevil, this is how we did the
> > gnome side of things:
> >
> > http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/
> >
>
> Yes, I know this but it does not really help to make it running using
> "Bordmittel".
>
> OK, I have phone that exports DUN:
>
> {pts/1}% sdptool search DUN
> Inquiring ...
> Searching for DUN on 00:24:03:BE:1A:29 ...
> Service Name: Dial-Up Networking
> Service RecHandle: 0x100c5
> Service Class ID List:
> "Dialup Networking" (0x1103)
> Protocol Descriptor List:
> "L2CAP" (0x0100)
> "RFCOMM" (0x0003)
> Channel: 4
> Language Base Attr List:
> code_ISO639: 0x454e
> encoding:0x6a
> base_offset: 0x100
> Profile Descriptor List:
> "Dialup Networking" (0x1103)
> Version: 0x0100
>
> As I understand, I need serial port that is used by ModemManager. I
> now create serial port for the phone:
>
> {pts/0}% sudo rfcomm bind 00:24:03:BE:1A:29 4
> {pts/0}% ll /dev/rfcomm0
> crw-rw 1 root dialout 216, 0 Ноя 20 23:22 /dev/rfcomm0
>
> But this port is ignored by ModemManager:
>
> {pts/0}% dbus-send --print-reply --system
> --dest=org.freedesktop.ModemManager /org/freedesktop/ModemManager
> org.freedesktop.ModemManager.EnumerateDevices
> method return sender=:1.10 -> dest=:1.315 reply_serial=2
>array [
>]
>
> So what is missing in this case? Thank you!
You don't actually need to create the rfcomm port yourself. NM will
create that on-the-fly when starting up DUN for the device. Since we
cannot scan for devices with Bluetooth (takes way too long and
interrupts existing connections) NM requires that a 'connection' already
be defined for a phone before you can use it; that connection stores
various config we want to know before connecting (like the BT address!).
Here's how it works for GNOME desktops:
http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/
Dan
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [OT] Re: GSM modem via Bluetooth?
On Mon, 2010-11-22 at 17:57 +, Sergio Monteiro Basto wrote: > On Fri, 2010-11-19 at 16:24 -0600, Dan Williams wrote: > > On Thu, 2010-11-04 at 15:33 +0300, Andrey Borzenkov wrote: > > > I have Nokia E51 and am using KDE with bluedevil; Modemmanager 0.4 and > > > NM 0.8.2-rc1. I can browse phone and transfer files, but modemmanager > > > does not display any available device when BT is activated. Is it > > > supposed to work at all and if yes, what is requires to get it > > > working? Pointers to documentation is appreciated. Thank you! > > > > Getting this working first requires adding a "connection" for the > > device, since we can't scan for it. Once the connection is added and > > known to NM, it'll show up in the menu and you can choose it. While it > > doesn't help you immediately with bluedevil, this is how we did the > > gnome side of things: > > > > http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/ > > > > > Hi , Off-Topic , I have an android , which have wifi but Androids can't > connect to ad-hoc hotspot, > (http://code.google.com/p/android/issues/detail?id=82) > > if it is possible do the opposite, android gets internet by connect > bluetooth to laptop , or some other solution where laptop has the > internet . or http://magazine.redhat.com/2008/10/16/video-fedora-10-connection-sharing/ when do a connection sharing do a sharing connection as an AP instead an ad-hoc ? Thanks, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[OT] Re: GSM modem via Bluetooth?
On Fri, 2010-11-19 at 16:24 -0600, Dan Williams wrote: > On Thu, 2010-11-04 at 15:33 +0300, Andrey Borzenkov wrote: > > I have Nokia E51 and am using KDE with bluedevil; Modemmanager 0.4 and > > NM 0.8.2-rc1. I can browse phone and transfer files, but modemmanager > > does not display any available device when BT is activated. Is it > > supposed to work at all and if yes, what is requires to get it > > working? Pointers to documentation is appreciated. Thank you! > > Getting this working first requires adding a "connection" for the > device, since we can't scan for it. Once the connection is added and > known to NM, it'll show up in the menu and you can choose it. While it > doesn't help you immediately with bluedevil, this is how we did the > gnome side of things: > > http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/ > Hi , Off-Topic , I have an android , which have wifi but Androids can't connect to ad-hoc hotspot, (http://code.google.com/p/android/issues/detail?id=82) if it is possible do the opposite, android gets internet by connect bluetooth to laptop , or some other solution where laptop has the internet . -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: GSM modem via Bluetooth?
On Sat, Nov 20, 2010 at 1:24 AM, Dan Williams wrote:
> On Thu, 2010-11-04 at 15:33 +0300, Andrey Borzenkov wrote:
>> I have Nokia E51 and am using KDE with bluedevil; Modemmanager 0.4 and
>> NM 0.8.2-rc1. I can browse phone and transfer files, but modemmanager
>> does not display any available device when BT is activated. Is it
>> supposed to work at all and if yes, what is requires to get it
>> working? Pointers to documentation is appreciated. Thank you!
>
> Getting this working first requires adding a "connection" for the
> device, since we can't scan for it. Once the connection is added and
> known to NM, it'll show up in the menu and you can choose it. While it
> doesn't help you immediately with bluedevil, this is how we did the
> gnome side of things:
>
> http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/
>
Yes, I know this but it does not really help to make it running using
"Bordmittel".
OK, I have phone that exports DUN:
{pts/1}% sdptool search DUN
Inquiring ...
Searching for DUN on 00:24:03:BE:1A:29 ...
Service Name: Dial-Up Networking
Service RecHandle: 0x100c5
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4
Language Base Attr List:
code_ISO639: 0x454e
encoding:0x6a
base_offset: 0x100
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
As I understand, I need serial port that is used by ModemManager. I
now create serial port for the phone:
{pts/0}% sudo rfcomm bind 00:24:03:BE:1A:29 4
{pts/0}% ll /dev/rfcomm0
crw-rw 1 root dialout 216, 0 Ноя 20 23:22 /dev/rfcomm0
But this port is ignored by ModemManager:
{pts/0}% dbus-send --print-reply --system
--dest=org.freedesktop.ModemManager /org/freedesktop/ModemManager
org.freedesktop.ModemManager.EnumerateDevices
method return sender=:1.10 -> dest=:1.315 reply_serial=2
array [
]
So what is missing in this case? Thank you!
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: GSM modem via Bluetooth?
On Thu, 2010-11-04 at 15:33 +0300, Andrey Borzenkov wrote: > I have Nokia E51 and am using KDE with bluedevil; Modemmanager 0.4 and > NM 0.8.2-rc1. I can browse phone and transfer files, but modemmanager > does not display any available device when BT is activated. Is it > supposed to work at all and if yes, what is requires to get it > working? Pointers to documentation is appreciated. Thank you! Getting this working first requires adding a "connection" for the device, since we can't scan for it. Once the connection is added and known to NM, it'll show up in the menu and you can choose it. While it doesn't help you immediately with bluedevil, this is how we did the gnome side of things: http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/ Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
GSM modem via Bluetooth?
I have Nokia E51 and am using KDE with bluedevil; Modemmanager 0.4 and NM 0.8.2-rc1. I can browse phone and transfer files, but modemmanager does not display any available device when BT is activated. Is it supposed to work at all and if yes, what is requires to get it working? Pointers to documentation is appreciated. Thank you! -Andrey ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
