From: "Albert Huang" <ashuang@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bluetooth remote control
Date: Wed, 12 Apr 2006 13:06:09 -0400 [thread overview]
Message-ID: <ef9938ec0604121006w6ba7fccbm6c5d39fab1445e61@mail.gmail.com> (raw)
In-Reply-To: <20060411223157.86042.qmail@web61222.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
Take a look at Xbtrc
http://wwwhome.cs.utwente.nl/~dijkhw/index.php?p=Katlijk/Xbtrc
problems encountered: multiple remotes can't connect to the same server.
>
> i see that the accept method (unlike tcp implementation) returns the
> server port upon accepting an incoming connection. for instance, if the
> server is listening on port 16, when any remote connects to the server, the
> server port 16 is used to establish end-to-end connection with the client.
> now, another device cannot connect to the same server until the first remote
> disconnects. this problem stops us from using multiple remotes with a single
> linux server.
>
There is no such restriction in hardware or bluetooth software stack.
Multiple clients can be simultaneously connected to the same RFCOMM channel
on a server. Use hcidump -X -V to find out where the connection fails.
Make sure that the server is always the master and that the clients are
always the slaves. This probably requires a role switch after each connect.
> >rfcomm connect 00:0D:88:C0:61:55 16
> Can't connect RFCOMM socket: Host is down
>
This syntax is incorrect. See the rfcomm documentation.
-albert
[-- Attachment #2: Type: text/html, Size: 1721 bytes --]
prev parent reply other threads:[~2006-04-12 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 22:31 [Bluez-users] bluetooth remote control deva seetharam
2006-04-12 2:25 ` Sowmya Gattupalli
2006-04-12 15:54 ` deva seetharam
2006-04-12 17:06 ` Albert Huang [this message]
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=ef9938ec0604121006w6ba7fccbm6c5d39fab1445e61@mail.gmail.com \
--to=ashuang@gmail.com \
--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