Re: Need some Info.

From: Shashank (shashank@evl.uic.edu)
Date: 01/16/01

  • Next message: Ivanovich, Milosh: "An "IP Level Version" of TCPTrace, IPTrace if you will :-)" 

    Date: Tue, 16 Jan 2001 16:00:04 -0600 (CST)
From: Shashank <shashank@evl.uic.edu>
Subject: Re: Need some Info.
Message-ID: <Pine.SGI.3.95.1010116155708.1937001h-100000@laurel.evl.uic.edu>

    Hi Simon,
    Thanks for the ans..
    I think u r right abt the first ans.. I retried my experiments by
    increaing the snaplenght and I got everything right.. (thanks)..

    Also I found the ans to the 2nd question...R. Stevens has dedicated his
    Volume III to something called T/TCP (Transaction TCP). the cc option us
    used by T/TCP. more information can be found in RFC1644(i think) or TCP/IP
    illistrated VOl III.)

    Regards
    Shashank

    > > 1. What is the last option that is specified in the SYNC packet
    > > ([|tcp]),
    >
    > This is tcpdump's way of saying that the header in question (tcp)
    > couldn't be decoded in its entirety because it was cut off early. By
    > default, tcpdump collects only the first 68 bytes of each packet.
    > Call tcpdump with the -s option to specify a larger "snaplen" (e.g.
    > -s 1500). Then tcpdump will decode the complete header.
    >
    > > 2. the "cc"option specifiesd in one of the data packets. It seems
    > > that this option is used by T/TCP, to minimize the number of
    > > segments exchanged in a single transation.. Is this correct??
    >
    > No idea.
    > --
    > Simon.
    > ----------------------------------------------------------------------------
    > To unsubscribe, send a message with body containing "unsubscribe tcptrace" to
    > majordomo@tcptrace.org.
    >

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

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