Thread View: demon.ip.developers
3 messages
3 total messages
Started by Chris Croughton
Fri, 28 Aug 1998 00:00
KA9Q reassembly queue?
Author: Chris Croughton
Date: Fri, 28 Aug 1998 00:00
Date: Fri, 28 Aug 1998 00:00
27 lines
1575 bytes
1575 bytes
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? In some cases it runs to 10 or 15 lines in the queue. I
thought at first it was something to do with the packet sizes, but they are
all 576/536 as standard. (the 83 bytes in that example is unusual, usually
they are all 512 bytes).
Is this something wrong with my configuration, or is it normal?
Chris C
Re: KA9Q reassembly queue?
Author: Richard Clayton
Date: Fri, 28 Aug 1998 00:00
Date: Fri, 28 Aug 1998 00:00
36 lines
1907 bytes
1907 bytes
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
Re: KA9Q reassembly queue?
Author: Chris Croughton
Date: Tue, 01 Sep 1998 00:00
Date: Tue, 01 Sep 1998 00:00
24 lines
1728 bytes
1728 bytes
In article <w8ZHv2AsEq51EAxQ@turnpike.com>
richard@turnpike.com "Richard Clayton" wrote:
>you have lost a 512 byte packet 5592489c-55924a9b
>later packets have arrived
Ah, that makes sense, and now you point it out I see the 'hole'.
>>Is this something wrong with my configuration, or is it normal?
>usual first question is "any overruns reported ?"
No, but doing "ping" does indicate that I'm losing up to 30% of the
packets to/from Demon. What I didn't tell you was that this is collecting
mail and news from Demon via my ISP in Germany - a hop check indicates
that most of these are being lost at either side of the Finchley router,
it's fine up to the London nodes outside Demon but finch*.demon.co.uk is
losing packets and the next node inside DEmon seemed to be losing even
more (I don't have a trace yet, when I do I'll post it - demon.service, or
direct to one of the demon.net addresses?).
In fact, it proved cheaper to dial international to Britain than to try to
get 900+ messages through the international link...
Chris C
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads