Re: High-latency link & tunnels: strange problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Herbert Xu wrote:

> >> tcpdump -i tun0 -n
> >> 23:53:01.984205 62.x.x.219.44364 > 62.x.x.217.http: . ack 140200 win
63591 <nop,nop,timestamp 20631295 53137471> (DF)
> >> 23:53:01.995589 62.x.x.217.http > 62.x.x.219.44364: .
140200:141553(1353) ack 1 win 5792 <nop,nop,timestamp 53137471 20631222>
(DF)
> >> 23:53:01.995598 62.x.x.219.44364 > 62.x.x.217.http: . ack 141553 win
63591 <nop,nop,timestamp 20631296 53137471> (DF)
> >> 23:53:02.033656 62.x.x.217.http > 62.x.x.219.44364: .
141553:142906(1353) ack 1 win 5792 <nop,nop,timestamp 53137475 20631230>
(DF)
> >> 23:53:02.033666 62.x.x.219.44364 > 62.x.x.217.http: . ack 142906 win
63591 <nop,nop,timestamp 20631300 53137475> (DF)
> >> 23:53:02.075913 62.x.x.217.http > 62.x.x.219.44364: .
142906:144259(1353) ack 1 win 5792 <nop,nop,timestamp 53137480 20631231>
(DF)
>
> You're dumping at the wrong end.  Show us the dump at the server
> end and we might be able to help you.

Here's the direct transfer dump at the server end (server running in the
internet, 100 mbps WAN connection, linux 2.4.27):

[root@ve0 root]# tcpdump -i eth0 -n host 80.x.x.177 and port http
tcpdump: listening on eth0
09:39:24.827539 80.x.x.177.41280 > 62.x.x.217.http: S
3216460786:3216460786(0) win 24120 <mss 1460>
09:39:24.827587 62.x.x.217.http > 80.x.x.177.41280: S
1247797054:1247797054(0) ack 3216460787 win 5840 <mss 1460> (DF)
09:39:24.849845 80.x.x.177.41280 > 62.x.x.217.http: . ack 1 win 5840
09:39:25.508654 80.x.x.177.41280 > 62.x.x.217.http: P 1:109(108) ack 1 win
5840
09:39:25.508717 62.x.x.217.http > 80.x.x.177.41280: . ack 109 win 5840 (DF)
09:39:25.509088 62.x.x.217.http > 80.x.x.177.41280: . 1:1461(1460) ack 109
win 5840 (DF)
09:39:25.509103 62.x.x.217.http > 80.x.x.177.41280: . 1461:2921(1460) ack
109 win 5840 (DF)
09:39:25.531489 80.x.x.177.41280 > 62.x.x.217.http: . ack 2921 win 2920
09:39:25.531549 62.x.x.217.http > 80.x.x.177.41280: P 2921:4381(1460) ack
109 win 5840 (DF)
09:39:25.531555 62.x.x.217.http > 80.x.x.177.41280: . 4381:5841(1460) ack
109 win 5840 (DF)
09:39:25.563302 80.x.x.177.41280 > 62.x.x.217.http: . ack 5841 win 0
09:39:25.776159 62.x.x.217.http > 80.x.x.177.41280: . ack 109 win 5840 (DF)
09:39:25.793513 80.x.x.177.41280 > 62.x.x.217.http: . ack 5841 win 0
.....................

And this is the tunnel one:

[root@ve0 root]# tcpdump -i tun0 -n port http
tcpdump: listening on tun0
09:12:15.383072 62.x.x.219.40761 > 62.x.x.217.http: S
1487389279:1487389279(0) win 5840 <mss 1365,sackOK,timestamp 2435965
0,nop,wscale 0> (DF)
09:12:15.383101 62.x.x.217.http > 62.x.x.219.40761: S
3836440495:3836440495(0) ack 1487389280 win 5792 <mss 1460,sackOK,timestamp
56497361 2435965,nop,wscale 0> (DF)
09:12:16.110259 62.x.x.219.40761 > 62.x.x.217.http: . ack 1 win 5840
<nop,nop,timestamp 2436039 56497361> (DF)
09:12:16.160778 62.x.x.219.40761 > 62.x.x.217.http: P 1:109(108) ack 1 win
5840 <nop,nop,timestamp 2436039 56497361> (DF)
09:12:16.160812 62.x.x.217.http > 62.x.x.219.40761: . ack 109 win 5792
<nop,nop,timestamp 56497439 2436039> (DF)
09:12:16.161216 62.x.x.217.http > 62.x.x.219.40761: . 1:1354(1353) ack 109
win 5792 <nop,nop,timestamp 56497439 2436039> (DF)
09:12:16.161228 62.x.x.217.http > 62.x.x.219.40761: . 1354:2707(1353) ack
109 win 5792 <nop,nop,timestamp 56497439 2436039> (DF)
09:12:16.884832 62.x.x.219.40761 > 62.x.x.217.http: . ack 1354 win 8118
<nop,nop,timestamp 2436117 56497439> (DF)
09:12:16.884861 62.x.x.217.http > 62.x.x.219.40761: P 2707:4060(1353) ack
109 win 5792 <nop,nop,timestamp 56497511 2436117> (DF)
09:12:16.884865 62.x.x.217.http > 62.x.x.219.40761: . 4060:5413(1353) ack
109 win 5792 <nop,nop,timestamp 56497511 2436117> (DF)

Both transfers where made from the same host.

> What is the server running BTW?

My end runs at linux 2.4.27. Server end runs the same system currently, but
I've tried another server wich I have access to, it runs linux 2.4.20 or so.

-- vlad


-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux