From: Marcel Holtmann <marcel@holtmann.org>
To: Edd Dumbill <edd@usefulinc.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Release of new BlueZ libs and utils
Date: Tue, 06 Jan 2004 14:20:17 +0100 [thread overview]
Message-ID: <1073395217.2508.62.camel@pegasus> (raw)
In-Reply-To: <1073394683.8730.225.camel@saag>
Hi Edd,
> > this only happens when rfcomm_connect_ind() returns false and this means
> > that we can't create the new socket. In most cases this is because there
> > is no listen socket for it. Do /proc/bluetooth/rfcomm show the listen
> > socket on that channel? Do you use the same channel number in your SDP
> > record as for dund?
>
> sdptool browse ff:ff:ff ....
>
> Service Name: Serial Port
> Service RecHandle: 0x804ee30
> Service Class ID List:
> "Serial Port" (0x1101)
> Protocol Descriptor List:
> "L2CAP" (0x0100)
> "RFCOMM" (0x0003)
> Channel: 3
> Profile Descriptor List:
> "Serial Port" (0x1101)
> Version: 0x0100
>
>
> strace dund --listen --persist --channel 3 --nodetach
maybe the P800 is buggy. Run a second dund on channel 1 to see if it
connects.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-01-06 13:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 23:55 [Bluez-users] Release of new BlueZ libs and utils Marcel Holtmann
2003-12-19 0:28 ` Michal Semler (volny.cz)
2003-12-19 9:19 ` Marcel Holtmann
2003-12-19 10:22 ` Michal Semler (volny.cz)
2003-12-20 7:14 ` Charles Bueche
2003-12-20 14:39 ` Marcel Holtmann
2003-12-19 10:15 ` Stephen Crane
2004-01-01 20:39 ` Edd Dumbill
2004-01-02 11:04 ` [Bluez-users] " Marcel Holtmann
2004-01-02 11:09 ` Edd Dumbill
2004-01-02 11:24 ` [Bluez-users] " Marcel Holtmann
2004-01-02 17:18 ` Michal Semler (volny.cz)
2004-01-02 23:35 ` Marcel Holtmann
2004-01-03 19:54 ` Michal Semler (volny.cz)
2004-01-04 10:35 ` Marcel Holtmann
2004-01-03 16:32 ` [Bluez-users] " Edd Dumbill
2004-01-03 16:47 ` Edd Dumbill
2004-01-03 17:10 ` Marcel Holtmann
2004-01-03 18:33 ` Edd Dumbill
2004-01-04 10:38 ` Marcel Holtmann
2004-01-06 11:26 ` Edd Dumbill
2004-01-06 12:37 ` Marcel Holtmann
2004-01-06 13:11 ` Edd Dumbill
2004-01-06 13:20 ` Marcel Holtmann [this message]
2004-01-06 14:02 ` Edd Dumbill
2004-01-06 14:15 ` Marcel Holtmann
2004-01-06 14:30 ` Edd Dumbill
2004-01-06 14:18 ` Xavier Garreau
2004-01-06 12:54 ` Xavier Garreau
2004-01-06 13:06 ` Marcel Holtmann
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=1073395217.2508.62.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=edd@usefulinc.com \
/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.