On Thu, 07 Oct 1999, Steve Dodd wrote:
> The pattern I've noticed so far seems to be that whenever the sending host
> queues multiple segments in quick succession, the remote host only ever sees
> the first:
>
> We see:
>
> 00:33:46.748313 loth.1131 > moria-eth.1883: P 1:1449(1448) ack 1 win 32120
><nop,nop,timestamp 1020677 71896360> (DF)
> 00:33:46.749684 loth.1131 > moria-eth.1883: P 1449:2897(1448) ack 1 win 32120
><nop,nop,timestamp 1020677 71896360> (DF)
> 00:33:47.366914 moria-eth.1883 > loth.1131: . ack 1449 win 31856 <nop,nop,timestamp
>71896444 1020677> (DF) [tos 0x10]
>
> The remote sees:
>
> 00:33:58.678060 loth.1131 > moria-eth.1883: P 1:1449(1448) ack 1 win 32120
><nop,nop,timestamp 1020677 71896360> (DF)
> 00:33:58.678334 moria-eth.1883 > loth.1131: . ack 1449 win 31856 <nop,nop,timestamp
>71896444 1020677> (DF) [tos 0x10]
I would love to see what characters the remote reads from its serial
port. At first glance this looks like the second packet is getting
corrupted by a serial overrun or something like that. Does the remote run
Linux? Could you use the `record' option on pppd at that end to see
whether the second packet is just not there, or if it is there but
corrupted?
Paul.
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
