--- In Bob Lees <> wrote:
>
> If you google for this you will find this problem has been well
exercised in
> the past, not on this list but on lists in general. It is a
"feature" of the
> way the TCP/IP stack works and unfortunately there is no magic bullet!
I saw exactly the same behavior on AIX (Unix for the IBM RS-6000) in
the early '90s. At that point it was explained to me that this delay
before a port can be reused is intentional. It is designed to prevent
any packets which are already in transit when the port gets closed
from causing problems. If a new socket opens immediately with the same
port number, these pokey packets will show up at that socket
unexpectedly. There is a small but finite chance that they will be
interpreted as valid packets. Of course, a packet could theoretically
be delayed for hours, but the timeout of 30 seconds or so was
considered long enough to reduce the chance of error to an acceptable
level.
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|