> 17:52:08.920000 THEM.www > ME.2900: . 88202:89174(972) ack 625 win 9720 
><nop,nop,timestamp 37623391 243244922> (DF)
> 
> 17:52:09.260000 THEM.www > ME.2900: . 89174:90146(972) ack 625 win 9720 
><nop,nop,timestamp 37623391 243244922> (DF)
> 
> 17:52:09.260000 ME.2900 > THEM.www: . ack 90146 win 31104 <nop,nop,timestamp 
>243246035 37623391> (DF)

Note the ack value here is 90146

> 17:52:09.620000 THEM.www > ME.2900: . 92090:93062(972) ack 625 win 9720 
><nop,nop,timestamp 37623529 243245061> (DF)

This data is after a frame is missed.

> 17:52:09.620000 ME.2900 > THEM.www: . ack 90146 win 31104 <nop,nop,timestamp 
>243246071 37623529,nop,nop,sack 26369@63727 27341@63727> (DF)
> 
> 17:52:09.960000 THEM.www > ME.2900: . 93062:94034(972) ack 625 win 9720 
><nop,nop,timestamp 37623529 243245061> (DF)

We keep acking the old value, and it keeps moving on sending newer and newer
valid data but always with the hole. It looks like you may have a modem config
problem or something similar that stops some specific bitpattern from being
passed.


-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]

Reply via email to