public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: R.Schade@tu-braunschweig.de
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] simple rfcomm connect!?
Date: Fri, 22 Oct 2004 12:51:38 +0200	[thread overview]
Message-ID: <1098442298.4704.30.camel@pegasus> (raw)
In-Reply-To: <517CF7F08A05D4118C380000E869BFA4BDEDD1@emg_ntserv2>

Hi Ralf,

> I have two identical BT-Dongles and I want to make my first steps on
> programming with bluez. For the first quick and dirty I tried to connect
> these two dongles on different PCs over a RFCOMM channel. The server comes
> up and is waiting, but the client breaks the connect with "Connection
> refused". What can I do? How can I debug or find out more information about
> whats going wrong? Can I switch to verbose output for the bluez-daemons?

run "hcidump -X" as root to see the details.

> Both PCs are on Debian Sarge 2.4.27 with whole bluez-stuff compiled in the
> kernel and the additional bluez-packages. The "hcid.conf" and "pin" are
> identical on both PCs, for testing the security is none. "l2ping" and the
> other basic tests are working. "hciconfig -a" and "hcitool scan" looks good,
> but sdptool browse xxxx shows only "L2CAP" on protocol-lists, no RFCOMM
> (look at the end of email). All internet examples have the rfcomm on the
> protocol list ??!

Show them to us and also show us the full source code. The ownsock
variable can't be an integer, but you treat it like an integer in the
printf statement. So either the type is wrong or you get a bunch of
compiler warnings that you are ignoring.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2004-10-22 10:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22  6:36 [Bluez-users] simple rfcomm connect!? R.Schade
2004-10-22  7:21 ` Fred Schaettgen
2004-10-22 10:51 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-22 12:07 R.Schade
2004-10-22 12:53 ` 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=1098442298.4704.30.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=R.Schade@tu-braunschweig.de \
    --cc=bluez-users@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox