On Wed, Jul 26, 2017 at 9:28 PM, maowenan <maowe...@huawei.com> wrote: > Ok, please check as below. Server: 192.169.0.18, client: 192.169.0.17 > ......
Thanks for this trace! Here is a condensed version that I believe should be equivalent, for those who are working on parsing what's going on: 2.239562 srv > cli: P 544:616(72) ack 351 win 92 2.240034 srv > cli: P 616:688(72) ack 351 win 92 2.260764 srv > cli: P 616:688(72) ack 351 win 92 # TLP 3.018020 cli > srv: . ack 616 win 1970 3.018386 srv > cli: P 688:760(72) ack 351 win 92 # srv sends B 3.022448 srv > cli: P 760:832(72) ack 351 win 92 # srv sends C 3.033813 cli > srv: P 351:0437(86) ack 616 win 1970 # data/ACK 616 3.034213 cli > srv: P 437:0523(86) ack 616 win 1970 # data/ACK 616 3.034633 srv > cli: . ack 523 win 92 3.039512 cli > srv: P 523:0659(136) ack 616 win 1970 3.040083 cli > srv: P 659:0795(136) ack 616 win 1970 3.040491 srv > cli: . ack 795 win 92 3.041161 cli > srv: P 795:0931(136) ack 616 win 1970 3.042828 cli > srv: P 931:1032(101) ack 616 win 1970 3.043198 srv > cli: . ack 1032 win 92 For the record, I posted my diagnosis of this issue in your thread for the v2 version of the patch. thanks, neal
