Re: [Wireshark-dev] Npcap 0.01 call for test about Windows loopback traffic capture feature

2015-07-14 Thread Yang Luo
Hi Pascal, I am not very familiar about dialup/PPP interfaces, perhaps you mean capturing on adapters like below? WAN Miniport (SSTP) WAN Miniport (IPv6) WAN Miniport (IP) WAN Miniport (L2TP) WAN Miniport (PPPOE) WAN Miniport (PPTP) WAN Miniport (Network Monitor) WAN Miniport (IKEv2) These adapte

Re: [Wireshark-dev] Wireshark messages I don't want to see

2015-07-14 Thread Joerg Mayer
On Tue, Jul 14, 2015 at 09:13:49PM +0200, Joerg Mayer wrote: > On Tue, Jul 14, 2015 at 11:52:18AM -0700, Guy Harris wrote: > > Line 1558 of epan/crypt/airpdcap.c is > > > > if (ctx->sa[ctx->first_free_index].used) { > > > > in AirPDcapStoreSa(). It was assuming that ctx->first_free_index wo

Re: [Wireshark-dev] Npcap 0.01 call for test about Windows loopback traffic capture feature

2015-07-14 Thread Pascal Quantin
2015-07-11 11:15 GMT+02:00 Yang Luo : > Hi list, > > In order not to diverge with WinPcap interfaces, I have made a "WinPcap > Mode" for Npcap, it uses the same system32 directory to put DLLs and has > the same "npf" service and driver name. So it can be directly used in > Wireshark without any pa

Re: [Wireshark-dev] Wireshark messages I don't want to see

2015-07-14 Thread Joerg Mayer
On Tue, Jul 14, 2015 at 11:52:18AM -0700, Guy Harris wrote: > Line 1558 of epan/crypt/airpdcap.c is > > if (ctx->sa[ctx->first_free_index].used) { > > in AirPDcapStoreSa(). It was assuming that ctx->first_free_index would be > within the bounds of the array, which isn't guaranteed (what

Re: [Wireshark-dev] Wireshark messages I don't want to see

2015-07-14 Thread Guy Harris
On Jul 14, 2015, at 11:01 AM, Joerg Mayer wrote: > ... but have no idea how to find or fix: Line 158 of the current epan/address.h is the memcpy(to_data, from->data, from->len); in copy_address(). The fact that it didn't *crash* is probably because from->len is zero, so it didn't a

Re: [Wireshark-dev] Wireshark messages I don't want to see

2015-07-14 Thread Peter Wu
Hi Jörg, On Tue, Jul 14, 2015 at 08:01:38PM +0200, Joerg Mayer wrote: > ... but have no idea how to find or fix: > > jmayer@egg privat$ wireshark -r 6.pcap.gz > /home/jmayer/work/wireshark/git/epan/address.h:158:5: runtime error: null > pointer passed as argument 1, which is declared to never be

Re: [Wireshark-dev] Enabling/disabling ANY heuristic dissector

2015-07-14 Thread Guy Harris
On Jul 14, 2015, at 4:23 AM, mman...@netscape.net wrote: > I started looking at the long options, but I thought they also needed a > corresponding mnemonic letter as well. No - part of the whole reason for long options is to give you an escape when you run out of the subset of ASCII characters

[Wireshark-dev] Wireshark messages I don't want to see

2015-07-14 Thread Joerg Mayer
... but have no idea how to find or fix: jmayer@egg privat$ wireshark -r 6.pcap.gz /home/jmayer/work/wireshark/git/epan/address.h:158:5: runtime error: null pointer passed as argument 1, which is declared to never be null /home/jmayer/work/wireshark/git/epan/address.h:158:5: runtime error: null

Re: [Wireshark-dev] Enabling/disabling ANY heuristic dissector

2015-07-14 Thread mmann78
I started looking at the long options, but I thought they also needed a corresponding mnemonic letter as well. I'll take a look at what you put in Gerrit. Thanks for the head start! -Original Message- From: Jim Young To: Developer support list for Wireshark Sent: Tue, Jul 14, 2015

Re: [Wireshark-dev] Enabling/disabling ANY heuristic dissector

2015-07-14 Thread Guy Harris
On Jul 13, 2015, at 5:27 PM, mman...@netscape.net wrote: > Command-line option sounds good, but it will probably take longer to figure > out the option letter (how many do we have left?) than the functionality that > does the enable/disable. Suggestions for option "letter" to use? Have we >