That was a timer problem in TCP code way back then.
I did notice it sometime around 1.3.5x, and gave enough
traces for Alan to figure it out. Arnt has 2.0.28, on
which the 16 second timeout horizon does not touble anymore.
The default connection timeout for TCP is (as I recall)
30 minutes (well, at least SEVERAL minutes.)
> This is important because wireless interfaces may be temporarily out of
> radio coverage and lose network connectivity for that time period.
>
> In Mobile-IP, a linux machine can move from one IP network to another IP
> network. Will the consequent change of routes affect linux TCP in any
> adverse way? (for instance timing, state of TCP connection)
>
> Is there any documentation on the net regarding the implementation of
> Linux's TCP/IP stack, particularly the TCP portion?
In the KHG ? Apparently not..
http://www.redhat.com:8080/HyperNews/get/khg.html
> Thanks,
> CCFoo
>
> More info about a Mobile-IP implementation for Linux can be obtained from
> http://mip.ee.nus.sg
> Another implementation is available in
> http://anchor.cs.binghamton.edu/~mobileip
/Matti Aarnio <matti.aarnio@tele.fi>