So weird! I sent the same message twice, and only when I changed the
url did it go through... perhaps coincidence. Let's see if this reply
makes it through.
On 01/09/18 15:20, Maynard, Chris wrote:
I'm not aware of any constraints with respect to URL's.
Here's a test of your message with
I'm not aware of any constraints with respect to URL's.
Here's a test of your message with the original URL you intended to write;
let's see if this goes through ...
- Chris
Hi,
Is there anyone who knows of an updated sharktooks that works with the latest
wireshark (2.2+) ?
https://github.com
What are the constraints for posting on this list? It does look like
url links contained in a post body will cause the post to be completely
blocked with no explanation/notification.
On 1/9/18 3:10 PM, Mark Murawski wrote:
I tried replying to this message with my other (real) message and it'
Trying to post this for the third time. I adjusted the url that was
maybe causing my post to get (silently) dropped.
Hi,
Is there anyone who knows of an updated sharktooks that works with the
latest wireshark (2.2+) ?
h t t p s github dot com /armenb/sharktools
I've contacted the author a
I tried replying to this message with my other (real) message and it's
not going through. It must be tripping some anti-spam filters or
something like that.
On 1/8/18 5:39 PM, Kennedy, Smith (Wireless & Standards Architec) wrote:
Ack.
On Jan 8, 2018, at 3:06 PM, Mark Murawski wrote:
I d
For what it's worth, libpcap 1.8 and later don't require that a local interface
be openable before listing it in pcap_findalldevs(), so, whilst you might still
need dumpcap to *capture* packets, it should be possible to *enumerate*
interfaces directly within Wireshark/TShark with libpcap 1.8 and
Hi,
This is run on a standard Windows7 PC with just the default extcaps.
This is the interfaces with the Preference off
C:\Development\wsbuild64>run\RelWithDebInfo\dumpcap.exe -D
1. \Device\NPF_{33D2B022-D2AC-40A3-BE47-C81B4F2EC346} (Wireless Network Connecti
on)
2. \Device\NPF_{F592C5E2-78A5-4C2C-
I have 5 extcaps, and the difference is about half a second. Would be
interesting, what kind of devices you have in your extcap list.
But in general, I still think the main time is loading the rest of
interfaces, extcap is a very small part, just pushed the whole time over
the top.
cheers
On Tue
Hi,
Startup time with extcap:
14:29:56.217 Main Info Wireshark is up and ready to go, elapsed time
5485000 us
Startup time with the new extcap parameter OFF
14:30:40.559 Main Info Wireshark is up and ready to go, elapsed time
3521000 us
Still a lot of time is spent with the local interf
