public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre N <pierren@mac.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Two simultanous connections
Date: Sat, 03 Apr 2004 13:50:11 +0200	[thread overview]
Message-ID: <1080993011.12261.12.camel@localhost> (raw)
In-Reply-To: <1080929429.2836.101.camel@pegasus>

[-- Attachment #1: Type: text/plain, Size: 2024 bytes --]

hcitool -a shows "invalid option -- a".
This is the bluetooth chip of an iPaq 3970. It's running Familiar
stable, so it must be a pretty old bluez version. Don't know if it
helps...

Ok, I knew I had to give more details... I create links between 3 iPaqs.
I tried using higher layer protocols to do so. Never worked. I'm just
trying to do a TCP/IP network so I can run XML-RPC on top of it, ssh
etc...

That's all I need. I tried to use pan, never worked, I tried to use dun
over pan, never worked, I tried to use rfcomm never worked. Always the
same problem:
I could connect A to B and B to C, never B to A and C to A. 

Now I went the hcitool route. Created my own connections very very
easily. I connected B to A and C to A (A master). Ran dund _after_
hcitool connections and everything is running great.

hcitool con on A gives me two master connections. These connections have
been initialised from B and C as slave. So I can have two master
connections, but I can't create them from A. First one works, second one
doesn't, nothing happen. It's just out of curiosity.

--
Pierre



On Fri, 2004-04-02 at 20:10, Marcel Holtmann wrote:
> Hi Pierre,
> 
> > I've been trying to setup ip net with 3 identical devices connected
> > simultanously over bluetooth. It works after a long
> > while of fiddling around. I had to go the hcitool route manually to set
> > the initial connections and then I could use dund no problem. My
> > question is: why can't I initiate a connection (hcitool cc) from a
> > device which is already connected?
> 
> for some setups this depends on your Bluetooth chip. So what does
> "hciconfig -a" show? But I am not sure about what kind of network you
> are talking, because between two device there can be only _one_ ACL link
> and this means you can only use "hcitool cc" once. Actually there is no
> need for creating the ACL link manually with hcitool, because every
> higher layer will create it on demand.
> 
> Regards
> 
> Marcel
> 
> 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-04-03 11:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02 18:00 [Bluez-users] Two simultanous connections Pierre N
2004-04-02 18:10 ` Marcel Holtmann
2004-04-03 11:50   ` Pierre N [this message]
2004-04-03 12:16     ` Marcel Holtmann
2004-04-03 13:01       ` Pierre N
2004-04-03 16:24         ` Andreas Gaufer
     [not found]         ` <20040403182354.5c3420eb.Andreas.Gaufer@blue-cell-networks.com>
2004-04-03 16:53           ` Pierre N

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=1080993011.12261.12.camel@localhost \
    --to=pierren@mac.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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