Hi,
thanks for the reply
>
> Define "a segment"? Do you mean an IP datagram or fragment? If so
> then the answer is... Of course. That's not even necessarily under control
> of the application.
>
> TCP/IP is basically a stream of data with a few "Out Of Band"
> signalling conventions. Lots of the protocols such as smtp, ftp, http,
> etc, etc, use a line oriented protocol. They send ascii commands which
> are delimited by new lines, generally a CR/NL termination. A command
> may be split across several IP datagrams at the discretion of the low
> level protocol stacks (subject to the absence of the "do not fragment"
> option). The server at the other end merely reads lines. It does not
> know or care if that line came across on one, two, or more datagrams.
---------> I meant the segment to be the unit of data that TCP
gives to the IP and asks it to send to some destination.
Is it possible that TCP might give to the ip "PU" first,
and T the next time? or it that it gives the whole command
to the IP at a time. (Please note that I am NOT
referring to the IP fragmenting a given datagram into
"fragments".)
What I am interested in knowing is the ftp client instructing
in some way for it's TCP to send it's commands as a single
TCP segment. (In general, there is no one-to-one correspondence
with application writes and TCP writes). I see in the
ftp masquerading module (masq_ftp_out) that it is assumed
these commands are not split. Please correct me if I am
wrong.
--gopi
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
