This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

cable TV box - slow - DUP ACK

0

I've been having painfully slow downloads on my Cable TV boxes for the last couple of months and I've been trying to solve the problem.

using port mirroring, I've managed to create a wireshark port capture of what is happening when I run a speed test on the cable tv box. The cable box IP is 192.168.55.253 in this case.

http://www.megafileupload.com/97uX/portcapturefoxtelfailing.pcapng

There seems to be a whole heap of TCP DUP ACK going on, would that have something to do with it?

asked 08 Aug '15, 23:51

toddfraser88's gravatar image

toddfraser88
6112
accept rate: 0%


2 Answers:

1

Let me rephrase the question: why does the speed test fail when connecting via a MikroTik router?

The 'speed-test' consists of an HTTP GET request of a large (10576244) file.
The test fails because the TCP sessions do not recover from packet loss instead the TV box closes the connection prematurely after 6 seconds not waiting long enough for the retransmission to be successful.

The succeeding speedtests via the netgear router do not show any packet loss.

So unless you can convince the TV box to wait longer for a successful retransmission,to fix this problem you need to avoid the packet loss.
As the number of segments in flight is not dramatically high due to the low windowsize offering my bet is that you are suffering from the default queue size being too low in your MikroTik router.

As per http://wiki.mikrotik.com/wiki/Manual:Queue_Size - Default-small queue type "By default most of the queues in RouterOS have queue size of 10. "

This is probably not enough to get a seamless packet-flow going .

Maybe this problem is better addressed to the http://forum.mikrotik.com/

Regards Matthias

answered 15 Aug '15, 09:00

mrEEde's gravatar image

mrEEde
3.9k152270
accept rate: 20%

0

"There seems to be a whole heap of TCP DUP ACK going on, would that have something to do with it?"

If you refer to 'it' as the slow downloads the answer is no.
The poor download performance is is more owed to the low windowsize offering of the cable box that does not grow above 17520 bytes.
At an average RTT of more than 50ms this will always be the bottleneck. See the discussions on Bandwidth Delay Product

Regards Matthias

answered 12 Aug '15, 00:22

mrEEde's gravatar image

mrEEde
3.9k152270
accept rate: 20%

I've grabbed a port capture of when it's working.

it seems window size is identical when it's working properly.

http://www.megafileupload.com/97vX/portcapturefoxtelworking.pcapng

this is using an old netgear WNDR3700

the router i've replaced it with is a mikrotik RB951G-2HnD

Can you see anything in these capture results that might explain why it fails vs when its working?

(12 Aug '15, 01:51) toddfraser88

I still need help with this.

(13 Aug '15, 11:46) toddfraser88

So it seems that in the failling case the server stops sending 6 seconds before the FIN from the client comes. But the reason could not be seen...

(13 Aug '15, 16:39) Christian_R

do you think a port capture from the WAN port would help?

(13 Aug '15, 23:48) toddfraser88

No, not really.

(14 Aug '15, 00:49) Christian_R

@toddfraser88

Your "answers" have been converted to comments as that's how this site works. Please read the FAQ for more information.

(14 Aug '15, 01:57) grahamb ♦

So the question you need an answer is: Why does the speed test fail to 192.168.55.253 when it succeeds to 192.168.1.145 ? Those are different TV boxes in different networks?

(15 Aug '15, 00:17) mrEEde

same modem, same tv box, same Ethernet cable, except in the working i put the mikrotik in switch mode and put the WNDR3700 in between it and the modem.

so the WNDR3700 does something differently that makes it work properly, I've no idea what though.

I've even tried reseting the mikrotik with no default configuration and setting it up entirely from scratch, even with the most basic config in place, the problem persists.

(15 Aug '15, 03:56) toddfraser88
showing 5 of 8 show 3 more comments