From: Marcel Holtmann <marcel@holtmann.org>
To: James Cameron <james.cameron@hp.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] pand/main.c, restore signals for dev-up script
Date: Mon, 28 Jun 2004 14:54:31 +0200 [thread overview]
Message-ID: <1088427271.3774.198.camel@pegasus> (raw)
In-Reply-To: <20040628120612.GF8871@hp.com>
Hi James,
> > [...] The remote address is available via "pand -l".
>
> Neat. Another way to get it. ;-) But this way activates pand again,
> so dev-up remains the most efficient way to get this address.
what do you wanna do with that information? Actually I never needed it.
Regards
Marcel
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-06-28 12:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 13:33 [Bluez-devel] [PATCH] pand/main.c, restore signals for dev-up script James Cameron
2004-06-27 20:06 ` Marcel Holtmann
2004-06-27 23:34 ` James Cameron
2004-06-28 7:44 ` Marcel Holtmann
2004-06-28 8:53 ` James Cameron
2004-06-28 9:05 ` Marcel Holtmann
2004-06-28 9:55 ` James Cameron
2004-06-28 10:13 ` Marcel Holtmann
2004-06-28 10:19 ` James Cameron
2004-06-28 10:39 ` Marcel Holtmann
2004-06-28 12:06 ` James Cameron
2004-06-28 12:54 ` Marcel Holtmann [this message]
2004-06-28 22:48 ` James Cameron
2004-06-28 23:26 ` Marcel Holtmann
2004-06-29 5:23 ` James Cameron
2004-06-29 8:58 ` Marcel Holtmann
2004-06-29 10:55 ` James Cameron
2004-06-29 11:26 ` Marcel Holtmann
2004-06-30 0:15 ` James Cameron
2004-06-30 9:06 ` 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=1088427271.3774.198.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=james.cameron@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox