public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Kohlsmith <akohlsmith-bluez@benshaw.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] rfcomm hell
Date: Tue, 22 Aug 2006 12:27:14 -0400	[thread overview]
Message-ID: <200608221227.15052.akohlsmith-bluez@benshaw.com> (raw)
In-Reply-To: <20060822181532.6fea4851@localhost>

On Tuesday 22 August 2006 12:15, The Peach wrote:
> # rfcomm bind 0 00:12:62:A8:12:FE

I've given up on rfcomm for the most part.  rfcomm's connect option is just 
plain broken.  Instead of trying to dig in and fix it, I happened upon some 
simple utilities which seem to work much better for my purposes.  I still use 
rfcomm bind to attach pppd, though.

http://auriga.wearlab.de/~andi/smalltools/

look at rfcomm-read, rfcomm-listen and rfcomm-listen-start, specifically.

Hope this helps!

-A.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2006-08-22 16:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22 16:15 [Bluez-users] rfcomm hell The Peach
2006-08-22 16:25 ` The Peach
2006-08-22 16:27 ` Andrew Kohlsmith [this message]
2006-08-22 17:52   ` The Peach
2006-08-22 17:57     ` Andrew Kohlsmith
2006-08-22 23:22       ` The Peach
2006-08-29  9:06 ` The Peach
2006-08-29 18:01   ` Stefan Seyfried
2006-08-29 20:49     ` 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=200608221227.15052.akohlsmith-bluez@benshaw.com \
    --to=akohlsmith-bluez@benshaw.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