Wireshark mailing list archives

Re: Redirecting Wireshark output through a socket

From: Stephen Fisher <steve () stephen-fisher com>
Date: Thu, 15 Oct 2009 16:32:19 -0600


On Oct 15, 2009, at 12:30 PM, Jeff Morriss wrote:

In that case you should probably use 'tshark' and you could (I suppose
this would work on Windows) do something like:

tshark -V -r /some/cap/file | the_other_analyzer

though I doubt that the commercial tool will really understand this
output...


... and the text is subject to change occasionally


Steve

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe

Current thread:

Redirecting Wireshark output through a socket Gustavo (Oct 15)
- Re: Redirecting Wireshark output through a socket Jeff Morriss (Oct 15)
  - Re: Redirecting Wireshark output through a socket Stephen Fisher (Oct 15)
    - Re: Redirecting Wireshark output through a socket Eloy Paris (Oct 15)
  - Re: Redirecting Wireshark output through a socket Gustavo (Oct 16)
    - Re: Redirecting Wireshark output through a socket Peter Ross (Oct 16)
    - Re: Redirecting Wireshark output through a socket Jaap Keuter (Oct 16)
    - Re: Redirecting Wireshark output through a socket Jeff Morriss (Oct 16)
    - Re: Redirecting Wireshark output through a socket Gustavo (Oct 19)