Re: tcptrace stdin/pipe buffering

From: pripke@csc.com.au
Date: 10/17/02

  • Next message: Oriana Riva: "tcptrace initial window parameter" 

    Subject: Re: tcptrace stdin/pipe buffering
Message-ID: <OFC25F7A60.109AC29F-ONCA256C55.001A6AD5@int.csc.com.au>
From: pripke@csc.com.au
Date: Thu, 17 Oct 2002 14:51:46 +1000

    Cool, it works! Must be something strange with the "stdin" handling
    in compress.c.

    I ended up needing to do further analysis, so I currently have a nice
    1.4GB tcpdump to play with.

    Thanks,
    Paul Ripke

    |---------+--------------------------->
    | | Jose Manuel Cano|
    | | Garcia |
    | | <cano@pc2072te.d|
    | | te.uma.es> |
    | | |
    | | 16/10/2002 20:37|
    | | |
    |---------+--------------------------->
    >------------------------------------------------------------------------------------------------------------------------|
      | |
      | To: pripke@csc.com.au, tcptrace@tcptrace.org |
      | cc: |
      | Subject: Re: tcptrace stdin/pipe buffering |
    >------------------------------------------------------------------------------------------------------------------------|

    I have created a pipe with "mkfifo" and I did not have any problem:

    mkfifo tmppipe
    tcptrace -r -l tmppipe (in one terminal/command line)
    tcpdump -w tmppipe (in other terminal/command line)

    However, it is not very useful since tcptrace is not realtime and waits
    until
    the "end" of the file (or the capture) to print the results.

    Best regards,

     Jose Manuel

    ----------------------------------------------------------------------------
    To unsubscribe, send a message with body containing "unsubscribe tcptrace" to
    majordomo@tcptrace.org.

    This archive was generated by hypermail 2b30 : 10/17/02 EDT