From: Russ Fink (russfink@hotmail.com)
Date: 08/31/04
From: "Russ Fink" <russfink@hotmail.com> Subject: RE: tcptrace how to know that UDP connection has stop? Date: Tue, 31 Aug 2004 09:51:52 -0400 Message-ID: <BAY1-F41HMh3LqPg33I00051ab0@hotmail.com>
>From: Lau Ker Chea <kerchea79@yahoo.com>
>
>tcptrace groups UDP connections from the same pair of IP addresses and same
>pair of UDP ports to belong to a connection. how do we know that the data
>transmission btw both sides is finish since UDP will not giv
>acknowledgement to other host to say that i wan to stop...
This question has little to do with tcptrace. The UDP protocol is
connectionless. You will have to inspect the upper layer protocols (e.g.,
application layer) to decide whether a transmission is complete. You could
take a timeout approach, and "give up" if you don't see any data on the
connection for "a while," whatever you decide that to be. Not sure how to
do this in tcptrace.
On the other hand, if some application is using UDP for inherently
client-server communications, then it should really be using TCP unless
there is a compelling reason not to. If you are designing the application,
you may wish to rethink it.
Russ
_________________________________________________________________
Check out Election 2004 for up-to-date election news, plus voter tools and
more! http://special.msn.com/msn/election2004.armx
----------------------------------------------------------------------------
To unsubscribe, send a message with body containing "unsubscribe tcptrace" to
majordomo@tcptrace.org.
This archive was generated by hypermail 2.1.7 : 08/31/04 EDT