Re: NM + DUN on Fedora-12?

[Dan Williams <dcbw redhat com>]

On Wed, 2010-06-23 at 17:34 -0700, Dan Williams wrote:
> On Wed, 2010-06-23 at 20:28 -0400, Derek Atkins wrote:
> > Dan,
> > 
> > On Wed, June 23, 2010 7:29 pm, Dan Williams wrote:
> > 
> > >> I've just upgraded my FC12 laptop to the most recent packages (but not
> > >> the testing packages).  I'm hitting this kernel/USB issue.  Any known
> > >> workarounds?  Any test-patches I could play with?
> > >
> > > Not really, but you can test stuff out manually if you want...
> > >
> > > 1) get your BT address
> > 
> > I presume by "your" you mean "the phone", right?
> 
> Yeah.
> 
> > > 2) pair the device
> > > 3) sdptool browse <btaddr>
> > > 4) from the sdptool output, find the channel that DUN uses
> > 
> > I'm not seeing it.  I've attached the output below.
> 
> The SDP record will look like this:
> 
> Service Name: Dialup Networking
> Service RecHandle: 0x10006
> Service Class ID List:
>   "Dialup Networking" (0x1103)
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 6
> Profile Descriptor List:
>   "Dialup Networking" (0x1103)
>     Version: 0x0100
> 
> If you don't have that record, either the phone can't do DUN, or there's
> something on the phone that's not enabled to make DUN show up.

Googling around a bit I find people with some of the same problems.
You're sure you've:

a) paired with the computer successfully
b) enabled BT DUN in PDAnet
c) whatever it says here?
http://www.junefabrics.com/android/bluetooth.php

etc.  Basically, if that SDP record doesn't show up, there's nothing
that Linux or even Windows/Mac OS X can do since the device is saying
it's not capable of DUN at all.

Dan

> Dan
> 
> > > 5) rfcomm connect hci0 <btaddr> <channel #>
> > >
> > > and it'll tell you what serial device it just made.  Then you open that
> > > up in minicom and try something like "ATI" and see what happens.
> > >
> > > If that all works, then the problem is likely in bluez or NM, not the
> > > kernel.
> > >
> > > Dan
> > 
> > Service RecHandle: 0x10000
> > Service Class ID List:
> >   "PnP Information" (0x1200)
> > 
> > Service Name: Headset Gateway
> > Service RecHandle: 0x10001
> > Service Class ID List:
> >   "Headset Audio Gateway" (0x1112)
> >   "Generic Audio" (0x1203)
> > Protocol Descriptor List:
> >   "L2CAP" (0x0100)
> >   "RFCOMM" (0x0003)
> >     Channel: 1
> > Profile Descriptor List:
> >   "Headset" (0x1108)
> >     Version: 0x0100
> > 
> > Service Name: Handsfree Gateway
> > Service RecHandle: 0x10002
> > Service Class ID List:
> >   "Handsfree Audio Gateway" (0x111f)
> >   "Generic Audio" (0x1203)
> > Protocol Descriptor List:
> >   "L2CAP" (0x0100)
> >   "RFCOMM" (0x0003)
> >     Channel: 2
> > Profile Descriptor List:
> >   "Handsfree" (0x111e)
> >     Version: 0x0105
> > 
> > Service Name: Object Push
> > Service RecHandle: 0x10003
> > Service Class ID List:
> >   "OBEX Object Push" (0x1105)
> > Protocol Descriptor List:
> >   "L2CAP" (0x0100)
> >   "RFCOMM" (0x0003)
> >     Channel: 3
> >   "OBEX" (0x0008)
> > Profile Descriptor List:
> >   "OBEX Object Push" (0x1105)
> >     Version: 0x0100
> > 
> > Service RecHandle: 0x10004
> > Service Class ID List:
> >   "AV Remote Target" (0x110c)
> > Protocol Descriptor List:
> >   "L2CAP" (0x0100)
> >     PSM: 23
> >   "AVCTP" (0x0017)
> >     uint16: 0x100
> > Profile Descriptor List:
> >   "AV Remote" (0x110e)
> >     Version: 0x0100
> > 
> > Service Name: BRCM Advanced Audio
> > Service RecHandle: 0x10005
> > Service Class ID List:
> >   "Audio Source" (0x110a)
> > Protocol Descriptor List:
> >   "L2CAP" (0x0100)
> >     PSM: 25
> >   "AVDTP" (0x0019)
> >     uint16: 0x102
> > Profile Descriptor List:
> >   "Advanced Audio" (0x110d)
> >     Version: 0x0102
> > 
> > Service Name: Phonebook Access PSE
> > Service RecHandle: 0x10006
> > Service Class ID List:
> >   "Phonebook Access - PSE" (0x112f)
> > Protocol Descriptor List:
> >   "L2CAP" (0x0100)
> >   "RFCOMM" (0x0003)
> >     Channel: 4
> >   "OBEX" (0x0008)
> > Profile Descriptor List:
> >   "Phonebook Access" (0x1130)
> >     Version: 0x0100
> > 
> > Service RecHandle: 0x10007
> > Service Class ID List:
> >   UUID 128: 00001103-0000-1000-8000-00805f9b34fb
> > Protocol Descriptor List:
> >   "L2CAP" (0x0100)
> >   "RFCOMM" (0x0003)
> >     Channel: 5
> > 
> > Service RecHandle: 0x10008
> > Service Class ID List:
> >   UUID 128: 00001103-0000-1000-8000-00805f9b34fb
> > Protocol Descriptor List:
> >   "L2CAP" (0x0100)
> >   "RFCOMM" (0x0003)
> >     Channel: 5
> > 
> > Service RecHandle: 0x10009
> > Service Class ID List:
> >   UUID 128: 00001103-0000-1000-8000-00805f9b34fb
> > Protocol Descriptor List:
> >   "L2CAP" (0x0100)
> >   "RFCOMM" (0x0003)
> >     Channel: 5
> > 
> > Service RecHandle: 0x1000a
> > Service Class ID List:
> >   UUID 128: 00001103-0000-1000-8000-00805f9b34fb
> > Protocol Descriptor List:
> >   "L2CAP" (0x0100)
> >   "RFCOMM" (0x0003)
> >     Channel: 5
> > 
> > 
> 
> 
> _______________________________________________
> networkmanager-list mailing list
> networkmanager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list