Linux bluetooth development
 help / color / mirror / Atom feed
From: Sybren Stuvel <sybren@thirdtower.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] rfcomm patch
Date: Wed, 5 Nov 2003 16:00:39 +0100	[thread overview]
Message-ID: <200311051600.40995.sybren@thirdtower.com> (raw)
In-Reply-To: <20031105121405.GA9763@sybren.thirdtower.com>

On Wednesday 05 November 2003 13:14, Sybren Stuvel wrote:
> I tried dund, but I couldn't get it to work together with Affix on my
> Sharp Zaurus (running OpenZaurus 3.2). I'll try again and come up with
> some info that might actually be useful for solving the mistery ;-)

Apparently I didn't try dund, or I tried it the wrong way. Now that I'm 
looking at it with a fresh mind it works like a charm:

sybren root # dund --search --nodetach
dund[10733]: DUN daemon ver 1.1
dund[10733]: Inquiring
dund[10733]: Searching for LAP on 00:10:7A:4C:23:02
dund[10733]: Connecting to 00:10:7A:4C:23:02 channel 2
dund[10733]: Connection established
Using interface ppp0
Connect: ppp0 <--> /dev/rfcomm0
local  IP address 172.16.0.2
remote IP address 172.16.0.1
BSD-Compress (15) compression enabled
 
Thank you very much! This saves me a lot of fuss!
You made me a very happy man :)

Greetz,
Sybren
-- 
(o_   Q: God, root, what is difference?
//\   A: God can change the byte order on the CPU, root can't.
V_/_

  parent reply	other threads:[~2003-11-05 15:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05  8:45 [Bluez-devel] rfcomm patch Sybren Stuvel
2003-11-05 10:16 ` Marcel Holtmann
2003-11-05 12:14   ` Sybren Stuvel
2003-11-05 12:22     ` Marcel Holtmann
2003-11-05 15:00     ` Sybren Stuvel [this message]
2003-11-05 15:50 ` Alan Huang
2003-11-06  8:39   ` Marcel Holtmann
2003-11-06 20:29     ` [Bluez-users] " Alan Huang
2003-11-06 23:44       ` 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=200311051600.40995.sybren@thirdtower.com \
    --to=sybren@thirdtower.com \
    --cc=bluez-devel@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