Wireshark-dev: Re: [Wireshark-dev] Jurassic packets
From: ronnie sahlberg <[email protected]>
Date: Thu, 13 Jun 2013 13:27:23 -0700
Can you try loading an NFS trace on it?

I recall that in the old days,  sniffers usually could not decode the
NFS replies since they did not keep enough state around between
request/response to identify what kind of response packet it was.



On Thu, Jun 13, 2013 at 11:09 AM, Gerald Combs <[email protected]> wrote:
> For Monday's Sharkfest keynote I wanted to show everyone what things
> looked like back in the early days of the project. After doing
> unspeakable things to a Red Hat 6.2 VM I managed to get a copy of
> Ethereal 0.2.0 up and running. Screenshot attached.
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <[email protected]>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:[email protected]?subject=unsubscribe