* Strange TCP dump between a Linux and a Samsung phone
@ 2008-11-11 14:05 ROUTE 66 - Catalin BOIE
2008-11-11 15:05 ` Ilpo Järvinen
0 siblings, 1 reply; 3+ messages in thread
From: ROUTE 66 - Catalin BOIE @ 2008-11-11 14:05 UTC (permalink / raw)
To: netdev
Hello!
I have captured a strange dump between a Linux kernel
2.6.25.6-55.fc9.x86_64 and a Samsung device.
I looked at it and it seems that the Linux stack does not send any
retransmissions to Samsung device.
But, I want a competent look from you.
The connection is done over a 3G connection.
The capture was done on a router between the two endpoints.
c.66.com is the Linux machine, the other IP is the Samsung device.
The last packets of the capture are:
11:31:36.816467 IP 213.233.90.58.32119 > c.66.com.http: . ack 1238481
win 65535
11:31:37.814711 IP 213.233.90.58.32119 > c.66.com.http: . ack 1238481
win 65535
11:31:38.814366 IP 213.233.90.58.32119 > c.66.com.http: . ack 1238481
win 65535
11:31:39.099101 IP c.66.com.http > 213.233.90.58.32119: .
1238481:1239941(1460) ack 414 win 6432
11:31:39.774267 IP 213.233.90.58.32119 > c.66.com.http: . ack 1242861
win 65535
11:31:39.774430 IP c.66.com.http > 213.233.90.58.32119: .
1253081:1254541(1460) ack 414 win 6432
11:31:39.774439 IP c.66.com.http > 213.233.90.58.32119: .
1254541:1256001(1460) ack 414 win 6432
11:31:39.954781 IP 213.233.90.58.32119 > c.66.com.http: . ack 1242861
win 65535
11:31:39.954921 IP c.66.com.http > 213.233.90.58.32119: .
1256001:1257461(1460) ack 414 win 6432
11:31:40.135381 IP 213.233.90.58.32119 > c.66.com.http: . ack 1242861
win 65535
11:31:40.135519 IP c.66.com.http > 213.233.90.58.32119: .
1257461:1258921(1460) ack 414 win 6432
11:31:40.314255 IP 213.233.90.58.32119 > c.66.com.http: . ack 1242861
win 65535
11:31:40.314398 IP c.66.com.http > 213.233.90.58.32119: .
1242861:1244321(1460) ack 414 win 6432
11:31:40.974698 IP 213.233.90.58.32119 > c.66.com.http: . ack 1254541
win 65535
11:31:40.974849 IP c.66.com.http > 213.233.90.58.32119: .
1254541:1256001(1460) ack 414 win 6432
11:31:41.636247 IP 213.233.90.58.32119 > c.66.com.http: . ack 1258921
win 65535
11:31:41.636423 IP c.66.com.http > 213.233.90.58.32119: .
1258921:1260381(1460) ack 414 win 6432
11:31:41.636432 IP c.66.com.http > 213.233.90.58.32119: .
1260381:1261841(1460) ack 414 win 6432
11:31:41.636439 IP c.66.com.http > 213.233.90.58.32119: .
1261841:1263301(1460) ack 414 win 6432
11:31:52.564127 IP c.66.com.http > 213.233.90.58.32119: .
1258921:1260381(1460) ack 414 win 6432
11:31:53.765346 IP 213.233.90.58.32119 > c.66.com.http: . ack 1260381
win 65535
11:31:53.765534 IP c.66.com.http > 213.233.90.58.32119: .
1263301:1264761(1460) ack 414 win 6432
11:31:53.765547 IP c.66.com.http > 213.233.90.58.32119: .
1264761:1266221(1460) ack 414 win 6432
11:31:53.926119 IP 213.233.90.58.32119 > c.66.com.http: . ack 1260381
win 65535
11:31:53.926258 IP c.66.com.http > 213.233.90.58.32119: .
1266221:1267681(1460) ack 414 win 6432
11:31:53.945502 IP 213.233.90.58.32119 > c.66.com.http: . ack 1260381
win 65535
11:31:54.105085 IP 213.233.90.58.32119 > c.66.com.http: . ack 1260381
win 65535
11:31:54.925746 IP 213.233.90.58.32119 > c.66.com.http: . ack 1260381
win 65535
11:31:55.924180 IP 213.233.90.58.32119 > c.66.com.http: . ack 1260381
win 65535
11:31:56.945416 IP 213.233.90.58.32119 > c.66.com.http: . ack 1260381
win 65535
11:31:57.945049 IP 213.233.90.58.32119 > c.66.com.http: . ack 1260381
win 65535
11:31:58.945921 IP 213.233.90.58.32119 > c.66.com.http: . ack 1260381
win 65535
11:31:59.945681 IP 213.233.90.58.32119 > c.66.com.http: . ack 1260381
win 65535
11:32:00.944815 IP 213.233.90.58.32119 > c.66.com.http: . ack 1260381
win 65535
11:32:01.945018 IP 213.233.90.58.32119 > c.66.com.http: . ack 1260381
win 65535
11:32:02.946170 IP 213.233.90.58.32119 > c.66.com.http: . ack 1260381
win 65535
11:32:15.621126 IP c.66.com.http > 213.233.90.58.32119: .
1260381:1261841(1460) ack 414 win 6432
11:32:16.823395 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:16.823565 IP c.66.com.http > 213.233.90.58.32119: .
1267681:1269141(1460) ack 414 win 6432
11:32:16.823574 IP c.66.com.http > 213.233.90.58.32119: .
1269141:1270601(1460) ack 414 win 6432
11:32:16.983981 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:16.984137 IP c.66.com.http > 213.233.90.58.32119: .
1270601:1272061(1460) ack 414 win 6432
11:32:16.984147 IP c.66.com.http > 213.233.90.58.32119: .
1272061:1273521(1460) ack 414 win 6432
11:32:17.003214 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:17.143529 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:17.163862 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:17.983174 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:18.983839 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:19.983172 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:20.984122 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:21.983888 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:22.985082 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:24.002955 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:25.003203 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:26.004390 IP 213.233.90.58.32119 > c.66.com.http: . ack 1261841
win 65535
11:32:56.453482 IP 213.233.90.58.32119 > c.66.com.http: F 414:414(0) ack
1261841 win 65535
11:32:56.493122 IP c.66.com.http > 213.233.90.58.32119: . ack 415 win 6432
11:33:00.535158 IP c.66.com.http > 213.233.90.58.32119: .
1261841:1263301(1460) ack 415 win 6432
11:33:01.162502 IP 213.233.90.58.32119 > c.66.com.http: R
777650211:777650211(0) win 0
As you may see, the Samsung device keeps sending an ACK for 1261841 and
after some time closes the connection.
Why the Linux stack does no retransmissions?
Thank you very much!
--
Catalin BOIE
ROUTE 66
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Strange TCP dump between a Linux and a Samsung phone
2008-11-11 14:05 Strange TCP dump between a Linux and a Samsung phone ROUTE 66 - Catalin BOIE
@ 2008-11-11 15:05 ` Ilpo Järvinen
2008-11-12 7:15 ` ROUTE 66 - Catalin BOIE
0 siblings, 1 reply; 3+ messages in thread
From: Ilpo Järvinen @ 2008-11-11 15:05 UTC (permalink / raw)
To: ROUTE 66 - Catalin BOIE; +Cc: Netdev
On Tue, 11 Nov 2008, ROUTE 66 - Catalin BOIE wrote:
> I have captured a strange dump between a Linux kernel
> 2.6.25.6-55.fc9.x86_64 and a Samsung device.
Please upgrade or prove that the tcp fixes that were in the later kernel
(.7 iirc or 2.6.26) got applied into that -55 part.
> I looked at it and it seems that the Linux stack does not send any
> retransmissions to Samsung device.
> But, I want a competent look from you.
>
> The connection is done over a 3G connection.
> The capture was done on a router between the two endpoints.
> c.66.com is the Linux machine, the other IP is the Samsung device.
...snip...
> As you may see, the Samsung device keeps sending an ACK for 1261841 and
> after some time closes the connection.
> Why the Linux stack does no retransmissions?
Looks like a know bug in frto which got fixed.
If upgrade is not an option, you can experiment by playing with tcp_frto
sysctl (with 0 you should not encounter that bug).
--
i.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Strange TCP dump between a Linux and a Samsung phone
2008-11-11 15:05 ` Ilpo Järvinen
@ 2008-11-12 7:15 ` ROUTE 66 - Catalin BOIE
0 siblings, 0 replies; 3+ messages in thread
From: ROUTE 66 - Catalin BOIE @ 2008-11-12 7:15 UTC (permalink / raw)
To: �; +Cc: Netdev
� wrote:
> On Tue, 11 Nov 2008, ROUTE 66 - Catalin BOIE wrote:
Hello!
After upgrading to 2.6.26.?, the problem was fixed!
Thank you very much for your super quick answer!
>> I have captured a strange dump between a Linux kernel
>> 2.6.25.6-55.fc9.x86_64 and a Samsung device.
>
> Please upgrade or prove that the tcp fixes that were in the later kernel
> (.7 iirc or 2.6.26) got applied into that -55 part.
>> I looked at it and it seems that the Linux stack does not send any
>> retransmissions to Samsung device.
>> But, I want a competent look from you.
>>
>> The connection is done over a 3G connection.
>> The capture was done on a router between the two endpoints.
>> c.66.com is the Linux machine, the other IP is the Samsung device.
>
> ...snip...
>
>> As you may see, the Samsung device keeps sending an ACK for 1261841 and
>> after some time closes the connection.
>> Why the Linux stack does no retransmissions?
>
> Looks like a know bug in frto which got fixed.
>
> If upgrade is not an option, you can experiment by playing with tcp_frto
> sysctl (with 0 you should not encounter that bug).
Thanks!
--
Catalin BOIE
ROUTE 66
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-11-12 7:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-11-11 14:05 Strange TCP dump between a Linux and a Samsung phone ROUTE 66 - Catalin BOIE
2008-11-11 15:05 ` Ilpo Järvinen
2008-11-12 7:15 ` ROUTE 66 - Catalin BOIE
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).