🚀 go-pugleaf

In article <Snews.980828.091855.chris.10879@keris.demon.co.uk>, Chris
Croughton <chris@keris.demon.co.uk> writes

>I keep getting (particularly on NNTP sockets) the transfer stopping and
>when I do a socket <n> to look at it I see something like:
>
>net> so 136
>TCP 852a0008 ascii eol seq: 0d 0a
>Local: 193.197.64.61:1053 Remote: 194.159.247.38:119 State: Established
>      Init seq    Unack     Next Resent CWind Thrsh  Wind  MSS Queue
>Total
>Send: 1adf5000 1adf6c34 1adf6c98   4016   536   536 17276  536   100
>7219
>Recv: 55901b97          5592489c  12970             11680          0
>142596
>Reassembly queue:
>  seq x55924a9c 512 bytes
>  seq x55924c9c 512 bytes
>  seq x55924e9c 83 bytes
>  seq x55924eef 512 bytes
>Backoff 1 Timer running (27720/28710 ms) SRTT 2614 ms Mean dev 2926 ms
>
>What is this?

you have lost a 512 byte packet  5592489c-55924a9b

later packets have arrived

>Is this something wrong with my configuration, or is it normal?

usual first question is "any overruns reported ?"

-- 
richard                       writing to inform and not as company policy
 http://www.demon.net/news/features/crypto/  for Demon's views on crypto
"Assembly of Japanese bicycle require great peace of mind" quoted in ZAMM