Re: manage bluetooth devices using NetworkManger

[Thomas Haller via networkmanager-list]

Hi,

On Mon, 2020-10-05 at 23:29 +0530, NIKHIL PATIL wrote:
> Hi,
>1)  yes. I added networkmanager with bluetooth support.
>  My networkmanager_1.10.6.bbappend file :-
>  PACKAGECONFIG_append = "  bluez5"  
>  
>   Is this fine for bluetooth support or need to be extra in
> networkmanager_1.10.6.bb file ?


Possibly. I am not familiar with yocto or your build setup. What
matters is that you have a file like "libnm-device-plugin-
bluetooth.so", and that the logfile indicates that the bluetooth plugin
is loaded.
 
>2)  default bluez5 (bluetooth package ) is dealing with connman ,
> how we can make so bluez5 will deal with networkmanager  in yocto? 

bluez is a service that provides a (D-Bus based) API for dealing with
bluetooth. Connman and NetworkManager are services that provide an API
for configuring network interfaces, they both may do so by interacting
with bluez. It is Connman/NetworkManager who talks to bluez, not the
other way around. This means, if you want NetworkManager to configure
your bluetooth devices, then do it in NetworkManager (by setting it up
correctly, like having the bluetooth plugin working, and activating a
bluetooth connection profile in NetworkManager). NetworkManager isn't
aware of what other services (connman) you have running.

Not sure what your question is, but of course if you currently have
another layer (like a GUI application) that is based on Connman's API,
then you need to convince that other layer to talk to NetworkManager
instead. Which might not be possible, because most upper layers (GUIs)
either talks to NetworkManager or Connman, not both). In that case, use
a upper layer tool that is on top of NetworkManager instead of Connman.


best,
Thomas



signature.asc
Description: This is a digitally signed message part
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: manage bluetooth devices using NetworkManger

[NIKHIL PATIL via networkmanager-list]

Hi,
   1)  yes. I added networkmanager with bluetooth support.
 My networkmanager_1.10.6.bbappend file :-
 PACKAGECONFIG_append = "  bluez5"

  Is this fine for bluetooth support or need to be extra in
networkmanager_1.10.6.bb file ?

   2)  default bluez5 (bluetooth package ) is dealing with connman , how we
can make so bluez5 will deal with networkmanager  in yocto?

On Mon, Oct 5, 2020 at 8:06 PM Thomas Haller  wrote:

> Hi,
>
> On Mon, 2020-10-05 at 13:11 +0530, NIKHIL PATIL wrote:
> > We are using Redpine module (rsi9113) which support bluetooth +
> > wifi .
> > OS - yocto based linux.
> > NetworkManager version :- 1.10.6
> >
> >1) for WIFI we are able to manage using nmcli commands .
> >-> nmcli device
> >DEVICE TYPE  STATE CONNECTION
> > wlp0s21f0u4wifi   connected    test
> >
> >  2) for bluetooth can we except like these ( bluetooth interface (eg.
> > bnp0)) using nmcli commands .
> >
> >   My  networkmanager_1.10.6.bbappend file :-
> >   PACKAGECONFIG_append = " modemmanager"
> >   PACKAGECONFIG_append = " ppp ifupdown wifi bluez5"
> >
> >I added bluez5 in .bbappend file , i thought it will manage
> > through these , but not happening ,
> >   i think by default bluez5 is dealing with connman ,  how we can
> > switch bluez5 with networkmanager .
>
> 1.10.0 was released almost 3 years ago (and the minor update 1.10.6
> five months after that). If possible, I wouldn't bother with such an
> old version and use something more recent.
>
> Anyway, did you build NetworkManager with bluetooth support enabled?
>
> Under `nmcli device` you would see the paired bluetooth devices (that
> support network related bluetooth profiles).
>
>
> Did you look at the log file?
>
>
> >3) using nmcli commands will show bluetooth device is connected or
> > not ?
>
> nmcli device
> nmcli connection
>
>
>
>
> best,
> Thomas
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: manage bluetooth devices using NetworkManger

[Thomas Haller via networkmanager-list]

Hi,

On Mon, 2020-10-05 at 13:11 +0530, NIKHIL PATIL wrote:
> We are using Redpine module (rsi9113) which support bluetooth +
> wifi . 
> OS - yocto based linux. 
> NetworkManager version :- 1.10.6
> 
>1) for WIFI we are able to manage using nmcli commands .
>-> nmcli device 
>DEVICE TYPE  STATE CONNECTION   
> wlp0s21f0u4wifi   connected    test 
> 
>  2) for bluetooth can we except like these ( bluetooth interface (eg.
> bnp0)) using nmcli commands .
>
>   My  networkmanager_1.10.6.bbappend file :-
>   PACKAGECONFIG_append = " modemmanager"
>   PACKAGECONFIG_append = " ppp ifupdown wifi bluez5"  
>
>I added bluez5 in .bbappend file , i thought it will manage
> through these , but not happening , 
>   i think by default bluez5 is dealing with connman ,  how we can
> switch bluez5 with networkmanager .  

1.10.0 was released almost 3 years ago (and the minor update 1.10.6
five months after that). If possible, I wouldn't bother with such an
old version and use something more recent.

Anyway, did you build NetworkManager with bluetooth support enabled?

Under `nmcli device` you would see the paired bluetooth devices (that
support network related bluetooth profiles).


Did you look at the log file?

   
>3) using nmcli commands will show bluetooth device is connected or
> not ? 

nmcli device
nmcli connection




best,
Thomas


signature.asc
Description: This is a digitally signed message part
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: manage bluetooth devices using NetworkManger

[NIKHIL PATIL via networkmanager-list]

Hi Team,
We are using Redpine module (rsi9113) which support bluetooth + wifi .
OS - yocto based linux.
NetworkManager version :- 1.10.6

   1) for WIFI we are able to manage using nmcli commands .
   -> nmcli device
   DEVICE TYPE STATE CONNECTION
wlp0s21f0u4 wifi connected test

2) for bluetooth can we except like these ( bluetooth interface (eg. bnp0))
using nmcli commands .
My *networkmanager_1.10.6.bbappend* file :-
PACKAGECONFIG_append = " modemmanager"
  PACKAGECONFIG_append = " ppp ifupdown wifi bluez5"
I added *bluez5* in .bbappend file , i thought it will manage through these
, but not happening ,
i think by default bluez5 is dealing with *connman , *how we can switch
bluez5 with* networkmanager .*
3) using nmcli commands will show bluetooth device is connected or not ?

On Mon, Oct 5, 2020 at 12:26 PM Thomas Haller  wrote:

> On Mon, 2020-10-05 at 12:22 +0530, NIKHIL PATIL via networkmanager-list
> wrote:
> > hi ,
> >   any update on these ?
> >we badly stuck here.
> >
> > On Tue, Sep 22, 2020 at 11:21 AM NIKHIL PATIL 
> > wrote:
> > > Hi ,
> > >   We are using Redpine rsi9113 bluetooth module connected
> > > via USB to Soc board.
> > >   processor - intel 3930 .
> > >   platform - yocto based linux .
> > >  How we can manage bluetooth device using NetworkManager (nmcli)
> > > commands.
>
>
> Hi,
>
>
> recent NetworkManager version interact (only) with bluez5.
>
> As always in NetworkManager, create a suitable connection profile and
> activate it. Actually, NetworkManager will automatically generate a
> profile for all paired devices, so you should see the respective
> profiles.
>
> And, read the logfile if something doesn't work (enable level=TRACE
> logging. See
>
> https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf#n28
>  ).
>
> Also, your question on this list is lacking detail. Explain what you
> are doing, what *exactly* you want to achieve, and what you think is
> happening.
>
>
> best,
> Thomas
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: manage bluetooth devices using NetworkManger

[Thomas Haller via networkmanager-list]

On Mon, 2020-10-05 at 12:22 +0530, NIKHIL PATIL via networkmanager-list 
wrote:
> hi , 
>   any update on these ?
>we badly stuck here.
> 
> On Tue, Sep 22, 2020 at 11:21 AM NIKHIL PATIL 
> wrote:
> > Hi ,
> >   We are using Redpine rsi9113 bluetooth module connected
> > via USB to Soc board. 
> >   processor - intel 3930 .
> >   platform - yocto based linux .
> >  How we can manage bluetooth device using NetworkManager (nmcli)
> > commands.


Hi,


recent NetworkManager version interact (only) with bluez5.

As always in NetworkManager, create a suitable connection profile and
activate it. Actually, NetworkManager will automatically generate a
profile for all paired devices, so you should see the respective
profiles.

And, read the logfile if something doesn't work (enable level=TRACE
logging. See 
https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf#n28
 ).

Also, your question on this list is lacking detail. Explain what you
are doing, what *exactly* you want to achieve, and what you think is
happening.


best,
Thomas


signature.asc
Description: This is a digitally signed message part
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: manage bluetooth devices using NetworkManger

[NIKHIL PATIL via networkmanager-list]

hi ,
  any update on these ?
   we badly stuck here.

On Tue, Sep 22, 2020 at 11:21 AM NIKHIL PATIL  wrote:

> Hi ,
>   We are using Redpine rsi9113 bluetooth module connected via USB
> to Soc board.
>   processor - intel 3930 .
>   platform - yocto based linux .
>  How we can manage bluetooth device using NetworkManager (nmcli) commands.
>
>
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

manage bluetooth devices using NetworkManger

[NIKHIL PATIL via networkmanager-list]

Hi ,
  We are using Redpine rsi9113 bluetooth module connected via USB
