All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Steve Drew <steve.drew@empics.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Problems connecting to multiple rfcomm sockets
Date: Wed, 27 Oct 2004 17:49:02 +0200	[thread overview]
Message-ID: <1098892142.6730.1.camel@pegasus> (raw)
In-Reply-To: <0DD4EA5DCF754A409C4E182C758C37F38204@tigris.i.empics.co.uk>

Hi Steve,

> I've been experiencing some problems when trying to open multiple rfcomm
> ports, with pppd using the rfcomm ports.
> 
> I have three bluetooth serial ports setup in rfcomm.conf, but it appears
> that I can open connections to two of them at once. 
> 
> While the first two serial ports are connected, and the third is trying
> to connect, running rfcomm gives;
> 
> rfcomm0: 00:0E:6D:1A:9A:3F channel 1 connected [tty-attached]
> rfcomm1: 00:02:EE:82:D9:29 channel 2 connected [tty-attached]
> rfcomm2: 00:60:57:70:CD:E1 channel 3 config [tty-attached]
> 
> Then the terminal with the third connection reports;
> 
> "Failed to open /dev/rfcomm2: Host is down"
> 
> At which point running #rfcomm gives;
> 
> rfcomm0: 00:0E:6D:1A:9A:3F channel 1 connected [tty-attached]
> rfcomm1: 00:02:EE:82:D9:29 channel 2 connected [tty-attached]
> rfcomm2: 00:60:57:70:CD:E1 channel 3 closed.

what does "hcitool con" tell you at this point? Run "hcidump -x" and see
with what error code the third connection fails.

> If I now close the connection to rfcomm1 or rfcomm0, I can connect to
> rfcomm2 (so I can always have a max of 2 active connections).
> 
> However, If before I start the pppd connections to the serial ports, I
> start 3 copies of l2ping (one to each of the MAC addresses listed
> above), and keep these running, I can establish pppd connections on
> rfcomm0+1+2 at the same time.
> 
> With this scenario, if one of the pppd sessions terminates, the l2ping
> to the corresponding rfcomm device's MAC will stop giving:
>  "Send failed: Connection reset by peer", and once again I can only use
> two of the rfcomm ports. 
> 
> Using bluez-utils-2.10-2 and bluez-libs-2.10-2 under a 2.4.22-1 kernel
> 
> Any idea/subjections/requests for more information greatly appreciated!

What devices did you use (hciconfig -a) and to what devices are you
connecting?

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-10-27 15:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27 15:42 [Bluez-users] Problems connecting to multiple rfcomm sockets Steve Drew
2004-10-27 15:49 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-27 16:32 Steve Drew
2004-10-27 16:45 ` Marcel Holtmann
     [not found] <0DD4EA5DCF754A409C4E182C758C37F38231@tigris.i.empics.co.uk>
2004-11-04 18:01 ` Marcel Holtmann
2004-11-04 18:15   ` Peter Stephenson

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=1098892142.6730.1.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=steve.drew@empics.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.