Hello friends,
We have a packet capturing application product. we have developed a tool in
which we first get the captured packet data ( pcap file based on metadata
information provided in query) and provided a button on the GUI of the tool
to open the retrieved packet data (pcap file) in
There has been discussion over the years about standardizing the way checksums
are handled in Wireshark. A lot of the discussion has been captured in bug
8859 [1], and I started writing a patch that would address it [2].
In developing the patch, I came across the following types of checksum
On 07/14/2016 02:44 AM, Michael Mann wrote:
I've done some investigation into the build warnings generated by the
Ubuntu and Windows buildbots. I thought I'd highlight some of the "big
offenders" so that if anyone has good ideas on how to fix them, it may
lead to thinning the forest out
I've done some investigation into the build warnings generated by the Ubuntu
and Windows buildbots. I thought I'd highlight some of the "big offenders" so
that if anyone has good ideas on how to fix them, it may lead to thinning the
forest out enough that we can see trees (and the raw number
On Wed, Jul 13, 2016 at 10:53 AM, Paul Offord
wrote:
> Hi,
>
>
>
> I recently measured some load and filter times with and without a LUA
> postdissector plugin called TRANSUM. I tried three different scenarios:
>
>
>
> ·No LUA - without any plugins other than
Hi,
I recently measured some load and filter times with and without a LUA
postdissector plugin called TRANSUM. I tried three different scenarios:
*No LUA - without any plugins other than those shipped as standard
*Bypassed LUA - with TRANSUM but a preference set so that on
Hi Tomek,
On Wed, Jul 13, 2016 at 11:20 AM, Tomek Mrugalski <
tomasz.mrugal...@gmail.com> wrote:
> Hi!
>
> Long time user, first time trying to extend the code and would like to
> ask for a bit of guidance. I'm trying to extend DHCPv6 (packet-dhcpv6.c)
> dissector to support RFC7598. Couple
Hi!
Long time user, first time trying to extend the code and would like to
ask for a bit of guidance. I'm trying to extend DHCPv6 (packet-dhcpv6.c)
dissector to support RFC7598. Couple options in that RFC uses new option
format that stores IPv6 prefix as two fields:
1. prefix-len (1 octet,