Re: [Wireshark-dev] Something that would be useful in Wireshark when dealing with dropped packets

2018-12-30 Thread ronnie sahlberg
That is a really good idea, but instead of you having to manually search for where the next pdu starts, it would be possible to teach wireshark to do this automatically. We already track the PDU boundaries for SMB as well as a bunch other protocols so we know where a pdu starts/stops, most of the

[Wireshark-dev] Something that would be useful in Wireshark when dealing with dropped packets

2018-12-30 Thread Richard Sharpe
Hi folks, I recently had to perform some surgery on a packet capture that had dropped packets. I was capturing a GbE link that was operating at capacity and a few packets were dropped in the area I was interested in. I was chasing the reason that the current Mac OS X smbfs would disconnect from

Re: [Wireshark-dev] Cannot get external capture (extcap) interface to work with my new plugin.

2018-12-30 Thread Roland Knall
Hi Have you properly closed the pipe after sending the packets? It looks more like an issue in flushing the pipe, then a code error. tshark handles this a little bit different then wireshark, so that might be the reason, why it did work on the CLI. Try flushing the pipe immediately after every pa

[Wireshark-dev] Cannot get external capture (extcap) interface to work with my new plugin.

2018-12-30 Thread hdv
Hello, I'm developing a new extcap interface as described in chapter 8.2.1 of the developers guide. The goal is to implement a plugin so I can directly attach it to a CAN bus sniffing device called "AnaGate CAN" (see http://www.anagate.de/) Until now all went well, I can see my new interface in