From: Rick Jones <rick@activeservice.co.uk>
To: Bastien Nocera <hadess@hadess.net>, Dan Williams <dcbw@redhat.com>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>,
networkmanager-list@gnome.org
Subject: Re: So very close, but so frustrating...
Date: Fri, 02 Oct 2009 01:55:27 +0100 [thread overview]
Message-ID: <CB7A3691FBC7EB0E857B7330@mineee> (raw)
In-Reply-To: <1254439169.22191.317.camel@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 1982 bytes --]
I've just installed blueman, to replace bluez-gnome, and it does this
perfectly.
It's a much better UI-oriented manager for BT devices altogether, it shows
my phone, I click on "attach serial service", and it exposes the BT modem
in DBus. NM 0.7 sees it just like a USB modem and it connects first time.
Magic!
I'm too hardened to be often impressed first-time with a piece of software,
but this was spot-on (does audio, obex, etc just as neatly). OK, it takes a
couple of extra clicks to connect the phone, which I guess a built-in NM
implementation could do automatically, but that's pretty minor.
Rick
--On Friday, October 02, 2009 00:19:29 +0100 Bastien Nocera
<hadess@hadess.net> wrote:
> On Thu, 2009-10-01 at 14:39 -0700, Dan Williams wrote:
> > On Wed, 2009-09-30 at 20:18 -0400, Darren Albers wrote:
> <snip>
> > > At this time Network Manager does not support Bluetooth modems. I
> > > think 0.8 supports phones if they use Bluetooth PAN but not Bluetooth
> > > DUN.
> >
> > Correct; I may just get bored enough today triaging bugs to go implement
> > DUN in 0.8. That opens up a huge number of cellphones, which will
> > inevitably lead to even more bugs since there's much more phone
> > variation than in the relatively small data card space. Oh well; it
> > would help a lot of people out.
>
> 1. Add ability for MM to identify Bluetooth modems
> 2. Add plugin in bluez to poke at the modem with MM if it doesn't know
> the type of device, cache the result, the bluez plugin exports the
> information through a service
> 3. Add DUN gnome-bluetooth plugin to nm-applet which would poke the
> bluez service
> 4. Add native support in NM to do the connection through bluetoothd
>
> After 3., if the box is ticked, the device should appear like an
> unconfigured WWAN modem to the user. The service configuration can then
> be done through nm-applet.
>
> I can certainly take care of 2. and 3. if you do 1. and the left-overs
> of 4 :)
>
> Cheers
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2467 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
next prev parent reply other threads:[~2009-10-02 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AC3EFD9.1020602@shic.co.uk>
[not found] ` <7cd7fc040909301718r3e441c53x767084b0b01f4a7c@mail.gmail.com>
[not found] ` <1254433173.9657.155.camel@localhost.localdomain>
2009-10-01 23:19 ` So very close, but so frustrating Bastien Nocera
2009-10-02 0:55 ` Rick Jones [this message]
2009-10-02 8:39 ` Bastien Nocera
2009-10-03 1:44 ` Dan Williams
2009-10-03 8:08 ` Dan Williams
2009-10-05 10:55 ` Bastien Nocera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CB7A3691FBC7EB0E857B7330@mineee \
--to=rick@activeservice.co.uk \
--cc=dcbw@redhat.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=networkmanager-list@gnome.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.