tcptrace Connections set to INACTIve after 4 minutes idle time.

From: Brian Utterback (brian.utterback@Sun.COM)
Date: 01/27/03

  • Next message: Gianluca Colangelo (TEI): "tcptrace Removing encapsulation" 

    Message-ID: <3E353F76.3040406@sun.com>
Date: Mon, 27 Jan 2003 09:17:26 -0500
From: Brian Utterback <brian.utterback@Sun.COM>
Subject: tcptrace Connections set to INACTIve after 4 minutes idle time.

    I just came across something I didn't realize, although i may be alone
    on this.

    Apparently, tcptrace will mark a TCP connection as INACTIVE after 4
    minutes of idle time. This means that
    subsequent packets on the same connection are counted as a new
    connection. I am not sure of the reasoning
    here, but I notice that there is a variable to set the idle time
    connection for continuous capture mode, but the
    time is hard coded for capture file mode. I think this should at least
    be settable. 

    -- 
blu

    NTP: the protocol that ensures that a good time is had by all.
--------------------------------------------------------------------------------
Brian Utterback - PTS Network Support - Sun Microsystems Inc.,
Ph/VM: 781-442-1343, Em:brian.utterback@sun.com

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

    This archive was generated by hypermail 2b30 : 01/27/03 EST