public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Mateus Interciso <mateus@ouvi.com.br>
To: Iain Hibbert <plunky@rya-online.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Question on simple RFCOMM server
Date: Tue, 25 Aug 2009 11:18:46 -0300	[thread overview]
Message-ID: <4A93F2C6.4030708@ouvi.com.br> (raw)
In-Reply-To: <1251207686.259635.1938.nullmailer@galant.ukfsn.org>

Thank you, however the Peter solution (setting via ioctl) worked 
perfectly, and it fit's with what I need, since all the clients are 
already implemented via RFCOMM, I'll leave it like this for now, the 
only issue is having to run it as root for setting the link mode, but I 
can bypass this by using hciconfig before running the main server.
Or is there any configuration that can make a normal user change the 
default link mode?

Thanks all once again.

Iain Hibbert wrote:
> On Tue, 25 Aug 2009, Mateus Interciso wrote:
> 
>> Hello, I have a very simple RFCOMM server that I adapted from an extremely
>> simple TCP echo server I've made for learning TCP, it's a simple fork()
>> server, and while the TCP server works perfeclty, the RFCOMM works only with 2
>> connected clients at the same time, and I'm failling to see the problem, can
>> someone help me?
> 
> You didn't post what the 'failure' was but for RFCOMM you can only have
> one connection on a server channel (each RFCOMM channel corresponds to
> an emulated serial port).
> 
> since a TCP connection is defined by the address and port at each end, the
> Bluetooth equivalent is more likely to be a a L2CAP connection to a given
> PSM which can support up to ~64k channels (though as the Peter Wippich
> notes, the number of devices the radio can maintain connections with is
> limited)
> 
> iain
> 
> 
> 

  reply	other threads:[~2009-08-25 14:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 12:26 Question on simple RFCOMM server Mateus Interciso
2009-08-25 12:31 ` Peter Wippich
2009-08-25 13:41 ` Iain Hibbert
2009-08-25 14:18   ` Mateus Interciso [this message]
2009-08-25 17:15     ` Iain Hibbert

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=4A93F2C6.4030708@ouvi.com.br \
    --to=mateus@ouvi.com.br \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=plunky@rya-online.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