From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Initial support for the BPA 100/105 sniffers
Date: Mon, 14 Mar 2005 17:29:12 +0100 [thread overview]
Message-ID: <1110817752.629.23.camel@pegasus> (raw)
In-Reply-To: <loom.20050314T161343-122@post.gmane.org>
Hi Andreas,
> I have one for testing (more sniffing) the telematic devices coming from our
> suppliers.
> Up to now we are using it with windows. But now we will have a deeper look to
> your support for the BPA105 :-)
I never thought that these sniffers are still in use. I would be great
to increase the Linux support for them. However be aware of that the
current code is not able to sniff encrypted traffic. I also still don't
have any idea how to differ between traffic from the master and the
slaves.
> We plan to switch to kernel 2.6.10 with your patches within the next two weeks.
It seems that people are really beginning to love the 2.6.10 kernel, but
personally I would see them to use 2.6.11.x.
> By the way, it's nice to have bluez for testing ...
me, too :)
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-03-14 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 21:51 [Bluez-devel] Initial support for the BPA 100/105 sniffers Marcel Holtmann
2005-03-14 15:43 ` [Bluez-devel] " Andreas
2005-03-14 16:29 ` Marcel Holtmann [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=1110817752.629.23.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@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