to Soc board.
  processor - intel 3930 .
  platform - yocto based linux .
 How we can manage bluetooth device using NetworkManager (nmcli) commands.
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: [PATCH] bluetooth: fix missing 'connected' notifications (rh #1255284)

[Dan Williams]

On Sun, 2015-10-25 at 19:55 +0100, Thomas Haller wrote:
> On Fri, 2015-10-23 at 11:50 -0500, Dan Williams wrote:
> > Because Bluez5 dropped DUN support, NM must do that manually which
> > includes emulating the "connected" property for Bluetooth devices
> > when
> > DUN is used.  It does this by setting priv->connected = TRUE in
> > nm_bluez_device_connect_finish().
> > 
> > But for PAN, when NM does process the 'connected' property change
> > notification, priv->connected is already TRUE and
> > _take_variant_property_connected() does nothing.  Hence the
> > corresponding GObject property notification is not emitted,
> > nm-device-bt.c::check_connect_continue() will never return success,
> > and
> > the activation times out.
> > 
> > To fix this, ensure that GObject notifications are emitted when the
> > device is connected, even if emulated internally.
> > 
> 
> 
> Patch looks good to me.
> I merged the patch:
> 
> master: 
> http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=0e3086e8b885164f24b43a1060cb1f87a62723a8
> 
> nm-1-0: 
> http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=cccb8fe5e6945085d43050411c1ced26453d85df

Thanks!

Dan

___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: [PATCH] bluetooth: fix missing 'connected' notifications (rh #1255284)

[Thomas Haller]

On Fri, 2015-10-23 at 11:50 -0500, Dan Williams wrote:
> Because Bluez5 dropped DUN support, NM must do that manually which
> includes emulating the "connected" property for Bluetooth devices
> when
> DUN is used.  It does this by setting priv->connected = TRUE in
> nm_bluez_device_connect_finish().
> 
> But for PAN, when NM does process the 'connected' property change
> notification, priv->connected is already TRUE and
> _take_variant_property_connected() does nothing.  Hence the
> corresponding GObject property notification is not emitted,
> nm-device-bt.c::check_connect_continue() will never return success,
> and
> the activation times out.
> 
> To fix this, ensure that GObject notifications are emitted when the
> device is connected, even if emulated internally.
> 


Patch looks good to me.
I merged the patch:

master: 
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=0e3086e8b885164f24b43a1060cb1f87a62723a8

nm-1-0: 
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=cccb8fe5e6945085d43050411c1ced26453d85df


Thomas

signature.asc
Description: This is a digitally signed message part
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

[PATCH] bluetooth: fix missing 'connected' notifications (rh #1255284)

[Dan Williams]

Because Bluez5 dropped DUN support, NM must do that manually which
includes emulating the "connected" property for Bluetooth devices when
DUN is used.  It does this by setting priv->connected = TRUE in
nm_bluez_device_connect_finish().

But for PAN, when NM does process the 'connected' property change
notification, priv->connected is already TRUE and
_take_variant_property_connected() does nothing.  Hence the
corresponding GObject property notification is not emitted,
nm-device-bt.c::check_connect_continue() will never return success, and
the activation times out.

To fix this, ensure that GObject notifications are emitted when the
device is connected, even if emulated internally.

---

diff --git a/src/devices/bluetooth/nm-bluez-device.c 
b/src/devices/bluetooth/nm-bluez-device.c
index cc44b9e..b703214 100644
--- a/src/devices/bluetooth/nm-bluez-device.c
+++ b/src/devices/bluetooth/nm-bluez-device.c
@@ -600,8 +600,10 @@ nm_bluez_device_connect_finish (NMBluezDevice *self,
return NULL;
 
device = (const char *) g_simple_async_result_get_op_res_gpointer 
(simple);
-   if (device && priv->bluez_version == 5)
+   if (device && priv->bluez_version == 5) {
priv->connected = TRUE;
+   g_object_notify (G_OBJECT (self), NM_BLUEZ_DEVICE_CONNECTED);
+   }
 
return device;
 }

___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

[PATCH] build: don't try to build bluetooth widget with newer bluez

[Cho, Yu-Chen]

since NM doesn't yet support bluez5 with DUN, the bluetooth plugin
is useless in that case too

Signed-off-by: Cho, Yu-Chen a...@suse.com
---
 configure.ac | 1 +
 1 file changed, 1 insertion(+)

diff --git a/configure.ac b/configure.ac
index d6ca9e6..3dafe3b 100644
--- a/configure.ac
+++ b/configure.ac
@@ -140,6 +140,7 @@ case ${with_bluetooth} in
PKG_CHECK_MODULES(GNOME_BLUETOOTH,
  gnome-bluetooth-1.0 = 2.27.6
  gnome-bluetooth-1.0  3.11.0
+ bluez  5.0
  libnm-util libnm-glib,
  have_gbt=yes, have_gbt=no)
;;
-- 
1.8.4.5

___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Bluetooth tethering with NM?

[Dan Williams]

On Sat, 2014-07-26 at 18:39 +0200, cheater00 . wrote:
 In fact, would you please create a diff of /etc/NetworkManager before
 and after pairing up with your phone? Hopefully on a fresh instance of
 /etc/NetworkManager?

Something like this:

[connection]
id=T-Mobile Internet
uuid=1535b59d-6d43-4a4a-a30c-2c8d97b6d3bb
type=bluetooth
autoconnect=false

[gsm]
apn=epc.tmobile.com

[bluetooth]
bdaddr=00:26:E2:33:22:11
type=dun

Should be all you need.

Dan

 Thank you
 
 On Sat, Jul 26, 2014 at 6:23 PM, cheater00 . cheate...@gmail.com wrote:
  Hi Dan,
  thanks for your quick reply.
 
  I don't run GNOME and don't have it installed; I run MATE which is a
  fork of GNOME 2. They have abandoned mate-bluetooth-applet (which was
  their copy of the gnome-blueetoth-applet) switching to blueman. They
  have probably based mate-bluetooth-applet off a version of
  gnome-bluetooth-applet which didn't have that checkbox yet; I don't
  see it if I use the latest version provided by MATE (1.6, while the
  latest MATE is 1.8).
 
  What would the procedure be without gnome-bluetooth-applet?
 
  I assume this creates a file somewhere like
  /etc/NetworkManager/system-connections; could you post the file that
  you get?
 
  Thanks a lot
 
  On Fri, Jul 25, 2014 at 5:38 PM, Dan Williams d...@redhat.com wrote:
  On Thu, 2014-07-24 at 17:11 +0200, cheater00 . wrote:
  Hi,
  I am on Ubuntu 13.10 and am trying to enable bluetooth tethering (so
  that I can use my phone's internet connection). This is preferrable to
  wifi tethering which eats up the battery.
 
  I can easily pair my laptop to my phone using blueman but, contrary to
  what tutorials online show, the bluetooth connection doesn't show up
  in nm-applet.
 
  My network-manager-gnome package is at version 0.9.8.0-1ubuntu5.1.
 
  blueman is 1.23+update1-2ubuntu1.
 
  The connection gets created when you pair the phone with the laptop, via
  the GNOME bluetooth applet.  It looks somewhat like this:
 
  http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/
 
  When you finish pairing the phone, you'll get a checkbox that has
  options for using the phone either as a PAN device, or a DUN device,
  depending on what your phone supports.  For PAN, all that's required is
  checking the box.  For DUN, ModemManager gets started to inspect the
  phone, and then the Mobile Broadband Wizard appears to let you configure
  the APN and other details.  After that, the phone should appear in the
  nm-applet menu.  Can you try the GNOME Bluetooth applet process and see
  if that makes things work?
 
  Dan
 


___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Bluetooth tethering with NM?

[cheater00 .]

I have bluetooth tethering enabled on my Samsung Galaxy S4 with stock Android.

On Sat, Jul 26, 2014 at 9:15 PM, Marius Kotsbak mar...@kotsbak.com wrote:
 Which phone? On Android it seems like you need to enable Bluetooth tethering
 in the menu.
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Bluetooth tethering with NM?

[cheater00 .]

Hi Dan,
thanks for your quick reply.

I don't run GNOME and don't have it installed; I run MATE which is a
fork of GNOME 2. They have abandoned mate-bluetooth-applet (which was
their copy of the gnome-blueetoth-applet) switching to blueman. They
have probably based mate-bluetooth-applet off a version of
gnome-bluetooth-applet which didn't have that checkbox yet; I don't
see it if I use the latest version provided by MATE (1.6, while the
latest MATE is 1.8).

What would the procedure be without gnome-bluetooth-applet?

I assume this creates a file somewhere like
/etc/NetworkManager/system-connections; could you post the file that
you get?

Thanks a lot

On Fri, Jul 25, 2014 at 5:38 PM, Dan Williams d...@redhat.com wrote:
 On Thu, 2014-07-24 at 17:11 +0200, cheater00 . wrote:
 Hi,
 I am on Ubuntu 13.10 and am trying to enable bluetooth tethering (so
 that I can use my phone's internet connection). This is preferrable to
 wifi tethering which eats up the battery.

 I can easily pair my laptop to my phone using blueman but, contrary to
 what tutorials online show, the bluetooth connection doesn't show up
 in nm-applet.

 My network-manager-gnome package is at version 0.9.8.0-1ubuntu5.1.

 blueman is 1.23+update1-2ubuntu1.

 The connection gets created when you pair the phone with the laptop, via
 the GNOME bluetooth applet.  It looks somewhat like this:

 http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/

 When you finish pairing the phone, you'll get a checkbox that has
 options for using the phone either as a PAN device, or a DUN device,
 depending on what your phone supports.  For PAN, all that's required is
 checking the box.  For DUN, ModemManager gets started to inspect the
 phone, and then the Mobile Broadband Wizard appears to let you configure
 the APN and other details.  After that, the phone should appear in the
 nm-applet menu.  Can you try the GNOME Bluetooth applet process and see
 if that makes things work?

 Dan

___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Bluetooth tethering with NM?

[cheater00 .]

In fact, would you please create a diff of /etc/NetworkManager before
and after pairing up with your phone? Hopefully on a fresh instance of
/etc/NetworkManager?

Thank you

On Sat, Jul 26, 2014 at 6:23 PM, cheater00 . cheate...@gmail.com wrote:
 Hi Dan,
 thanks for your quick reply.

 I don't run GNOME and don't have it installed; I run MATE which is a
 fork of GNOME 2. They have abandoned mate-bluetooth-applet (which was
 their copy of the gnome-blueetoth-applet) switching to blueman. They
 have probably based mate-bluetooth-applet off a version of
 gnome-bluetooth-applet which didn't have that checkbox yet; I don't
 see it if I use the latest version provided by MATE (1.6, while the
 latest MATE is 1.8).

 What would the procedure be without gnome-bluetooth-applet?

 I assume this creates a file somewhere like
 /etc/NetworkManager/system-connections; could you post the file that
 you get?

 Thanks a lot

 On Fri, Jul 25, 2014 at 5:38 PM, Dan Williams d...@redhat.com wrote:
 On Thu, 2014-07-24 at 17:11 +0200, cheater00 . wrote:
 Hi,
 I am on Ubuntu 13.10 and am trying to enable bluetooth tethering (so
 that I can use my phone's internet connection). This is preferrable to
 wifi tethering which eats up the battery.

 I can easily pair my laptop to my phone using blueman but, contrary to
 what tutorials online show, the bluetooth connection doesn't show up
 in nm-applet.

 My network-manager-gnome package is at version 0.9.8.0-1ubuntu5.1.

 blueman is 1.23+update1-2ubuntu1.

 The connection gets created when you pair the phone with the laptop, via
 the GNOME bluetooth applet.  It looks somewhat like this:

 http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/

 When you finish pairing the phone, you'll get a checkbox that has
 options for using the phone either as a PAN device, or a DUN device,
 depending on what your phone supports.  For PAN, all that's required is
 checking the box.  For DUN, ModemManager gets started to inspect the
 phone, and then the Mobile Broadband Wizard appears to let you configure
 the APN and other details.  After that, the phone should appear in the
 nm-applet menu.  Can you try the GNOME Bluetooth applet process and see
 if that makes things work?

 Dan

___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Bluetooth tethering with NM?

[Marius Kotsbak]

Which phone? On Android it seems like you need to enable Bluetooth
tethering in the menu.
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Bluetooth tethering with NM?

[Dan Williams]

On Thu, 2014-07-24 at 17:11 +0200, cheater00 . wrote:
 Hi,
 I am on Ubuntu 13.10 and am trying to enable bluetooth tethering (so
 that I can use my phone's internet connection). This is preferrable to
 wifi tethering which eats up the battery.
 
 I can easily pair my laptop to my phone using blueman but, contrary to
 what tutorials online show, the bluetooth connection doesn't show up
 in nm-applet.
 
 My network-manager-gnome package is at version 0.9.8.0-1ubuntu5.1.
 
 blueman is 1.23+update1-2ubuntu1.

The connection gets created when you pair the phone with the laptop, via
the GNOME bluetooth applet.  It looks somewhat like this:

http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/

When you finish pairing the phone, you'll get a checkbox that has
options for using the phone either as a PAN device, or a DUN device,
depending on what your phone supports.  For PAN, all that's required is
checking the box.  For DUN, ModemManager gets started to inspect the
phone, and then the Mobile Broadband Wizard appears to let you configure
the APN and other details.  After that, the phone should appear in the
nm-applet menu.  Can you try the GNOME Bluetooth applet process and see
if that makes things work?

Dan

___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Bluetooth tethering with NM?

[cheater00 .]

Hi,
I am on Ubuntu 13.10 and am trying to enable bluetooth tethering (so
that I can use my phone's internet connection). This is preferrable to
wifi tethering which eats up the battery.

I can easily pair my laptop to my phone using blueman but, contrary to
what tutorials online show, the bluetooth connection doesn't show up
in nm-applet.

My network-manager-gnome package is at version 0.9.8.0-1ubuntu5.1.

blueman is 1.23+update1-2ubuntu1.

I would appreciate any help or pointers.

Thanks!
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: [n-m-a] Support for the ModemManager1 interface in bluetooth DUN setups

[Aleksander Morgado]

 The following two patches include support for the new ModemManager1 interface
 in the bluetooth DUN setups, so that we know which kind of device we're 
 handling
 before launching the mobile broadband wizard.
 
 [PATCH 1/2] build: new `--with-modem-manager-1' to check for new...
 [PATCH 2/2] nma-bt-device: handle modems from the new...

For reference, these just got applied to git master.

-- 
Aleksander
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

[n-m-a] Support for the ModemManager1 interface in bluetooth DUN setups

[Aleksander Morgado]

The following two patches include support for the new ModemManager1 interface
in the bluetooth DUN setups, so that we know which kind of device we're handling
before launching the mobile broadband wizard.

[PATCH 1/2] build: new `--with-modem-manager-1' to check for new...
[PATCH 2/2] nma-bt-device: handle modems from the new...
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

[NM] [PATCH] corrected Bluetooth driver name checking

[Andrew -]

412c412
   if (driver  !strcmp (driver, bluetooth)) {
---
   if (driver  strcmp (driver, bluetooth)) {


That`s it.
As far as I can see, that IF-statement should evaluate TRUE only when
the driver is something other than Bluetooth.
This fix shall solve
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/583728

Please don`t blame me for improper formatting or something alike. This
is my first post in mailing lists.
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: network-manager-applet fails to compile against gnome-bluetooth-3.3

[Dan Williams]

On Sat, 2011-11-26 at 12:10 -0600, Daniel Drake wrote:
 On Fri, Nov 25, 2011 at 9:10 AM, Daniel Drake d...@laptop.org wrote:
  It looks like gnome-bluetooth used to specify dbus-glib includes/libs
  but no longer does so. Perhaps network-manager-applet compile should
  use the suggested includes of libnm-glib in this case.
 
 Network-manager-applet does have this correct upstream, but in Fedora
 as its built as a subpackage there is a hacky patch applied to enable
 building of network-manager-applet before NetworkManager headers/libs
 are fully installed on the build host. I updated this patch to pull in
 dbus-glib-1 cflags/libs and now it is working.

I keep meaning to split out the applet for every Fedora release but
never quite get there.  Perhaps now would be the time for F17/rawhide
since it's quite early.

Dan

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: network-manager-applet fails to compile against gnome-bluetooth-3.3

[Daniel Drake]

On Fri, Nov 25, 2011 at 9:10 AM, Daniel Drake d...@laptop.org wrote:
 It looks like gnome-bluetooth used to specify dbus-glib includes/libs
 but no longer does so. Perhaps network-manager-applet compile should
 use the suggested includes of libnm-glib in this case.

Network-manager-applet does have this correct upstream, but in Fedora
as its built as a subpackage there is a hacky patch applied to enable
building of network-manager-applet before NetworkManager headers/libs
are fully installed on the build host. I updated this patch to pull in
dbus-glib-1 cflags/libs and now it is working.

Daniel
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

network-manager-applet fails to compile against gnome-bluetooth-3.3

[Daniel Drake]

Hi,

NetworkManager is breaking rawhide because it needs to be rebuilt
againts gnome-bluetooth-3.3. However, network-manager-applet fails to
rebuild:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../..
-DDATADIR=\/usr/share\ -DICONDIR=\\
-DLOCALEDIR=\/usr/share/locale\ -I../.. -I../../src/marshallers
-I../../src/utils -I../../src/libnm-gtk -I../../../include
-I../../../libnm-util -I../../../libnm-glib -pthread
-I/usr/include/gnome-bluetooth -I/usr/include/gtk-3.0
-I/usr/include/atk-1.0 -I/usr/include/cairo
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/pixman-1 -I/usr/include/freetype2
-I/usr/include/libpng15 -Wall -Werror -std=gnu89 -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m32 -march=i686 -mtune=atom
-fasynchronous-unwind-tables -Wshadow -Wmissing-declarations
-Wmissing-prototypes -Wno-deprecated-declarations
-Wno-error=deprecated-declarations -Wdeclaration-after-statement
-Wfloat-equal -Wno-unused-parameter -Wno-sign-compare
-fno-strict-aliasing -c bt-widget.c  -fPIC -DPIC -o .libs/bt-widget.o
In file included from bt-widget.c:45:0:
../../../libnm-glib/nm-remote-settings.h:28:28: fatal error:
dbus/dbus-glib.h: No such file or directory

It looks like gnome-bluetooth used to specify dbus-glib includes/libs
but no longer does so. Perhaps network-manager-applet compile should
use the suggested includes of libnm-glib in this case.

Thanks
Daniel
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: network-manager-applet fails to compile against gnome-bluetooth-3.3

[Bastien Nocera]

On Fri, 2011-11-25 at 09:10 -0600, Daniel Drake wrote:
 Hi,
 
 NetworkManager is breaking rawhide because it needs to be rebuilt
 againts gnome-bluetooth-3.3. However, network-manager-applet fails to
 rebuild:
snip
 It looks like gnome-bluetooth used to specify dbus-glib includes/libs
 but no longer does so. Perhaps network-manager-applet compile should
 use the suggested includes of libnm-glib in this case.

Indeed, gnome-bluetooth got ported to GDBus in the 3.4 devel cycle.

Cheers

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager and Bluetooth

[Dan Williams]

On Wed, 2011-06-01 at 00:10 +0100, Timothy Murphy wrote:
 I thought I read some time ago that NM had incorporated Bluetooth
 in some way, but I couldn't find any reference to Bluetooth
 in the NM files in Fedora.
 
 To be concrete, can I use NM to establish Bluetooth connection
 with a mobile phone?

If you're using the GNOME desktop, it's done when you pair the phone,
like so:

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: bluetooth DUN silently discarding invalid APNs

[Dan Williams]

On Fri, 2011-05-06 at 11:02 +0100, Marc Herbert wrote:
  By the way it is not possible to enter a blank APN either (asking the
  network use the default APN). This again works perfectly with wvdial.
  And this is valid.
 
  Yes, it's valid, but note that the default APN is stored in the
  *device*, not the SIM card, and has no relation to the SIM card at all.
  So if you ever swap SIM cards, or use a different provider, then the APN
  is surely going to be wrong and the dialing will fail.  However, I've
  been thinking of ways to enable using the default APN since that works
  for some phones that don't allow setting the APN at all via AT commands,
  but where dialing works fine.
  
 
 No, I was not referring to any default APN stored from the phone, but
 to the case where the phone does not provide any APN to the network *at
 all*.
 
 Section 3.1 Definitions at the very beginning of 3GPP 23.401:
 
   Default APN: A Default APN is defined as the APN which is marked as
   default in the subscription data [...] when no APN is provided by
   the UE.
 
 UE = User Equipment. The subscription data comes from the HSS in the 
 network.
 
 In the same spec see also paragraph 12 in section 5.3.2.1. This
 paragraph has about 5-6 sentences starting with: If the UE does [not]
 provide an APN,...
 
 The operator I can connect to using a blank APN did not even exist yet
 when I bought the phone, so for sure the phone is not sneakily
 providing any good default APN to get me online. It is a old
 2.5G EDGE phone by the way.

And T-Mobile appears to allow this as well according to my testing; I
looked around and couldn't find much information on it at all, but
you're right, and we should allow passing no APN to MM, which would
trigger MM to create a blank default PDP context with no APN, which MM
would then activate.  Then we hope it works.

Dan


___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

NetworkManager and Bluetooth

[Timothy Murphy]

I thought I read some time ago that NM had incorporated Bluetooth
in some way, but I couldn't find any reference to Bluetooth
in the NM files in Fedora.

To be concrete, can I use NM to establish Bluetooth connection
with a mobile phone?

-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: bluetooth DUN silently discarding invalid APNs

[Marc Herbert]

 By the way it is not possible to enter a blank APN either (asking the
 network use the default APN). This again works perfectly with wvdial.
 And this is valid.

 Yes, it's valid, but note that the default APN is stored in the
 *device*, not the SIM card, and has no relation to the SIM card at all.
 So if you ever swap SIM cards, or use a different provider, then the APN
 is surely going to be wrong and the dialing will fail.  However, I've
 been thinking of ways to enable using the default APN since that works
 for some phones that don't allow setting the APN at all via AT commands,
 but where dialing works fine.
 

No, I was not referring to any default APN stored from the phone, but
to the case where the phone does not provide any APN to the network *at
all*.

Section 3.1 Definitions at the very beginning of 3GPP 23.401:

  Default APN: A Default APN is defined as the APN which is marked as
  default in the subscription data [...] when no APN is provided by
  the UE.

UE = User Equipment. The subscription data comes from the HSS in the network.

In the same spec see also paragraph 12 in section 5.3.2.1. This
paragraph has about 5-6 sentences starting with: If the UE does [not]
provide an APN,...

The operator I can connect to using a blank APN did not even exist yet
when I bought the phone, so for sure the phone is not sneakily
providing any good default APN to get me online. It is a old
2.5G EDGE phone by the way.

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: bluetooth DUN silently discarding invalid APNs

[Marc Herbert]

Le 04/05/2011 21:02, Dan Williams a écrit :

 APNs are defined by GSM 03.03 section 14.9 which says:

 http://www.3gpp.org/ftp/Specs/html-info/0303.htm

 =
 The syntax of the APN shall follow the Name Syntax defined in RFC 2181
 [14] and RFC 1035 [15]. The APN consists of one or more labels. Each
 label is coded as one octet length field followed by that number of
 octets coded as 8 bit ASCII characters. Following RFC 1035 [15] the
 labels should consist only of the alphabetic characters (A-Z and a-z),
 digits (0-9) and the dash (-). The case of alphabetic characters is not
 significant. The APN is not terminated by a length byte of zero.
 =
 

It is funny how GSM 03.03 makes the usual misinterpretation of (the
admittedly confusing) DNS RFC1035, while in the same paragraph quoting
RFC2181 which explicitly rectifies this misinterpretation (in section
11).

DNS does not put any restrictions on label characters. This
restriction came from hostname.

 But the specification does use the word should, which implies that
 APNs may deviate from the suggestion.

I suspect resolving the APN through DNS is not even mandatory. Some
networks could use alternative ways to select the GGSN.

 Many APNs already use '.' (which the specification does not suggest)

That is because '.' is the usual way to separate DNS labels in text
form (not on the wire). The '.' is not part of any label.

 and perhaps we should allow _ too.

You should simply just stay clear of this whole mess and not validate
anything. This would add two new and incredibly great features:

- Restore an error message in case of a typo (as opposed to silently
  discarding user input)
- Support APNs with unusual characters.

Two new features by merely deleting some code, how great value is that?


Cheers,

Marc


___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: bluetooth DUN silently discarding invalid APNs

[Dan Williams]

On Thu, 2011-05-05 at 09:28 +0100, Marc Herbert wrote:
 Le 04/05/2011 21:02, Dan Williams a écrit :
 
  APNs are defined by GSM 03.03 section 14.9 which says:
 
  http://www.3gpp.org/ftp/Specs/html-info/0303.htm
 
  =
  The syntax of the APN shall follow the Name Syntax defined in RFC 2181
  [14] and RFC 1035 [15]. The APN consists of one or more labels. Each
  label is coded as one octet length field followed by that number of
  octets coded as 8 bit ASCII characters. Following RFC 1035 [15] the
  labels should consist only of the alphabetic characters (A-Z and a-z),
  digits (0-9) and the dash (-). The case of alphabetic characters is not
  significant. The APN is not terminated by a length byte of zero.
  =
  
 
 It is funny how GSM 03.03 makes the usual misinterpretation of (the
 admittedly confusing) DNS RFC1035, while in the same paragraph quoting
 RFC2181 which explicitly rectifies this misinterpretation (in section
 11).
 
 DNS does not put any restrictions on label characters. This
 restriction came from hostname.
 
  But the specification does use the word should, which implies that
  APNs may deviate from the suggestion.
 
 I suspect resolving the APN through DNS is not even mandatory. Some
 networks could use alternative ways to select the GGSN.
 
  Many APNs already use '.' (which the specification does not suggest)
 
 That is because '.' is the usual way to separate DNS labels in text
 form (not on the wire). The '.' is not part of any label.
 
  and perhaps we should allow _ too.
 
 You should simply just stay clear of this whole mess and not validate
 anything. This would add two new and incredibly great features:
 
 - Restore an error message in case of a typo (as opposed to silently
   discarding user input)
 - Support APNs with unusual characters.
 
 Two new features by merely deleting some code, how great value is that?

The code was put into NM in the first place to ensure that characters
like spaces and such that certainly *aren't* allowed in APNs weren't
used.  The validation is still necessary, but I think the core problem
we should fix is ensuring that you can't type invalid characters into
the box and you can't type an invalid APN length.  Then we should extend
the allowed characters.  We certainly shouldn't remove the checks
completely, since there *are* actually restrictions on the APN contents
and length.

Dan

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: bluetooth DUN silently discarding invalid APNs

[Marc Herbert]

 You should simply just stay clear of this whole mess and not validate
 anything. This would add two new and incredibly great features:

 - Restore an error message in case of a typo (as opposed to silently
   discarding user input)
 - Support APNs with unusual characters.

 Two new features by merely deleting some code, how great value is that?
 
 The code was put into NM in the first place to ensure that characters
 like spaces and such that certainly *aren't* allowed in APNs weren't
 used.  The validation is still necessary, but I think the core problem
 we should fix is ensuring that you can't type invalid characters into
 the box and you can't type an invalid APN length.  Then we should extend
 the allowed characters.  We certainly shouldn't remove the checks
 completely, since there *are* actually restrictions on the APN contents
 and length.

Besides the hostname legacy, please tell where do these certainly
not allowed characters come from. My Nokia phone lets me input any
character crap in the APN field without even a warning. Then I just
get the same Connection failed, check your settings error message
than for any other valid typo  (reminder: Nokia and Ericsson
designed and implemented GSM, UMTS  LTE practically alone). wvdial
lets me enter the same crap. So why is NetworkManager implementing
this? Too much spare time?

But once again, the core problem is not abusive validation. The core
problem is silently discarding user input with a misleading
configuration completed message. This needs an quick fix that cannot
wait the redesign of a better user interface. And surprise, there is a
really obvious quick fix: just behave like Nokia.

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: bluetooth DUN silently discarding invalid APNs

[Dan Williams]

On Thu, 2011-05-05 at 17:54 +0100, Marc Herbert wrote:
  You should simply just stay clear of this whole mess and not validate
  anything. This would add two new and incredibly great features:
 
  - Restore an error message in case of a typo (as opposed to silently
discarding user input)
  - Support APNs with unusual characters.
 
  Two new features by merely deleting some code, how great value is that?
  
  The code was put into NM in the first place to ensure that characters
  like spaces and such that certainly *aren't* allowed in APNs weren't
  used.  The validation is still necessary, but I think the core problem
  we should fix is ensuring that you can't type invalid characters into
  the box and you can't type an invalid APN length.  Then we should extend
  the allowed characters.  We certainly shouldn't remove the checks
  completely, since there *are* actually restrictions on the APN contents
  and length.
 
 Besides the hostname legacy, please tell where do these certainly
 not allowed characters come from. My Nokia phone lets me input any
 character crap in the APN field without even a warning. Then I just
 get the same Connection failed, check your settings error message
 than for any other valid typo  (reminder: Nokia and Ericsson
 designed and implemented GSM, UMTS  LTE practically alone). wvdial
 lets me enter the same crap. So why is NetworkManager implementing
 this? Too much spare time?

Because certain characters are not allowed, and the length is
restricted, and just because you have devices that might for some reason
allow this, there are devices that certainly don't, and these characters
are not valid at all anyway.  So to avoid unexpected errors *before* the
connect attempt, we should be filtering them out.  We don't allow spaces
in IP addresses, so why should we allow in APNs where they are also
invalid?  It's basic input validation.

Yes, we'll allow _.  But no, we're not going to allow ȫ.  Why?  Because
the standards disallow that.  APNs are not a freeform byte-string type.
Nor should we treat them as such.

The original reason that the validation code was added was specifically
for spaces.  These cause some modems to puke, not to mention that
causing the connect attempt to fail because there's a space in the APN
or something like that is completely unhelpful, when we know that these
characters are invalid.

Dan

 But once again, the core problem is not abusive validation. The core
 problem is silently discarding user input with a misleading
 configuration completed message. This needs an quick fix that cannot
 wait the redesign of a better user interface. And surprise, there is a
 really obvious quick fix: just behave like Nokia.
 
 ___
 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: bluetooth DUN silently discarding invalid APNs

[Dan Williams]

On Tue, 2011-05-03 at 12:33 +0100, Marc Herbert wrote:
 Hi,
 
   I wasted a number of hours when trying to tether using
 bluetooth... it seems any APN containing an underscore _ causes the
 DUN configuration entered into the gnome bluetooth wizard to be
 *SILENTLY* discarded.

APNs are defined by GSM 03.03 section 14.9 which says:

http://www.3gpp.org/ftp/Specs/html-info/0303.htm
=
The syntax of the APN shall follow the Name Syntax defined in RFC 2181
[14] and RFC 1035 [15]. The APN consists of one or more labels. Each
label is coded as one octet length field followed by that number of
octets coded as 8 bit ASCII characters. Following RFC 1035 [15] the
labels should consist only of the alphabetic characters (A-Z and a-z),
digits (0-9) and the dash (-). The case of alphabetic characters is not
significant. The APN is not terminated by a length byte of zero.
=

Note that none of the APNs in the  mobile broadband provider database
contain an underscore.

But the specification does use the word should, which implies that
APNs may deviate from the suggestion.  Many APNs already use '.' (which
the specification does not suggest) and perhaps we should allow _ too.

 Can anyone reproduce this? Only a bluetooth phone is needed, plus
 deleting the bluetooth configuration for this phone if you already
 have one (sorry), so you can run the wizard on it again. You do not
 even need a valid network subscription to reproduce this problem.
 
 I am using NetworkManager 0.8.4 in Fedora 14.
 
 Since the APN is the hostname of the GGSN or PDN gateway, I guess this
 validation tries to apply the restrictions of RFC 1123 concerning
 hostnames (note that, as opposed to a common misconception, the DNS
 itself does not have any such restriction, see section 11 in RFC
 2181. DNS is not just for hostnames.)
 
 I see extremely little value in this validation. There are millions of
 other and more likely typos that it will never catch. Since it does
 not even issue an error message but silently discard the user input
 instead, the little value that ever was intended is completely
 gone. This validation feature has now become a severe bug since it
 hides the next and proper error message (i.e., connection failed,
 check your settings). And wastes hours.
 
 Even worse, wvdial is perfectly able to get me online using an APN
 that includes an underscore. So whatever the standards say, this
 validation prevents some configurations to work.
 
 By the way it is not possible to enter a blank APN either (asking the
 network use the default APN). This again works perfectly with wvdial.
 And this is valid.

Yes, it's valid, but note that the default APN is stored in the
*device*, not the SIM card, and has no relation to the SIM card at all.
So if you ever swap SIM cards, or use a different provider, then the APN
is surely going to be wrong and the dialing will fail.  However, I've
been thinking of ways to enable using the default APN since that works
for some phones that don't allow setting the APN at all via AT commands,
but where dialing works fine.

Dan

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

bluetooth DUN silently discarding invalid APNs

[Marc Herbert]

Hi,

  I wasted a number of hours when trying to tether using
bluetooth... it seems any APN containing an underscore _ causes the
DUN configuration entered into the gnome bluetooth wizard to be
*SILENTLY* discarded.

Can anyone reproduce this? Only a bluetooth phone is needed, plus
deleting the bluetooth configuration for this phone if you already
have one (sorry), so you can run the wizard on it again. You do not
even need a valid network subscription to reproduce this problem.

I am using NetworkManager 0.8.4 in Fedora 14.

Since the APN is the hostname of the GGSN or PDN gateway, I guess this
validation tries to apply the restrictions of RFC 1123 concerning
hostnames (note that, as opposed to a common misconception, the DNS
itself does not have any such restriction, see section 11 in RFC
2181. DNS is not just for hostnames.)

I see extremely little value in this validation. There are millions of
other and more likely typos that it will never catch. Since it does
not even issue an error message but silently discard the user input
instead, the little value that ever was intended is completely
gone. This validation feature has now become a severe bug since it
hides the next and proper error message (i.e., connection failed,
check your settings). And wastes hours.

Even worse, wvdial is perfectly able to get me online using an APN
that includes an underscore. So whatever the standards say, this
validation prevents some configurations to work.

By the way it is not possible to enter a blank APN either (asking the
network use the default APN). This again works perfectly with wvdial.
And this is valid.

Cheers,

Marc


___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

How nm-applet and gnome-bluetooth interact to create a bluetooth connection?

[Lamarque Vieira Souza]

Hi all,

Alex Fiestas and me are trying to implement Bluetooth DUN support for 
KDE. We spent some time trying to figure out the steps nm-applet and gnome-
bluetooth do to implement it but without much success. Can someone help us?

During my tests I hit this part of NM code in src/nm-manager.c:

/* 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;
}

Commenting the return allows me to use my cellphone as bluetooth 
serial 
modem (after creating /dev/rfcomm0 using BlueZ), but of course I guess that 
code is there for a reason. I still do not understand how gnome-bluetooth (or 
nm-applet) creates the rfcomm port. I know that can be done using BlueZ's DBus 
interface by calling the org.bluez.Serial.Connect method on a bluetooth 
device. But since NM is explicitly ignoring the rfcomm port, how are NM's 
bluetooth connections supposed to work?

-- 
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Cannot add another Bluetooth DUN Device N900

[Jonathan Pritchard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

I'm having trouble getting my Nokia N900 connecting to my Fedora 14
laptop (all latest updates) via Bluetooth DUN. I have previously got a
Nokia N82 working via Bluetooth DUN, and the entry for this still
appeared in the nm-applet menu, until I deleted its settings, trying to
get the N900 to work.

I have gone through Blueman to setup Bluetooth DUN, and Blueman reports
that the connection should show up in NetworkManager, however even after
restarts this isn't the case. Moreover, there are no new settings in
gconf created for this connection, so I don't think it's even gotten
that far. I deleted all entries in the .gconf folder to the old Nokia
N82 settings, as well.

These are the packages I'm using:
NetworkManager-0.8.3.998-2.fc14.i686
NetworkManager-gnome-0.8.3.998-2.fc14.i686
ModemManager-0.4-4.git20100720.fc14.i686


Here is some output from /var/log/messages:
Apr  3 03:47:16 Jon-Laptop bluetoothd[1483]: link_key_request
(sba=00:23:4D:F4:54:AB, dba=0C:DD:EF:93:00:01)
Apr  3 03:47:16 Jon-Laptop bluetoothd[1483]: link_key_request
(sba=00:23:4D:F4:54:AB, dba=0C:DD:EF:93:00:01)
Apr  3 03:47:16 Jon-Laptop modem-manager: (rfcomm0) opening serial device...
Apr  3 03:47:17 Jon-Laptop modem-manager: (rfcomm0) closing serial device...
Apr  3 03:47:17 Jon-Laptop modem-manager: (rfcomm0) opening serial device...
Apr  3 03:47:17 Jon-Laptop modem-manager: (Generic): GSM modem
/sys/devices/pci:00/:00:1a.1/usb4/4-2 claimed port rfcomm0
Apr  3 03:47:17 Jon-Laptop NetworkManager[1326]: info ignoring modem
'rfcomm0' (no associated Bluetooth device)
Apr  3 03:47:17 Jon-Laptop modem-manager: Modem
/org/freedesktop/ModemManager/Modems/0: Equipment identifier set
(356938034104571)
Apr  3 03:47:17 Jon-Laptop modem-manager: (rfcomm0) closing serial device...

I would really appreciate your help. Many thanks.

Jon Pritchard

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk2X48MACgkQV/z7jdey4lFQxQCguSbNSwW6FXwzZNjnIIUMdEkU
zjkAnj6FfgzDl1Qa3XRsdTJL5T3NFB8/
=SdX8
-END PGP SIGNATURE-
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: GSM modem via Bluetooth?

[Andrey Borzenkov]

On Thu, Jan 6, 2011 at 10:16 PM, Dan Williams d...@redhat.com 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?

[Bastien Nocera]

On Thu, 2011-01-06 at 13:16 -0600, Dan Williams wrote:
snip
 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?

[Bastien Nocera]

On Tue, 2011-01-11 at 20:36 +0300, Andrey Borzenkov wrote:
 On Thu, Jan 6, 2011 at 10:16 PM, Dan Williams d...@redhat.com 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?

[Dan Williams]

On Tue, 2011-01-11 at 17:49 +, Bastien Nocera wrote:
 On Thu, 2011-01-06 at 13:16 -0600, Dan Williams wrote:
 snip
  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: Mobile Broadband Status of Bluetooth DUN

[Jonathan Pritchard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/01/11 19:10, Dan Williams wrote:
 On Thu, 2011-01-06 at 04:55 +, Jonathan Pritchard wrote:
 Hello,

 I really love the new mobile broadband status feature you have for these
 sort of modems, showing the connection type and strength. I was just
 wondering if it's also possible to have this data supplied when
 connected through Bluetooth DUN to a mobile phone's modem for example?
 And also whether it's on the roadmap to implement this?
 
 It's not usually possible, and it depends on the specific phone itself.
 Most phones only provide a single DUN channel, which is used for data
 (PPP) when connected.  Clearly it can't be used for status info at the
 same time.
 
 Some phones provide additional rfcomm serial channels (not DUN channels)
 that *may* support AT commands at the same time as the DUN channel is
 active, but whether that's the case depends on the phone itself.
 
 I don't have a roadmap for adding support for that  mainly because I
 haven't investigated how  much work it would  take to do so.  That
 doesn't mean somebody else can't look into that too :)  First step would
 be to start an rfcomm connection to any non-DUN serial channel (using
 rfcomm connect hci0 bdaddr channel #) then start up minicom or
 screen and try to talk to the device with something like AT+CREG? and
 see what it reports.  If you get something back, then maybe it can be
 used alongside DUN.
 
 Dan
 

Thanks for the informative reply Dan. I didn't realise there was a
problem of only one channel, so to speak, on most phones. I was just
thinking from a user standpoint, if it's possible then it would be
desirable; I have a great experience with a Huawei E1550, and indeed the
Bluetooth tethering is working pretty well too.

Thanks for your great work on this project.

Jon Pritchard

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk0rR6QACgkQV/z7jdey4lEy3ACfVv3Hp+ho9Eanny8IKYsNNrPf
eegAoOfofvumIyMz7pB6a6hUosZphtC2
=zAAO
-END PGP SIGNATURE-
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Mobile Broadband Status of Bluetooth DUN

[Dan Williams]

On Thu, 2011-01-06 at 04:55 +, Jonathan Pritchard wrote:
 Hello,
 
 I really love the new mobile broadband status feature you have for these
 sort of modems, showing the connection type and strength. I was just
 wondering if it's also possible to have this data supplied when
 connected through Bluetooth DUN to a mobile phone's modem for example?
 And also whether it's on the roadmap to implement this?

It's not usually possible, and it depends on the specific phone itself.
Most phones only provide a single DUN channel, which is used for data
(PPP) when connected.  Clearly it can't be used for status info at the
same time.

Some phones provide additional rfcomm serial channels (not DUN channels)
that *may* support AT commands at the same time as the DUN channel is
active, but whether that's the case depends on the phone itself.

I don't have a roadmap for adding support for that  mainly because I
haven't investigated how  much work it would  take to do so.  That
doesn't mean somebody else can't look into that too :)  First step would
be to start an rfcomm connection to any non-DUN serial channel (using
rfcomm connect hci0 bdaddr channel #) then start up minicom or
screen and try to talk to the device with something like AT+CREG? and
see what it reports.  If you get something back, then maybe it can be
used alongside DUN.

Dan

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: GSM modem via Bluetooth?

[Dan Williams]

On Wed, 2010-11-24 at 09:06 +0300, Andrey Borzenkov wrote:
 On Wed, Nov 24, 2010 at 6:55 AM, Dan Williams d...@redhat.com wrote:
  On Sat, 2010-11-20 at 23:28 +0300, Andrey Borzenkov wrote:
  On Sat, Nov 20, 2010 at 1:24 AM, Dan Williams d...@redhat.com 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-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Mobile Broadband Status of Bluetooth DUN

[Jonathan Pritchard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

I really love the new mobile broadband status feature you have for these
sort of modems, showing the connection type and strength. I was just
wondering if it's also possible to have this data supplied when
connected through Bluetooth DUN to a mobile phone's modem for example?
And also whether it's on the roadmap to implement this?

Thanks.

Jon Pritchard
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk0lSyAACgkQV/z7jdey4lHsDwCgi1g7xu3I4/aJBcw7Gi0ZsA7x
kS4An0TQhWI4+9gZW/dtBFWT58uS6/zi
=QgbJ
-END PGP SIGNATURE-
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: GSM modem via Bluetooth?

[Ferry Toth]

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 d...@redhat.com wrote:
  On Sat, 2010-11-20 at 23:28 +0300, Andrey Borzenkov wrote:
  On Sat, Nov 20, 2010 at 1:24 AM, Dan Williams d...@redhat.com 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?

[Dan Williams]

On Sat, 2010-11-20 at 23:28 +0300, Andrey Borzenkov wrote:
 On Sat, Nov 20, 2010 at 1:24 AM, Dan Williams d...@redhat.com 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: GSM modem via Bluetooth?

[Andrey Borzenkov]

On Wed, Nov 24, 2010 at 6:55 AM, Dan Williams d...@redhat.com wrote:
 On Sat, 2010-11-20 at 23:28 +0300, Andrey Borzenkov wrote:
 On Sat, Nov 20, 2010 at 1:24 AM, Dan Williams d...@redhat.com 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: [OT] Re: GSM modem via Bluetooth?

[Sergio Monteiro Basto]

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

Re: GSM modem via Bluetooth?

[Andrey Borzenkov]

On Sat, Nov 20, 2010 at 1:24 AM, Dan Williams d...@redhat.com 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?

[Dan Williams]

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?

[Andrey Borzenkov]

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

Re: networkmanager hasnt option bluetooth device for DUN @ Acer TimelineX

[Dan Williams]

On Sat, 2010-09-25 at 19:45 -0700, thief shadow wrote:
 Hi,
 
 I've two laptop. One of them Fujitsu-Siemens and the other Acer
 TimelineX and Arch Linux is installed on both of them. There are some
 differences between running same programs because of hardware issues.
 Anyway, i dont know why there is no Bluetooth device option in
 NetworkManager on Acer TimelineX but it works perfect on
 Fujitsu-Siemens. Maybe versions are different because Arch Linux on
 Acer TimelineX is more up-to-date. i'm almost sure that the problem
 doesnt depends on hardware  because when i connect Dial-up Networking
 (DUN) everything goes ok.. 
 [r...@hoobastank ~]# rfcomm
 rfcomm0: F0:5E:CD:AE:FC:33 - 00:25:D0:BF:EF:AE channel 4 connected
 [reuse-dlc tty-attached]
 [r...@hoobastank ~]#
 so there is actually a Bluetooth device but NetworkManager cant handle
 it, there is no option.
 Arch Linux @ Acer TimelineX
 bluez-4.72-1
 blueman-1.21-5
 networkmanager-0.8.1-1
 modemmanager-0.4-1
 My smart phone : Nokia E71
 

NetworkManager 0.8.1 does have Bluetooth DUN support, so the version
should be fine.  However, you'll want to make sure you have
gnome-bluetooth installed, and then you'll want to re-pair your phone
and at the end of the pairing process, check the Access the internet
with my phone box, which makes the device show up in NetworkManager.

http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/

If that doesn't work, getting some logs from NetworkManager (usually
in /var/log/messages or /var/log/daemon.log) woudl be necessary to
figure out what's going wrong.

Dan


___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

networkmanager hasnt option bluetooth device for DUN @ Acer TimelineX

[thief shadow]

Hi,

 I've two laptop. One of them Fujitsu-Siemens and the other Acer 
TimelineX and Arch Linux is installed on both of them. There are some 
differences between running same programs because of hardware issues. Anyway,
 i dont know why there is no Bluetooth device option in NetworkManager 
on Acer TimelineX but it works perfect on Fujitsu-Siemens. Maybe 
versions are different because Arch Linux on Acer TimelineX is more 
up-to-date. i'm almost sure that the problem doesnt depends on hardware  
because when i connect Dial-up Networking (DUN) everything goes ok.. 
[r...@hoobastank ~]# rfcomm
rfcomm0: F0:5E:CD:AE:FC:33 - 00:25:D0:BF:EF:AE channel 4 connected [reuse-dlc 
tty-attached]
[r...@hoobastank ~]#
so there is actually a Bluetooth device but NetworkManager cant handle it, 
there is no option.
Arch Linux @ Acer TimelineX
bluez-4.72-1
blueman-1.21-5
networkmanager-0.8.1-1
modemmanager-0.4-1
My smart phone : Nokia E71




  ___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Blackberry Torch and Bluetooth Connections (Success!)

[Darren Albers]

ATT sent me a Torch today, on a whim I decided to try Bluetooth
Tethering which did not work with any previous model I have tried
(Storm1, Bold 9000, Bold 9700).   However this time it worked without
a hitch!

I am not sure if this is a change with OS6?   I know when Dan looked
at it earlier this year that there were a number of odd things about
it that resulted in it not working but those seem to have been fixed
or maybe the ModemManager update from the other day fixed it?

When I see OS6 come out for a bold 9700 I will test that as well to
see if it is the OS that works or something specific to the Torch.

As always thank you for the great work Dan!
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Blackberry Torch and Bluetooth Connections (Success!)

[Dan Williams]

On Thu, 2010-08-12 at 22:49 -0400, Darren Albers wrote:
 ATT sent me a Torch today, on a whim I decided to try Bluetooth
 Tethering which did not work with any previous model I have tried
 (Storm1, Bold 9000, Bold 9700).   However this time it worked without
 a hitch!

I did commit the CREG rework about a month ago or more, and that build
should be in Fedora 13 already.  That was the last problem that I think
we had with the Storm from June.  The BB only replied to +CGREG
(packet-switched status) and always returned ERROR to +CREG
(circuit-switched status); I changed MM to use +CGREG state if +CREG
never returned success.

 I am not sure if this is a change with OS6?   I know when Dan looked
 at it earlier this year that there were a number of odd things about
 it that resulted in it not working but those seem to have been fixed
 or maybe the ModemManager update from the other day fixed it?

I think we did fix them as described above and I pushed out a
ModemManager update in late July I think.

 When I see OS6 come out for a bold 9700 I will test that as well to
 see if it is the OS that works or something specific to the Torch.

Yeah, please let me know!

Dan


___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13 Beta

[Ascanio Alba]

Thank you for the quick turn around. I can confirm that the F13 packages
have fixed my problems. NM Bluetooth DUN is setup correctly by the wizard,
and ppp connection is made successfully.

On Tue, May 11, 2010 at 4:06 PM, Dan Williams d...@redhat.com wrote:

 On Mon, 2010-05-10 at 14:49 +0100, Bastien Nocera wrote:
  On Mon, 2010-05-10 at 14:36 +0100, Bastien Nocera wrote:
   On Mon, 2010-05-10 at 21:26 +0800, Ascanio Alba wrote:
I tried without blueman and got a similar error message.
   
   
I disabled blueman and went via the  gnome-bluetooth wizard to setup
new device.
I reached Access Internet using your mobile phone (DUN)
Got Detecting phone configuration...
MM seems to detect the 3G phone and exported it but NM rejects. Then
MM removes the device.
I tried this on another system  but even worse gnome bluetooth wizard
ABRTing.
  
   If the bluetooth wizard from gnome-bluetooth crashes, please file a
 bug.
 
  My guess is that it's a duplicate of:
  https://bugzilla.redhat.com/show_bug.cgi?id=590666
 
  Which is a bug in NetworkManager's gnome-bluetooth plugin.

 And is now fixed upstream and in F13.

 Dan



___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

RE: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13Beta

[Nguyen Canh Toan]

Hi, 

It seems that NetworkManager cannot find driver for your device, also your
device is not provide 'Generic interface'. Try to find/write its driver for
yourself.

 

  _  

From: networkmanager-list-boun...@gnome.org
[mailto:networkmanager-list-boun...@gnome.org] On Behalf Of Ascanio Alba
Sent: Sunday, May 09, 2010 9:55 PM
To: networkmanager-list@gnome.org
Subject: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora
13Beta

 

Hi,

 I have a bluetooth DUN device (/dev/rfcomm0) exported by modem-manager but
being ignored by NetworkManager.
This is on Fedora 13 Beta, latest updates-testing. I was getting some
SELinux denials but did an audit2allow to remove that variable from the
system.

blueman attaches to the DUN service.
modem-manager sees and exports the device, but NM ignores it.

Version: NetworkManager-0.8.0-12.git20100504.fc13.x86_64

NetworkManager --no-daemon --log-level=DEBUG

-- Original message: type=0x14 length=56 flags=REQUEST,ACK,ATOMIC
sequence-nr=1273466780 pid=4202530
NetworkManager[8226]: warn bluez error getting default adapter: The name
org.bluez was not provided by any .service files
NetworkManager[8226]: debug [1273466770.628023] [nm-netlink-monitor.c:117]
link_msg_handler(): netlink link message: iface idx 1 flags 0x10049
NetworkManager[8226]: debug [1273466770.628166] [nm-netlink-monitor.c:117]
link_msg_handler(): netlink link message: iface idx 2 flags 0x11043
NetworkManager[8226]: debug [1273466770.628277] [nm-netlink-monitor.c:117]
link_msg_handler(): netlink link message: iface idx 3 flags 0x1002
NetworkManager[8226]: info Activation (eth0) Stage 3 of 5 (IP Configure
Start) started...
NetworkManager[8226]: info Activation (eth0) Stage 4 of 5 (IP4 Configure
Get) scheduled...
NetworkManager[8226]: info Activation (eth0) Stage 3 of 5 (IP Configure
Start) complete.
NetworkManager[8226]: info Activation (eth0) Stage 4 of 5 (IP4 Configure
Get) started...
NetworkManager[8226]: info Activation (eth0) Stage 5 of 5 (IP Configure
Commit) scheduled...
NetworkManager[8226]: info Activation (eth0) Stage 4 of 5 (IP4 Configure
Get) complete.
NetworkManager[8226]: info Activation (eth0) Stage 5 of 5 (IP Configure
Commit) started...
NetworkManager[8226]: info (eth0): device state change: 7 - 8 (reason 0)
NetworkManager[8226]: info Policy set 'System eth0' (eth0) as default for
IPv4 routing and DNS.
NetworkManager[8226]: info Activation (eth0) successful, device activated.
NetworkManager[8226]: info Activation (eth0) Stage 5 of 5 (IP Configure
Commit) complete.
NetworkManager[8226]: debug [1273466778.926831] [nm-netlink-monitor.c:117]
link_msg_handler(): netlink link message: iface idx 7 flags 0x1002
NetworkManager[8226]: debug [1273466778.937908] [nm-udev-manager.c:477]
handle_uevent(): UDEV event: action 'add' subsys 'net' device 'pan0'
NetworkManager[8226]: warn /sys/devices/virtual/net/pan0: couldn't
determine device driver; ignoring...
NetworkManager[8226]: debug [1273466785.853458] [nm-udev-manager.c:477]
handle_uevent(): UDEV event: action 'change' subsys 'rfkill' device
'rfkill0'
NetworkManager[8226]: info ignoring modem 'rfcomm0' (no associated
Bluetooth device)



modem-manager --debug:

** Message: Loaded plugin Option High-Speed
** Message: Loaded plugin Ericsson MBM
** Message: Loaded plugin Huawei
** Message: Loaded plugin Generic
** Message: Loaded plugin MotoC
** Message: Loaded plugin AnyData
** Message: Loaded plugin Sierra
** Message: Loaded plugin Nokia
** Message: Loaded plugin Option
** Message: Loaded plugin ZTE
** Message: Loaded plugin Novatel
** Message: Loaded plugin Longcheer
** Message: Loaded plugin Gobi
** (modem-manager:8225): DEBUG: (tty/ttyS1): port's parent platform driver
is not whitelisted
** (modem-manager:8225): DEBUG: (tty/ttyS2): port's parent platform driver
is not whitelisted
** (modem-manager:8225): DEBUG: (tty/ttyS3): port's parent platform driver
is not whitelisted
** (modem-manager:8225): DEBUG: (tty/ttyS0): could not get port's parent
device
** (modem-manager:8225): DEBUG: (net/vboxnet0): could not get port's parent
device
** (modem-manager:8225): DEBUG: (net/pan0): could not get port's parent
device
** (modem-manager:8225): DEBUG: (tty/rfcomm0): could not get port's parent
device
** Message: (rfcomm0) opening serial device...
** (modem-manager:8225): DEBUG: 1273466797.123682 (rfcomm0) device open
count is 1 (open)
** (modem-manager:8225): DEBUG: (rfcomm0): probe requested by plugin
'Generic'
** (modem-manager:8225): DEBUG: 1273466797.222951 (rfcomm0): --
'AT+GCAPCR'
** (modem-manager:8225): DEBUG: 1273466798.23952 (rfcomm0): --
'AT+GCAPCRCRLF+GCAP: +CGSM,+DS,+WCRLFCRLFOKCRLF'
** (modem-manager:8225): DEBUG: 1273466798.24144 (rfcomm0) device open
count is 0 (close)
** Message: (rfcomm0) closing serial device...
** Message: (rfcomm0) type primary claimed by
/sys/devices/pci:00/:00:13.0/usb5/5-1
** Message: (rfcomm0) opening serial device...
** (modem-manager:8225): DEBUG: 1273466798.25980 (rfcomm0) device open
count

Re: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13 Beta

[Bastien Nocera]

On Mon, 2010-05-10 at 12:54 +0800, Ascanio Alba wrote:
 Hi,
 
  I have a bluetooth DUN device (/dev/rfcomm0) exported by
 modem-manager but being ignored by NetworkManager.
 This is on Fedora 13 Beta, latest updates-testing. I was getting some
 SELinux denials but did an audit2allow to remove that variable from
 the system.
 
 blueman attaches to the DUN service.
 modem-manager sees and exports the device, but NM ignores it.
 
 Version: NetworkManager-0.8.0-12.git20100504.fc13.x86_64

Don't use blueman to set up DUN, use the wizard in gnome-bluetooth
instead (you'll need to re-pair your device to do that, and it should
ask you a question once setup).

Blueman's way of setting up rfcomm was always hacky, and is now
out-of-date.

Cheers

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13 Beta

[Ascanio Alba]

I tried without blueman and got a similar error message.

I disabled blueman and went via the  gnome-bluetooth wizard to setup new
device.
I reached Access Internet using your mobile phone (DUN)
Got Detecting phone configuration...
MM seems to detect the 3G phone and exported it but NM rejects. Then MM
removes the device.
I tried this on another system  but even worse gnome bluetooth wizard
ABRTing.

NM reports:
NetworkManager[14671]: info ignoring modem 'rfcomm0' (no associated
Bluetooth device)


MM reports:

** (modem-manager:14420): DEBUG: (tty/rfcomm0): could not get port's parent
device
** Message: (rfcomm0) opening serial device...
** (modem-manager:14420): DEBUG: 1273497578.791149 (rfcomm0) device open
count is 1 (open)
** (modem-manager:14420): DEBUG: (rfcomm0): probe requested by plugin
'Generic'
** (modem-manager:14420): DEBUG: 1273497578.890504 (rfcomm0): --
'AT+GCAPCR'
** (modem-manager:14420): DEBUG: 1273497579.691510 (rfcomm0): --
'AT+GCAPCRCRLF+GCAP: +CGSM,+DS,+WCRLFCRLFOKCRLF'
** (modem-manager:14420): DEBUG: 1273497579.691700 (rfcomm0) device open
count is 0 (close)
** Message: (rfcomm0) closing serial device...
** Message: (rfcomm0) type primary claimed by
/sys/devices/pci:00/:00:13.0/usb5/5-2
** Message: (rfcomm0) opening serial device...
** (modem-manager:14420): DEBUG: 1273497579.692679 (rfcomm0) device open
count is 1 (open)
** Message: (Generic): GSM modem
/sys/devices/pci:00/:00:13.0/usb5/5-2 claimed port rfcomm0
** (modem-manager:14420): DEBUG: Added modem
/sys/devices/pci:00/:00:13.0/usb5/5-2
** (modem-manager:14420): DEBUG: (tty/rfcomm0): outstanding support task
prevents export of /sys/devices/pci:00/:00:13.0/usb5/5-2
** (modem-manager:14420): DEBUG: 1273497579.692956 (rfcomm0): --
'AT+CPIN?CR'
** (modem-manager:14420): DEBUG: 1273497579.702872 (rfcomm0): -- 'AT+'
** (modem-manager:14420): DEBUG: 1273497579.703528 (rfcomm0): -- 'C'
** (modem-manager:14420): DEBUG: 1273497579.707549 (rfcomm0): -- 'P'
** (modem-manager:14420): DEBUG: 1273497579.708539 (rfcomm0): -- 'I'
** (modem-manager:14420): DEBUG: 1273497579.710546 (rfcomm0): -- 'N'
** (modem-manager:14420): DEBUG: 1273497579.711523 (rfcomm0): -- '?'
** (modem-manager:14420): DEBUG: 1273497579.713537 (rfcomm0): --
'CRCRLF+CPIN: READYCRLFCRLFOKCRLF'
** (modem-manager:14420): DEBUG: 1273497579.713673 (rfcomm0) device open
count is 0 (close)
** Message: (rfcomm0) closing serial device...
** (modem-manager:14420): DEBUG: Exported modem
/sys/devices/pci:00/:00:13.0/usb5/5-2 as
/org/freedesktop/ModemManager/Modems/2
** (modem-manager:14420): DEBUG: (/org/freedesktop/ModemManager/Modems/2):
data port is rfcomm0
** (modem-manager:14420): DEBUG: Removed modem
/sys/devices/pci:00/:00:13.0/usb5/5-2
On Mon, May 10, 2010 at 6:16 PM, Bastien Nocera had...@hadess.net wrote:

 On Mon, 2010-05-10 at 12:54 +0800, Ascanio Alba wrote:
  Hi,
 
   I have a bluetooth DUN device (/dev/rfcomm0) exported by
  modem-manager but being ignored by NetworkManager.
  This is on Fedora 13 Beta, latest updates-testing. I was getting some
  SELinux denials but did an audit2allow to remove that variable from
  the system.
 
  blueman attaches to the DUN service.
  modem-manager sees and exports the device, but NM ignores it.
 
  Version: NetworkManager-0.8.0-12.git20100504.fc13.x86_64

 Don't use blueman to set up DUN, use the wizard in gnome-bluetooth
 instead (you'll need to re-pair your device to do that, and it should
 ask you a question once setup).

 Blueman's way of setting up rfcomm was always hacky, and is now
 out-of-date.

 Cheers


___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13 Beta

[Bastien Nocera]

On Mon, 2010-05-10 at 21:26 +0800, Ascanio Alba wrote:
 I tried without blueman and got a similar error message.
 
 
 I disabled blueman and went via the  gnome-bluetooth wizard to setup
 new device.
 I reached Access Internet using your mobile phone (DUN)
 Got Detecting phone configuration...
 MM seems to detect the 3G phone and exported it but NM rejects. Then
 MM removes the device.
 I tried this on another system  but even worse gnome bluetooth wizard
 ABRTing.

If the bluetooth wizard from gnome-bluetooth crashes, please file a bug.

Cheers


___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13 Beta

[Bastien Nocera]

On Mon, 2010-05-10 at 14:36 +0100, Bastien Nocera wrote:
 On Mon, 2010-05-10 at 21:26 +0800, Ascanio Alba wrote:
  I tried without blueman and got a similar error message.
  
  
  I disabled blueman and went via the  gnome-bluetooth wizard to setup
  new device.
  I reached Access Internet using your mobile phone (DUN)
  Got Detecting phone configuration...
  MM seems to detect the 3G phone and exported it but NM rejects. Then
  MM removes the device.
  I tried this on another system  but even worse gnome bluetooth wizard
  ABRTing.
 
 If the bluetooth wizard from gnome-bluetooth crashes, please file a bug.

My guess is that it's a duplicate of:
https://bugzilla.redhat.com/show_bug.cgi?id=590666

Which is a bug in NetworkManager's gnome-bluetooth plugin.

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

NetworkManager Ignoring rfcomm0 device (bluetooth DUN) on Fedora 13 Beta

[Ascanio Alba]

Hi,

 I have a bluetooth DUN device (/dev/rfcomm0) exported by modem-manager but
being ignored by NetworkManager.
This is on Fedora 13 Beta, latest updates-testing. I was getting some
SELinux denials but did an audit2allow to remove that variable from the
system.

blueman attaches to the DUN service.
modem-manager sees and exports the device, but NM ignores it.

Version: NetworkManager-0.8.0-12.git20100504.fc13.x86_64

NetworkManager --no-daemon --log-level=DEBUG

-- Original message: type=0x14 length=56 flags=REQUEST,ACK,ATOMIC
sequence-nr=1273466780 pid=4202530
NetworkManager[8226]: warn bluez error getting default adapter: The name
org.bluez was not provided by any .service files
NetworkManager[8226]: debug [1273466770.628023] [nm-netlink-monitor.c:117]
link_msg_handler(): netlink link message: iface idx 1 flags 0x10049
NetworkManager[8226]: debug [1273466770.628166] [nm-netlink-monitor.c:117]
link_msg_handler(): netlink link message: iface idx 2 flags 0x11043
NetworkManager[8226]: debug [1273466770.628277] [nm-netlink-monitor.c:117]
link_msg_handler(): netlink link message: iface idx 3 flags 0x1002
NetworkManager[8226]: info Activation (eth0) Stage 3 of 5 (IP Configure
Start) started...
NetworkManager[8226]: info Activation (eth0) Stage 4 of 5 (IP4 Configure
Get) scheduled...
NetworkManager[8226]: info Activation (eth0) Stage 3 of 5 (IP Configure
Start) complete.
NetworkManager[8226]: info Activation (eth0) Stage 4 of 5 (IP4 Configure
Get) started...
NetworkManager[8226]: info Activation (eth0) Stage 5 of 5 (IP Configure
Commit) scheduled...
NetworkManager[8226]: info Activation (eth0) Stage 4 of 5 (IP4 Configure
Get) complete.
NetworkManager[8226]: info Activation (eth0) Stage 5 of 5 (IP Configure
Commit) started...
NetworkManager[8226]: info (eth0): device state change: 7 - 8 (reason 0)
NetworkManager[8226]: info Policy set 'System eth0' (eth0) as default for
IPv4 routing and DNS.
NetworkManager[8226]: info Activation (eth0) successful, device activated.
NetworkManager[8226]: info Activation (eth0) Stage 5 of 5 (IP Configure
Commit) complete.
NetworkManager[8226]: debug [1273466778.926831] [nm-netlink-monitor.c:117]
link_msg_handler(): netlink link message: iface idx 7 flags 0x1002
NetworkManager[8226]: debug [1273466778.937908] [nm-udev-manager.c:477]
handle_uevent(): UDEV event: action 'add' subsys 'net' device 'pan0'
NetworkManager[8226]: warn /sys/devices/virtual/net/pan0: couldn't
determine device driver; ignoring...
NetworkManager[8226]: debug [1273466785.853458] [nm-udev-manager.c:477]
handle_uevent(): UDEV event: action 'change' subsys 'rfkill' device
'rfkill0'
NetworkManager[8226]: info ignoring modem 'rfcomm0' (no associated
Bluetooth device)



modem-manager --debug:

** Message: Loaded plugin Option High-Speed
** Message: Loaded plugin Ericsson MBM
** Message: Loaded plugin Huawei
** Message: Loaded plugin Generic
** Message: Loaded plugin MotoC
** Message: Loaded plugin AnyData
** Message: Loaded plugin Sierra
** Message: Loaded plugin Nokia
** Message: Loaded plugin Option
** Message: Loaded plugin ZTE
** Message: Loaded plugin Novatel
** Message: Loaded plugin Longcheer
** Message: Loaded plugin Gobi
** (modem-manager:8225): DEBUG: (tty/ttyS1): port's parent platform driver
is not whitelisted
** (modem-manager:8225): DEBUG: (tty/ttyS2): port's parent platform driver
is not whitelisted
** (modem-manager:8225): DEBUG: (tty/ttyS3): port's parent platform driver
is not whitelisted
** (modem-manager:8225): DEBUG: (tty/ttyS0): could not get port's parent
device
** (modem-manager:8225): DEBUG: (net/vboxnet0): could not get port's parent
device
** (modem-manager:8225): DEBUG: (net/pan0): could not get port's parent
device
** (modem-manager:8225): DEBUG: (tty/rfcomm0): could not get port's parent
device
** Message: (rfcomm0) opening serial device...
** (modem-manager:8225): DEBUG: 1273466797.123682 (rfcomm0) device open
count is 1 (open)
** (modem-manager:8225): DEBUG: (rfcomm0): probe requested by plugin
'Generic'
** (modem-manager:8225): DEBUG: 1273466797.222951 (rfcomm0): --
'AT+GCAPCR'
** (modem-manager:8225): DEBUG: 1273466798.23952 (rfcomm0): --
'AT+GCAPCRCRLF+GCAP: +CGSM,+DS,+WCRLFCRLFOKCRLF'
** (modem-manager:8225): DEBUG: 1273466798.24144 (rfcomm0) device open
count is 0 (close)
** Message: (rfcomm0) closing serial device...
** Message: (rfcomm0) type primary claimed by
/sys/devices/pci:00/:00:13.0/usb5/5-1
** Message: (rfcomm0) opening serial device...
** (modem-manager:8225): DEBUG: 1273466798.25980 (rfcomm0) device open
count is 1 (open)
** Message: (Generic): GSM modem
/sys/devices/pci:00/:00:13.0/usb5/5-1 claimed port rfcomm0
** (modem-manager:8225): DEBUG: Added modem
/sys/devices/pci:00/:00:13.0/usb5/5-1
** (modem-manager:8225): DEBUG: (tty/rfcomm0): outstanding support task
prevents export of /sys/devices/pci:00/:00:13.0/usb5/5-1
** (modem-manager:8225): DEBUG: 1273466798.26270 (rfcomm0): --
'AT+CPIN?CR'
** (modem-manager:8225): DEBUG

Re: Bluetooth ICS

[Dan Williams]

On Thu, 2010-04-08 at 23:53 +0200, Stéphane Maniaci wrote:
 Hi, 
 
 Sorry if this question has been asked before, but I got a little bit
 lost in my researches on the Internet.
 
 Is it possible to enable connection sharing via Bluetooth between two
 _computers_ ? One has an ethernet connection and a bluetooth dongle,
 the other only has bluetooth. Does the bluetooth spec implements such
 a possibility ?

Not quite yet, but we've got a feature request for it in bugzilla and
I've already spent some time thinking about it and discussing
implementation details with relevant people (Bastien, really).

The general idea is that you'd just check a share my internet
connection over bluetooth somewhere, which would poke NM to start up
sharing over bluetooth like any normal NM ICS works.

I have no idea when this would hit, since some of it depends on other UI
components like gnome-bluetooth or kde-bluetooth.

Dan


___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Bluetooth ICS

[Bastien Nocera]

On Thu, 2010-04-08 at 16:54 -0700, Dan Williams wrote:
 On Thu, 2010-04-08 at 23:53 +0200, Stéphane Maniaci wrote:
  Hi, 
  
  Sorry if this question has been asked before, but I got a little bit
  lost in my researches on the Internet.
  
  Is it possible to enable connection sharing via Bluetooth between two
  _computers_ ? One has an ethernet connection and a bluetooth dongle,
  the other only has bluetooth. Does the bluetooth spec implements such
  a possibility ?
 
 Not quite yet, but we've got a feature request for it in bugzilla and
 I've already spent some time thinking about it and discussing
 implementation details with relevant people (Bastien, really).
 
 The general idea is that you'd just check a share my internet
 connection over bluetooth somewhere, which would poke NM to start up
 sharing over bluetooth like any normal NM ICS works.
 
 I have no idea when this would hit, since some of it depends on other UI
 components like gnome-bluetooth or kde-bluetooth.

The code needed on the gnome-bluetooth side is one function, akin to the
one in the gnome-bluetooth plugin for nm-applet to switch on PAN.

It's more finding the time to write the NM code that's the problem ;)

In the meanwhile, you can use pand on your server. There's already
pretty good pages on how to do that. On the connecting side, you can
then use gnome-bluetooth to pair and enable the connection to that
machine.

Cheers

___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Bluetooth ICS

[Marcel Holtmann]

Hi Dan,

  Sorry if this question has been asked before, but I got a little bit
  lost in my researches on the Internet.
  
  Is it possible to enable connection sharing via Bluetooth between two
  _computers_ ? One has an ethernet connection and a bluetooth dongle,
  the other only has bluetooth. Does the bluetooth spec implements such
  a possibility ?
 
 Not quite yet, but we've got a feature request for it in bugzilla and
 I've already spent some time thinking about it and discussing
 implementation details with relevant people (Bastien, really).
 
 The general idea is that you'd just check a share my internet
 connection over bluetooth somewhere, which would poke NM to start up
 sharing over bluetooth like any normal NM ICS works.
 
 I have no idea when this would hit, since some of it depends on other UI
 components like gnome-bluetooth or kde-bluetooth.

actually this should not involve gnome-bluetooth or any Bluetooth UI
code at all. This should be a pure feature inside NetworkManager.

So for Bluetooth it does work a little bit different than for WiFi or
other technologies, because the profiles clearly define what needs to be
done. And there are qualification tests to ensure this.

The basic code in bluetoothd is present today, but we have to update the
D-Bus API to actually match reality. I have talked with Luiz about it
last time and I have the proposal here. Just need to push it and update
the code a little bit.

General idea is the following. NetworkManager has to create a bridge
interface and provide DHCP and DNS servers on this bridge. After that it
calls into bluetoothd via D-Bus and activates PAN server. Arguments are
the bridge interface name and some authentication details. Then if
someone connects over Bluetooth, a new bnepX networking interface will
be created and added to the bridge by bluetoothd. That is basically it.

And as a side note, nothing is stopping you to also use that bridge for
WiFi or anything else. However in that cases normally the bridge in
between is not required. With Bluetooth it actually is. Even if you can
potentially start many DHCP and DNS servers and point them individually
to every bnepX interface. I doesn't really follow the specification and
you lose the capabilities of link local support between the clients. And
we will not be exposing an API to access the individual bnepX interface
manually anyway. Especially since the bnepX namespace is shared between
clients and servers. In the end it is just an Ethernet emulation.

If you look at the uevent for Bluetooth BNEP interfaces these days, you
will see that they are clearly marked with DEVTYPE=bluetooth. And this
reminds me that we might need to add some sort of UUID=nap/panu field to
it to clearly distinguish the role of it. I have to look into this.

Regards

Marcel


___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: [PATCH] libnm-glib Bluetooth device correction

[Dan Williams]

On Tue, 2010-01-12 at 14:43 +0100, Jirka Klimes wrote:
 Hello,
 libnm-glib/nm-device-bt.c typo:
 
 uses NM_DBUS_INTERFACE_DEVICE_WIRED interface instead of  
 NM_DBUS_INTERFACE_DEVICE_BLUETOOTH

Committed, thanks!

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

[PATCH] libnm-glib Bluetooth device correction

[Jirka Klimes]

Hello,
libnm-glib/nm-device-bt.c typo:

uses NM_DBUS_INTERFACE_DEVICE_WIRED interface instead of  
NM_DBUS_INTERFACE_DEVICE_BLUETOOTH

Jirka
diff --git a/libnm-glib/nm-device-bt.c b/libnm-glib/nm-device-bt.c
index 5792add..bb1ff66 100644
--- a/libnm-glib/nm-device-bt.c
+++ b/libnm-glib/nm-device-bt.c
@@ -95,7 +95,7 @@ nm_device_bt_get_hw_address (NMDeviceBt *device)
 	priv = NM_DEVICE_BT_GET_PRIVATE (device);
 	if (!priv-hw_address) {
 		priv-hw_address = _nm_object_get_string_property (NM_OBJECT (device),
-		  NM_DBUS_INTERFACE_DEVICE_WIRED,
+		  NM_DBUS_INTERFACE_DEVICE_BLUETOOTH,
 		  DBUS_PROP_HW_ADDRESS);
 	}
 
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Networkmanager + Bluetooth

[van Schelve]

 Hi.
 
 After some more testing I found out that NM is able to bring up the
 connection when following these steps:
 
 1. sudo rfcomm connect hci0 bdaddr
 2. In nm-applet you can now start the already configured connection
 
 My questions are now:
 - Is it possible to lable the bluetooth based connections as
Bluetooth
 or whatever.
 
 They are, if correctly configured.  This already happens for PAN
 connections, but DUN connections are not yet natively supported even
 though they will work if you create the rfcomm connection underneath NM.
 DUN is slated for the 0.8.1 release.
 

Do you have a timeline for 0.8.1? Do you see a chance that this will be
available until March 2010?

 - why do i need to open the rfcomm connection? Isn't it enought to bind
 to
 the mobile?
 
 You wont' need to do this after real DUN support lands.  NM will do it
 automatically for you.
 

Interesting.

Best regards and happy new year to all of you!

 Dan
 
 
 -- HG
 
 
  I am currently looking for way to use bluetooth based dial up
together
  with networkmanager.
  
  Can someone give me an overview? What I'm looking for is
  
  1. simple dialog for the initial pairing
  2. an entry in nm-applet to bring up or disconnect the connection
  3. I need to configure the apn + chap credentials.
 ___
 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: Networkmanager + Bluetooth

[Dan Williams]

On Fri, 2009-12-18 at 21:21 +0100, Hans-Gerd van Schelve wrote:
 Hi.
 
 After some more testing I found out that NM is able to bring up the
 connection when following these steps:
 
 1. sudo rfcomm connect hci0 bdaddr
 2. In nm-applet you can now start the already configured connection
 
 My questions are now:
 - Is it possible to lable the bluetooth based connections as Bluetooth
 or whatever.

They are, if correctly configured.  This already happens for PAN
connections, but DUN connections are not yet natively supported even
though they will work if you create the rfcomm connection underneath NM.
DUN is slated for the 0.8.1 release.

 - why do i need to open the rfcomm connection? Isn't it enought to bind to
 the mobile?

You wont' need to do this after real DUN support lands.  NM will do it
automatically for you.

Dan


 -- HG
 
 
  I am currently looking for way to use bluetooth based dial up together
  with networkmanager.
  
  Can someone give me an overview? What I'm looking for is
  
  1. simple dialog for the initial pairing
  2. an entry in nm-applet to bring up or disconnect the connection
  3. I need to configure the apn + chap credentials.
 ___
 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: Networkmanager + Bluetooth

[van Schelve]

Hmm... really nobody here who can help?

 
 After some more testing I found out that NM is able to bring up the
 connection when following these steps:
 
 1. sudo rfcomm connect hci0 bdaddr
 2. In nm-applet you can now start the already configured connection
 
 My questions are now:
 - Is it possible to lable the bluetooth based connections as Bluetooth
 or whatever.
 - why do i need to open the rfcomm connection? Isn't it enought to bind
to
 the mobile?
 
 -- HG
 
 
 I am currently looking for way to use bluetooth based dial up together
 with networkmanager.
 
 Can someone give me an overview? What I'm looking for is
 
 1. simple dialog for the initial pairing
 2. an entry in nm-applet to bring up or disconnect the connection
 3. I need to configure the apn + chap credentials.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Networkmanager + Bluetooth

[Pietro Battiston]

Il giorno mar, 22/12/2009 alle 20.33 +0100, van Schelve ha scritto:
 Hmm... really nobody here who can help?

PAN is supported, DUN is not but it seems we're not far from it, I
personally am able to use DUN through blueman, all that seems cryptic to
you in this words will be perfectly clear once you do some search in the
archives of the mailing list, and if you had searched before you would
have known already.

Pietro


 
  
  After some more testing I found out that NM is able to bring up the
  connection when following these steps:
  
  1. sudo rfcomm connect hci0 bdaddr
  2. In nm-applet you can now start the already configured connection
  
  My questions are now:
  - Is it possible to lable the bluetooth based connections as Bluetooth
  or whatever.
  - why do i need to open the rfcomm connection? Isn't it enought to bind
 to
  the mobile?
  
  -- HG
  
  
  I am currently looking for way to use bluetooth based dial up together
  with networkmanager.
  
  Can someone give me an overview? What I'm looking for is
  
  1. simple dialog for the initial pairing
  2. an entry in nm-applet to bring up or disconnect the connection
  3. I need to configure the apn + chap credentials.
 ___
 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

Networkmanager + Bluetooth

[van Schelve]

Hello,

I am currently looking for way to use bluetooth based dial up together
with networkmanager.

Can someone give me an overview? What I'm looking for is

1. simple dialog for the initial pairing
2. an entry in nm-applet to bring up or disconnect the connection
3. I need to configure the apn + chap credentials.

Thanks!
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Connection through bluetooth phones

[Gianluca Sforna]

I am looking for some info about how Fedora 12 stands wrt allowing 3G
internet connection through a mobile phone.
In particular, I tried with my Nokia 6210 Classic and the last step in
the wizard shown at:

http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/

surely did not include the Access the Internet using your mobile phone button.

Any help is appreciated

-- 
Gianluca Sforna

http://morefedora.blogspot.com
http://www.linkedin.com/in/gianlucasforna
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Connection through bluetooth phones

[Bastien Nocera]

On Mon, 2009-11-09 at 14:22 +0100, Gianluca Sforna wrote:
 I am looking for some info about how Fedora 12 stands wrt allowing 3G
 internet connection through a mobile phone.
 In particular, I tried with my Nokia 6210 Classic and the last step in
 the wizard shown at:
 
 http://blogs.gnome.org/dcbw/2009/07/10/unwire-with-networkmanager/
 
 surely did not include the Access the Internet using your mobile phone 
 button.
 
 Any help is appreciated

Attach the output of bluetooth-properties -d. My guess is that your
phone doesn't have PAN support, and there's currently no DUN support in
NetworkManager (though Dan is working on it in a branch).

Cheers


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Connection through bluetooth phones

[Gianluca Sforna]

On Mon, Nov 9, 2009 at 2:32 PM, Bastien Nocera had...@hadess.net wrote:

 Attach the output of bluetooth-properties -d. My guess is that your
 phone doesn't have PAN support, and there's currently no DUN support in
 NetworkManager (though Dan is working on it in a branch).

Device: Tweety (00:1B:AF:6F:39:50)
D-Bus Path: /org/bluez/1423/hci0/dev_00_1B_AF_6F_39_50
Type: Phone Icon: phone
Paired: True Trusted: True Connected: False
UUIDs: SyncMLClient DialupNetworking OBEXObjectPush OBEXFileTransfer
AudioSource A/V_RemoteControlTarget A/V_RemoteControl Headset_-_AG
HandsfreeAudioGateway SIM_Access

-- 
Gianluca Sforna

http://morefedora.blogspot.com
http://www.linkedin.com/in/gianlucasforna
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Connection through bluetooth phones

[Bastien Nocera]

On Mon, 2009-11-09 at 14:40 +0100, Gianluca Sforna wrote:
 On Mon, Nov 9, 2009 at 2:32 PM, Bastien Nocera had...@hadess.net wrote:
 
  Attach the output of bluetooth-properties -d. My guess is that your
  phone doesn't have PAN support, and there's currently no DUN support in
  NetworkManager (though Dan is working on it in a branch).
 
 Device: Tweety (00:1B:AF:6F:39:50)
   D-Bus Path: /org/bluez/1423/hci0/dev_00_1B_AF_6F_39_50
   Type: Phone Icon: phone
   Paired: True Trusted: True Connected: False
   UUIDs: SyncMLClient DialupNetworking OBEXObjectPush OBEXFileTransfer
 AudioSource A/V_RemoteControlTarget A/V_RemoteControl Headset_-_AG
 HandsfreeAudioGateway SIM_Access

Yep, no PAN support. You'll need to wait for DUN support to be merged
into NetworkManager proper then.

Cheers

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Connection through bluetooth phones

[Gianluca Sforna]

On Mon, Nov 9, 2009 at 3:04 PM, Bastien Nocera had...@hadess.net wrote:
 On Mon, 2009-11-09 at 14:40 +0100, Gianluca Sforna wrote:
 On Mon, Nov 9, 2009 at 2:32 PM, Bastien Nocera had...@hadess.net wrote:
 
  Attach the output of bluetooth-properties -d. My guess is that your
  phone doesn't have PAN support, and there's currently no DUN support in
  NetworkManager (though Dan is working on it in a branch).

 Device: Tweety (00:1B:AF:6F:39:50)
       D-Bus Path: /org/bluez/1423/hci0/dev_00_1B_AF_6F_39_50
       Type: Phone Icon: phone
       Paired: True Trusted: True Connected: False
       UUIDs: SyncMLClient DialupNetworking OBEXObjectPush OBEXFileTransfer
 AudioSource A/V_RemoteControlTarget A/V_RemoteControl Headset_-_AG
 HandsfreeAudioGateway SIM_Access

 Yep, no PAN support. You'll need to wait for DUN support to be merged
 into NetworkManager proper then.

Ok, so with PAN devices it would have worked as advertised?

Anyway, thank you very much for the great work on BT stuff!


-- 
Gianluca Sforna

http://morefedora.blogspot.com
http://www.linkedin.com/in/gianlucasforna
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Connection through bluetooth phones

[Bastien Nocera]

On Mon, 2009-11-09 at 15:08 +0100, Gianluca Sforna wrote:
 On Mon, Nov 9, 2009 at 3:04 PM, Bastien Nocera had...@hadess.net wrote:
  On Mon, 2009-11-09 at 14:40 +0100, Gianluca Sforna wrote:
  On Mon, Nov 9, 2009 at 2:32 PM, Bastien Nocera had...@hadess.net wrote:
  
   Attach the output of bluetooth-properties -d. My guess is that your
   phone doesn't have PAN support, and there's currently no DUN support in
   NetworkManager (though Dan is working on it in a branch).
 
  Device: Tweety (00:1B:AF:6F:39:50)
D-Bus Path: /org/bluez/1423/hci0/dev_00_1B_AF_6F_39_50
Type: Phone Icon: phone
Paired: True Trusted: True Connected: False
UUIDs: SyncMLClient DialupNetworking OBEXObjectPush OBEXFileTransfer
  AudioSource A/V_RemoteControlTarget A/V_RemoteControl Headset_-_AG
  HandsfreeAudioGateway SIM_Access
 
  Yep, no PAN support. You'll need to wait for DUN support to be merged
  into NetworkManager proper then.
 
 Ok, so with PAN devices it would have worked as advertised?

For comparison, this is the output on my Sony Ericsson k850i:
UUIDs: SyncMLClient SerialPort DialupNetworking IrMCSync OBEXObjectPush
OBEXFileTransfer AudioSource A/V_RemoteControlTarget A/V_RemoteControl
Headset_-_AG PANU NAP HandsfreeAudioGateway HumanInterfaceDeviceService
Phonebook_Access_-_PSE SEMC HLA SEMC Watch Phone 

Note the PANU profile.

 Anyway, thank you very much for the great work on BT stuff!

Thanks to Dan for fixing up my early, incomplete code :)

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Connection through bluetooth phones

[Pietro Battiston]

Il giorno lun, 09/11/2009 alle 15.08 +0100, Gianluca Sforna ha scritto:
 On Mon, Nov 9, 2009 at 3:04 PM, Bastien Nocera had...@hadess.net wrote:
  On Mon, 2009-11-09 at 14:40 +0100, Gianluca Sforna wrote:
  On Mon, Nov 9, 2009 at 2:32 PM, Bastien Nocera had...@hadess.net wrote:
  
   Attach the output of bluetooth-properties -d. My guess is that your
   phone doesn't have PAN support, and there's currently no DUN support in
   NetworkManager (though Dan is working on it in a branch).
 
  Device: Tweety (00:1B:AF:6F:39:50)
D-Bus Path: /org/bluez/1423/hci0/dev_00_1B_AF_6F_39_50
Type: Phone Icon: phone
Paired: True Trusted: True Connected: False
UUIDs: SyncMLClient DialupNetworking OBEXObjectPush OBEXFileTransfer
  AudioSource A/V_RemoteControlTarget A/V_RemoteControl Headset_-_AG
  HandsfreeAudioGateway SIM_Access
 
  Yep, no PAN support. You'll need to wait for DUN support to be merged
  into NetworkManager proper then.
 
 Ok, so with PAN devices it would have worked as advertised?
 
 Anyway, thank you very much for the great work on BT stuff!


FYI, in the meanwhile blueman+networkmanaer do the job for me (Ubuntu
Karmic, non-PAN mobile).

bye

Pietro

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

[PATCH] ModemManager: Don't send AT+CFUN to bluetooth modems

[Valmantas Palikša]

I think this will cause less problems with bluetooth DUN.
diff --git a/src/mm-generic-gsm.c b/src/mm-generic-gsm.c
index 3becf7f..85b3281 100644
--- a/src/mm-generic-gsm.c
+++ b/src/mm-generic-gsm.c
@@ -1925,10 +1925,16 @@ get_property (GObject *object, guint prop_id,
 g_value_set_boolean (value, priv-valid);
 break;
 case MM_GENERIC_GSM_PROP_POWER_UP_CMD:
-g_value_set_string (value, +CFUN=1);
+if(strcmp(priv-driver, bluetooth) == 0)
+g_value_set_string (value, );
+else
+g_value_set_string (value, +CFUN=1);
 break;
 case MM_GENERIC_GSM_PROP_POWER_DOWN_CMD:
-g_value_set_string (value, +CFUN=0);
+if(strcmp(priv-driver, bluetooth) == 0)
+g_value_set_string (value, );
+else
+g_value_set_string (value, +CFUN=0);
 break;
 case MM_GENERIC_GSM_PROP_INIT_CMD:
 g_value_set_string (value, Z E0 V1 X4 C1 +CMEE=1);
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: gnome-bluetooth integration

[Dan Williams]

On Fri, 2009-08-07 at 17:02 -0700, Marcel Holtmann wrote:
 Hi Dan,
 
NAP means that the iPhone would access the Internet using
   your computer,
not your computer accessing the internet through your
   iPhone...
   
   
   no, if the phone tells you NAP, then this means that the
   iPhone acts as
   Network Access Point. The computer connecting to the phone
   would be the
   PANU. This patch is 100% correct.
   
   Anyhow it works flawlesly for me with gnome-bluetooth 2.27.8, 
   bluez 4.46 and current git versions of NM and nm-applet and
   iPhone 3G OS 3.0.
   Thanks for that - it makes my life a whole lot easier.
  
  Awesome, great to know!  I just pushed the fix to the GUI bits that
  should fix your original problem.  We got everything right in NM, but
  the gnome-bluetooth plugin wasn't checking the right capability bit.
 
 I still don't understand why gnome-bluetooth is involved in the PAN
 support for NM? To be honest NM could pick up paired devices that allow
 PAN connection directly without the round-trip via the UI. I must be
 missing something here since I don't get it.

The original idea was that we weren't going to show/expose bluetooth
devices in the UI that didn't have some NM config created for them.
Partially to keep the menu and device list less cluttered by any random
BT device you had paired with but weren't actually using for networking
support.  Since we can't scan for the devices, we don't actually know
they are available to use, and thus we have to show them in the menu all
the time.  So showing every paired device that could do PAN or DUN in
the menu irregardless of whether you wanted to use it for PAN or DUN
seemed a bit wrong.  But it's true that most people will have only a few
BT devices anyway.

Having actually implemented this now though, we probably don't need
gnome-bluetooth for the PAN bits, you're right.  We do, however, need
gnome-bluetooth for the DUN bits so we run our mobile broadband wizard
when you set up the PAN connection.

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: gnome-bluetooth integration

[Marcel Holtmann]

Hi Dan,

   NAP means that the iPhone would access the Internet using
  your computer,
   not your computer accessing the internet through your
  iPhone...
  
  
  no, if the phone tells you NAP, then this means that the
  iPhone acts as
  Network Access Point. The computer connecting to the phone
  would be the
  PANU. This patch is 100% correct.
  
  Anyhow it works flawlesly for me with gnome-bluetooth 2.27.8, 
  bluez 4.46 and current git versions of NM and nm-applet and
  iPhone 3G OS 3.0.
  Thanks for that - it makes my life a whole lot easier.
 
 Awesome, great to know!  I just pushed the fix to the GUI bits that
 should fix your original problem.  We got everything right in NM, but
 the gnome-bluetooth plugin wasn't checking the right capability bit.

I still don't understand why gnome-bluetooth is involved in the PAN
support for NM? To be honest NM could pick up paired devices that allow
PAN connection directly without the round-trip via the UI. I must be
missing something here since I don't get it.

Regards

Marcel


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: gnome-bluetooth integration

[Bastien Nocera]

On Thu, 2009-08-06 at 16:30 +0200, Andrzej Wytyczak-Partyka wrote:
 Hi guys,
 please consider this patch, which enables iPhone support in the
 gnome-bluetooth plugin.
 The iPhone reports a NAP service, instead of a PANU service, but it
 works - after connecting
 to that service through NetworkManager a connection is setup and
 operational.

NAP means that the iPhone would access the Internet using your computer,
not your computer accessing the internet through your iPhone...

If the SDP record is wrong, then it needs to be fixed in bluez, or
gnome-bluetooth, not worked around in NetworkManager.

Cheers

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: gnome-bluetooth integration

[Andrzej Wytyczak-Partyka]

On Thu, Aug 6, 2009 at 5:04 PM, Bastien Nocera had...@hadess.net wrote:

 On Thu, 2009-08-06 at 16:30 +0200, Andrzej Wytyczak-Partyka wrote:
  Hi guys,
  please consider this patch, which enables iPhone support in the
  gnome-bluetooth plugin.
  The iPhone reports a NAP service, instead of a PANU service, but it
  works - after connecting
  to that service through NetworkManager a connection is setup and
  operational.

 NAP means that the iPhone would access the Internet using your computer,
 not your computer accessing the internet through your iPhone...

 If the SDP record is wrong,


It seems that way.

then it needs to be fixed in bluez, or
 gnome-bluetooth, not worked around in NetworkManager.


ok, I'll post to their list.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: gnome-bluetooth integration

[Marcel Holtmann]

Hi Bastien,

  please consider this patch, which enables iPhone support in the
  gnome-bluetooth plugin.
  The iPhone reports a NAP service, instead of a PANU service, but it
  works - after connecting
  to that service through NetworkManager a connection is setup and
  operational.
 
 NAP means that the iPhone would access the Internet using your computer,
 not your computer accessing the internet through your iPhone...

no, if the phone tells you NAP, then this means that the iPhone acts as
Network Access Point. The computer connecting to the phone would be the
PANU. This patch is 100% correct.

I would actually go that far to remove the PANU check. Since a PANU is
not required to have a DHCP server running. It is suppose to use link
local addresses.

Regards

Marcel


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: gnome-bluetooth integration

[Andrzej Wytyczak-Partyka]

On Thu, Aug 6, 2009 at 9:07 PM, Marcel Holtmann mar...@holtmann.org wrote:

 Hi Bastien,

  NAP means that the iPhone would access the Internet using your computer,
  not your computer accessing the internet through your iPhone...

 no, if the phone tells you NAP, then this means that the iPhone acts as
 Network Access Point. The computer connecting to the phone would be the
 PANU. This patch is 100% correct.


Anyhow it works flawlesly for me with gnome-bluetooth 2.27.8,
bluez 4.46 and current git versions of NM and nm-applet and
iPhone 3G OS 3.0.
Thanks for that - it makes my life a whole lot easier.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Using a mobile phone via Bluetooth

[Dan Williams]

On Mon, 2009-07-06 at 23:52 -0400, Ryan Novosielski wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Dan Williams wrote:
  On Mon, 2009-07-06 at 12:54 -0400, Ryan Novosielski wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  Brian Morrison wrote:
  Saw this on the Planet Fedora RSS feed today:
 
  http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/
 
  Does this look the sort of thing where a more sane approach could be
  added to NM or udev to cope with a wider range of phones without
  needing to create user rules?
  I notice this solution mentions GSM. Is there any reason this should not
  work for a CDMA phone?
  
  As long as the phone responds to AT+GCAP with IS-707 the probe will
  tag the phone as a CDMA device and you should be able to use it with a
  CDMA connection like any normal data card or USB-attached CDMA phone.
  NM shouldn't be confused by the mis-tagged HAL entry in the linked
  dialup-bluetooth.py because it prefers the probed capabilities over
  static ones in HAL.
 
 So I actually got this working where an rfcomm1 shows up in the NM
 Plasma Applet (I assume that I'm probably supposed to stop setting up
 rfcomm0 manually with /etc/bluetooth/rfcomm.conf). However, nothing I do
 seems to make it want to actually connect. At first the rfcomm1 shows up
 and claims to be looking for an IP address. Then it fails. It's not
 clear that it ever attempts to dialup via PPP, even though I have a
 connection configured. Is there some way to troubleshoot this?

Sounds like more on the Bluetooth side, of course.  Does your phone do
anything when NM tries to bring the connection up?  Mine usually asks me
whether I want to allow the computer to connect, or it'll show an icon
saying a computer is connected.  In any case, this is exactly why this
method is a hack, and why we want the real solution...

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Using a mobile phone via Bluetooth

[Ryan Novosielski]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dan Williams wrote:
 On Mon, 2009-07-06 at 23:52 -0400, Ryan Novosielski wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Dan Williams wrote:
 On Mon, 2009-07-06 at 12:54 -0400, Ryan Novosielski wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Brian Morrison wrote:
 Saw this on the Planet Fedora RSS feed today:

 http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/

 Does this look the sort of thing where a more sane approach could be
 added to NM or udev to cope with a wider range of phones without
 needing to create user rules?
 I notice this solution mentions GSM. Is there any reason this should not
 work for a CDMA phone?
 As long as the phone responds to AT+GCAP with IS-707 the probe will
 tag the phone as a CDMA device and you should be able to use it with a
 CDMA connection like any normal data card or USB-attached CDMA phone.
 NM shouldn't be confused by the mis-tagged HAL entry in the linked
 dialup-bluetooth.py because it prefers the probed capabilities over
 static ones in HAL.
 So I actually got this working where an rfcomm1 shows up in the NM
 Plasma Applet (I assume that I'm probably supposed to stop setting up
 rfcomm0 manually with /etc/bluetooth/rfcomm.conf). However, nothing I do
 seems to make it want to actually connect. At first the rfcomm1 shows up
 and claims to be looking for an IP address. Then it fails. It's not
 clear that it ever attempts to dialup via PPP, even though I have a
 connection configured. Is there some way to troubleshoot this?
 
 Sounds like more on the Bluetooth side, of course.  Does your phone do
 anything when NM tries to bring the connection up?  Mine usually asks me
 whether I want to allow the computer to connect, or it'll show an icon
 saying a computer is connected.  In any case, this is exactly why this
 method is a hack, and why we want the real solution...

My phone is already paired because I use it all the time from kppp, but
would love to do it this way instead. I believe there is some activity
on the phone but will have to take a look at it again. I'm assuming
there's some way to run NM in a mode where I can see exactly what it
thinks it's doing? If something fails, it would be good to see what so I
can tweak if possible.

- --
  _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Systems Programmer II
 |$| |__| |  | |__/ | \| _| |novos...@umdnj.edu - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/CST - NJMS Medical Science Bldg - C630
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpTcaEACgkQmb+gadEcsb6XjACbBHvQm8tCzE9Tn5lewIGpjiY3
v78Anj05wTaRnJalDWhMzhCi1OisOwll
=DNX0
-END PGP SIGNATURE-
begin:vcard
fn:Ryan Novosielski
n:Novosielski;Ryan
org:UMDNJ;IST/AST
adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103
email;internet:novos...@umdnj.edu
title:Systems Programmer II
tel;work:(973) 972-0922
tel;fax:(973) 972-7412
tel;pager:(866) 20-UMDNJ
x-mozilla-html:FALSE
version:2.1
end:vcard

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Using a mobile phone via Bluetooth

[david . daniel . smith]

On Tue, Jul 7, 2009 at 3:18 AM, Dan Williamsd...@redhat.com wrote:

On Mon, 2009-07-06 at 12:54 -0400, Ryan Novosielski wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Brian Morrison wrote:
 Saw this on the Planet Fedora RSS feed today:

 
http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/

 Does this look the sort of thing where a more sane approach could be
 added to NM or udev to cope with a wider range of phones without
 needing to create user rules?

I notice this solution mentions GSM. Is there any reason this should not
work for a CDMA phone?


As long as the phone responds to AT+GCAP with IS-707 the probe will
tag the phone as a CDMA device and you should be able to use it with a
CDMA connection like any normal data card or USB-attached CDMA phone.
NM shouldn't be confused by the mis-tagged HAL entry in the linked
dialup-bluetooth.py because it prefers the probed capabilities over
static ones in HAL.



I have an emobile (Japanese provider) CDMA device that responds with +GCAP: 
+CGSM,+DS,+ES but not IS-707 and so only gets resolved as GSM by NM, but in 
reality it's a CDMA-only device and works fine when just dialed with pppd. What 
should I do in this situation? Also an earlier model from the same provider 
that was also CDMA failed to respond at all to the AT+GCAP (and subsequent) 
commands from nm-modem-probe. Is the device not following the spec or is NM too 
strict?


signature.asc
Description: OpenPGP digital signature
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Using a mobile phone via Bluetooth

[Dan Williams]

On Wed, 2009-07-08 at 01:13 +0900, david.daniel.sm...@gmail.com wrote:
 On Tue, Jul 7, 2009 at 3:18 AM, Dan Williamsd...@redhat.com wrote:
  On Mon, 2009-07-06 at 12:54 -0400, Ryan Novosielski wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  Brian Morrison wrote:
   Saw this on the Planet Fedora RSS feed today:
  
   http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/
  
   Does this look the sort of thing where a more sane approach could be
   added to NM or udev to cope with a wider range of phones without
   needing to create user rules?
 
  I notice this solution mentions GSM. Is there any reason this should not
  work for a CDMA phone?
 
  As long as the phone responds to AT+GCAP with IS-707 the probe will
  tag the phone as a CDMA device and you should be able to use it with a
  CDMA connection like any normal data card or USB-attached CDMA phone.
  NM shouldn't be confused by the mis-tagged HAL entry in the linked
  dialup-bluetooth.py because it prefers the probed capabilities over
  static ones in HAL.
 
 
 I have an emobile (Japanese provider) CDMA device that responds with +GCAP: 
 +CGSM,+DS,+ES but not IS-707 and so only gets resolved as GSM by NM, but in 
 reality it's a CDMA-only device and works fine when just dialed with pppd. 
 What should I do in this situation? Also an earlier model from the same 
 provider that was also CDMA failed to respond at all to the AT+GCAP (and 
 subsequent) commands from nm-modem-probe. Is the device not following the 
 spec or is NM too strict?

Emobile appears to be a GSM carrier, they appear to provide HSPA-based
3G services.  You may be confusing CDMA with W-CDMA.  W-CDMA (Wideband
CDMA) is the GSM-based 3G standard but shares a technological basis with
the CDMA2000 standards that we actually think of as CDMA.

What does your ppp dialup script contain?  That would help narrow the
issue down.

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Using a mobile phone via Bluetooth

[David Smith]

emobile.pppd
Description: Binary data


signature.asc
Description: OpenPGP digital signature
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Using a mobile phone via Bluetooth

[Dan Williams]

On Wed, 2009-07-08 at 01:31 +0900, David Smith wrote:
 On Wed, Jul 8, 2009 at 1:19 AM, Dan Williamsd...@redhat.com wrote:
  On Wed, 2009-07-08 at 01:13 +0900, david.daniel.sm...@gmail.com wrote:
  On Tue, Jul 7, 2009 at 3:18 AM, Dan Williamsd...@redhat.com wrote:
   On Mon, 2009-07-06 at 12:54 -0400, Ryan Novosielski wrote:
   -BEGIN PGP SIGNED MESSAGE-
   Hash: SHA1
  
   Brian Morrison wrote:
Saw this on the Planet Fedora RSS feed today:
   
http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/
   
Does this look the sort of thing where a more sane approach could be
added to NM or udev to cope with a wider range of phones without
needing to create user rules?
  
   I notice this solution mentions GSM. Is there any reason this should not
   work for a CDMA phone?
  
   As long as the phone responds to AT+GCAP with IS-707 the probe will
   tag the phone as a CDMA device and you should be able to use it with a
   CDMA connection like any normal data card or USB-attached CDMA phone.
   NM shouldn't be confused by the mis-tagged HAL entry in the linked
   dialup-bluetooth.py because it prefers the probed capabilities over
   static ones in HAL.
  
 
  I have an emobile (Japanese provider) CDMA device that responds with 
  +GCAP: +CGSM,+DS,+ES but not IS-707 and so only gets resolved as GSM by 
  NM, but in reality it's a CDMA-only device and works fine when just dialed 
  with pppd. What should I do in this situation? Also an earlier model from 
  the same provider that was also CDMA failed to respond at all to the 
  AT+GCAP (and subsequent) commands from nm-modem-probe. Is the device not 
  following the spec or is NM too strict?
 
  Emobile appears to be a GSM carrier, they appear to provide HSPA-based
  3G services.  You may be confusing CDMA with W-CDMA.  W-CDMA (Wideband
  CDMA) is the GSM-based 3G standard but shares a technological basis with
  the CDMA2000 standards that we actually think of as CDMA.
 
 
 Indeed, sorry for the confusion.
 
  What does your ppp dialup script contain?  That would help narrow the
  issue down.
 
 I've attached the pppd config file and the chatscript. It all seems like very 
 default settings (just dial the right number and use em/em for l/p). I 
 suppose it's the format of the number it's dialing that's interesting?

Yup.  That tells the phone what stored APN to use, in this case APN #1.
Whatever that is; you can use AT+CGDCONT=? to get them I think.

Dan

 
  Dan
 
 
 
 

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Using a mobile phone via Bluetooth

[Brian Morrison]

Dan Williams wrote:

 Sounds like more on the Bluetooth side, of course.  Does your phone do
 anything when NM tries to bring the connection up?  Mine usually asks me
 whether I want to allow the computer to connect, or it'll show an icon
 saying a computer is connected.

Bluetooth will insist on being paired and authorised as well or it will
ask for permission to allow the connection and use it.

  In any case, this is exactly why this
 method is a hack, and why we want the real solution...

I don't see there is any way to bypass these parts of the Bluetooth
protocol stack, but perhaps you know differently.

-- 

Brian
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Using a mobile phone via Bluetooth

[Dan Williams]

On Tue, 2009-07-07 at 17:43 +0100, Brian Morrison wrote:
 Dan Williams wrote:
 
  Sounds like more on the Bluetooth side, of course.  Does your phone do
  anything when NM tries to bring the connection up?  Mine usually asks me
  whether I want to allow the computer to connect, or it'll show an icon
  saying a computer is connected.
 
 Bluetooth will insist on being paired and authorised as well or it will
 ask for permission to allow the connection and use it.

Right, you can't always just open the persistent rfcomm port and expect
it to work, due to these sorts of issues.

   In any case, this is exactly why this
  method is a hack, and why we want the real solution...
 
 I don't see there is any way to bypass these parts of the Bluetooth
 protocol stack, but perhaps you know differently.

Well, the problem is that there's no intelligence built into that hack
method of doing Bluetooth.  In the bits we've added to 0.8 for
Bluetooth, we ask Bluez to set up the rfcomm port, and we can get
reliable errors when we can't talk to the phone or when something else
goes wrong.  With the persistent stuff, the errors just get completely
lost, because to NetworkManager, the hacked rfcomm thing just looks like
a directly connected serial port and thus all errors on the bluetooth
side just end up looking like a generic failure to talk to the modem.

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Using a mobile phone via Bluetooth

[Ryan Novosielski]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Brian Morrison wrote:
 Saw this on the Planet Fedora RSS feed today:
 
 http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/
 
 Does this look the sort of thing where a more sane approach could be
 added to NM or udev to cope with a wider range of phones without
 needing to create user rules?

I notice this solution mentions GSM. Is there any reason this should not
work for a CDMA phone?

- --
  _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Systems Programmer II
 |$| |__| |  | |__/ | \| _| |novos...@umdnj.edu - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/CST - NJMS Medical Science Bldg - C630
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpSLDMACgkQmb+gadEcsb72KgCeKW0iv4XjuPSezHHPRpNle0YQ
qTwAoIaeE/fo4pbEIhzPAtkYtTi/qGJC
=rkxV
-END PGP SIGNATURE-
begin:vcard
fn:Ryan Novosielski
n:Novosielski;Ryan
org:UMDNJ;IST/AST
adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103
email;internet:novos...@umdnj.edu
title:Systems Programmer II
tel;work:(973) 972-0922
tel;fax:(973) 972-7412
tel;pager:(866) 20-UMDNJ
x-mozilla-html:FALSE
version:2.1
end:vcard

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Using a mobile phone via Bluetooth

[Dan Williams]

On Sat, 2009-07-04 at 23:55 +0100, Brian Morrison wrote:
 Saw this on the Planet Fedora RSS feed today:
 
 http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/
 
 Does this look the sort of thing where a more sane approach could be
 added to NM or udev to cope with a wider range of phones without
 needing to create user rules?

The sane approach is to actually handle bluetooth devices natively in
NM; while the rfcomm thing works, it's certainly not preferred for a
variety of reasons I can explain if you like.  First off is that rfcomm
ports aren't usually dynamic, thus when probed and your phone isn't in
range the probe will fail.  Second is that they don't show up in the NM
API or the menu properly because NM of course doesn't know much about
them because they don't have a proper backing physical device that NM
knows about.  Second, NM can't respond to Bluez events or do anything
intelligent about errors, because NM sees it as just an rfcomm port.

However, there's already bluetooth PAN support in 0.8/master, and DUN
should be coming soon now that all the ModemManager stuff is fixed up
for udev.

http://blogs.gnome.org/dcbw/2009/05/22/a%e2%80%a2b%e2%80%a2c-delicious/

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Using a mobile phone via Bluetooth

[Dan Williams]

On Mon, 2009-07-06 at 12:54 -0400, Ryan Novosielski wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Brian Morrison wrote:
  Saw this on the Planet Fedora RSS feed today:
  
  http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/
  
  Does this look the sort of thing where a more sane approach could be
  added to NM or udev to cope with a wider range of phones without
  needing to create user rules?
 
 I notice this solution mentions GSM. Is there any reason this should not
 work for a CDMA phone?

As long as the phone responds to AT+GCAP with IS-707 the probe will
tag the phone as a CDMA device and you should be able to use it with a
CDMA connection like any normal data card or USB-attached CDMA phone.
NM shouldn't be confused by the mis-tagged HAL entry in the linked
dialup-bluetooth.py because it prefers the probed capabilities over
static ones in HAL.

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Using a mobile phone via Bluetooth

[Ryan Novosielski]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dan Williams wrote:
 On Mon, 2009-07-06 at 12:54 -0400, Ryan Novosielski wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Brian Morrison wrote:
 Saw this on the Planet Fedora RSS feed today:

 http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/

 Does this look the sort of thing where a more sane approach could be
 added to NM or udev to cope with a wider range of phones without
 needing to create user rules?
 I notice this solution mentions GSM. Is there any reason this should not
 work for a CDMA phone?
 
 As long as the phone responds to AT+GCAP with IS-707 the probe will
 tag the phone as a CDMA device and you should be able to use it with a
 CDMA connection like any normal data card or USB-attached CDMA phone.
 NM shouldn't be confused by the mis-tagged HAL entry in the linked
 dialup-bluetooth.py because it prefers the probed capabilities over
 static ones in HAL.

So I actually got this working where an rfcomm1 shows up in the NM
Plasma Applet (I assume that I'm probably supposed to stop setting up
rfcomm0 manually with /etc/bluetooth/rfcomm.conf). However, nothing I do
seems to make it want to actually connect. At first the rfcomm1 shows up
and claims to be looking for an IP address. Then it fails. It's not
clear that it ever attempts to dialup via PPP, even though I have a
connection configured. Is there some way to troubleshoot this?

- --
  _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Systems Programmer II
 |$| |__| |  | |__/ | \| _| |novos...@umdnj.edu - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/CST - NJMS Medical Science Bldg - C630
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpSxpMACgkQmb+gadEcsb4rhwCdH/FnSG5Nwl+ddhD2taECkSWm
4QMAn0ZDmzNjzPNHiSr0JIcVyJKjT0i7
=iIxk
-END PGP SIGNATURE-
begin:vcard
fn:Ryan Novosielski
n:Novosielski;Ryan
org:UMDNJ;IST/AST
adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103
email;internet:novos...@umdnj.edu
title:Systems Programmer II
tel;work:(973) 972-0922
tel;fax:(973) 972-7412
tel;pager:(866) 20-UMDNJ
x-mozilla-html:FALSE
version:2.1
end:vcard

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Using a mobile phone via Bluetooth

[Brian Morrison]

Saw this on the Planet Fedora RSS feed today:

http://fetzig.org/2009/07/04/tethering-in-fedora-using-your-mobile-phone-with-networkmanager-to-surf-the-web/

Does this look the sort of thing where a more sane approach could be
added to NM or udev to cope with a wider range of phones without
needing to create user rules?

-- 

Brian Morrison

bdm at fenrir dot org dot uk

   Arguing with an engineer is like wrestling with a pig in the mud;
after a while you realize you are muddy and the pig is enjoying it.

GnuPG key ID DE32E5C5 - http://wwwkeys.uk.pgp.net/pgpnet/wwwkeys.html
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list