From: James Cameron <james.cameron@hp.com>
To: h0016530@hkusua.hku.hk
Cc: James Cameron <james.cameron@hp.com>, bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Questions about Role Changing during PAN setup
Date: Thu, 8 Jul 2004 15:54:23 +1000 [thread overview]
Message-ID: <20040708055423.GI18689@hp.com> (raw)
In-Reply-To: <1089265279.40ecde7f12156@imp.webmail.hku.hk>
On Thu, Jul 08, 2004 at 01:41:19PM +0800, h0016530@hkusua.hku.hk wrote:
> server(PC):
> #modprobe l2cap
> #modprobe bnep
> #sdpd
> #hcid
> #hciconfig hci0 up
> #pand --listen --role NAP --service --sdp --master
> #pand --connect 00:02:C7:18:25:A0
> #ifconfig bnep0 10.0.0.1
>
> client(iPAQ, familiar linux):
> #pand --listen --role PANU
> #ifconfig bnep0 10.0.0.2
Slightly different. On my server (PC) I run:
# pand --listen --role NAP
And on client (laptop) I run:
# pand --nodetach --role PANU --search
ifconfig is handled automatically by hotplug on both systems, but
essentially it happens shortly after connection is made.
Since you are making PANU connection from server to iPAQ, it is not
wrong for "pand --show" to show PANU connection.
--
James Cameron
Software Security Response Team
HP Services, Asia Pacific
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-07-08 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 4:57 [Bluez-devel] Questions about Role Changing during PAN setup h0016530
2004-07-08 5:13 ` James Cameron
2004-07-08 5:27 ` James Cameron
2004-07-08 5:41 ` h0016530
2004-07-08 5:54 ` James Cameron [this message]
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=20040708055423.GI18689@hp.com \
--to=james.cameron@hp.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=h0016530@hkusua.hku.hk \
/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