Joined: 24 Aug 2009 Posts: 2070 Location: South Florida
Posted: Wed Oct 27, 2010 20:36 Post subject: TCP Congestion Control
After seeing this option in the newer builds, I decided to do some research.
I think most of us know that TCP Vegas has been implemented in the DD-WRT firmware for a long time, however I decided to use TCP Cubic due to the fact that I am on a DOCSIS 3.0 network with 40Mb/s DL and 5Mb/s Up.
The way my ISP operates is ridiculous. The DNS servers are located in Tampa, yet the routing table they use first contacts the main DHCP relay in Texas, then over to North Carolina, then to Tallahassee, FL and back to Tampa.
Since I've set my network up with Cubic, everything seems much faster (tracerts, pathping etc.)
Anybody else played around with this setting? What are your thoughts? _________________ Optware, the Right Way
Asus RT-AC68U
Asus RT-N66U
Asus RT-N10
Asus RT-N12
Asus RT-N16 x5
Asus WL520gU
Engenious ECB350
Linksys WRT600Nv1.1
Linksys WRT610Nv1
Linksys E2000
Netgear WNDR3300
SonicWall NSA220W
SonicWall TZ215W
SonicWall TZ205W
SonicWall TZ105W
Thanks for the wiki link. While interesting reading, it would be great if there were some kind of guidelines based on connection type/bandwidth as far as which algorithm would be most effective for a given type.
I read through (or tried to at least) most of the wiki page and was still scratching my head as to which one to select. I think I am going to go with TCP CUBIC for now, given it is the default algo on Linux kernel since 2.6. No scientific basis for this decision though. Would love to hear someone's more educated advice.
as a Kernel2.4 user i have only 3 options.
Westwood,vegas and bic.
With the default which is vegas i`m having one big problem. When playing a mp3 stream with winamp or other players, i`m getting buffer underruns after half an hour of playing.
This happened with all the older builds. I thought this was my ISP, but when i switched to westwood or bic the stuttering was gone. Switching back to vegas and the problem comes back after half an hour of playing.
I`m using bic for now with my 25/1 cable line.
Seems to work fine for me. _________________ Netgear WNR834B v2 - Eko build v24-sp2 15943M mini NEWD K2.4 (running MINIUPNPD)
Tested with BS 15943 mini build with my 32/1 line over wireless:
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Wed Nov 03, 2010 2:21 Post subject:
Skydiver wrote:
Hi,
as a Kernel2.4 user i have only 3 options.
Westwood,vegas and bic.
With the default which is vegas i`m having one big problem. When playing a mp3 stream with winamp or other players, i`m getting buffer underruns after half an hour of playing.
This happened with all the older builds. I thought this was my ISP, but when i switched to westwood or bic the stuttering was gone. Switching back to vegas and the problem comes back after half an hour of playing.
I`m using bic for now with my 25/1 cable line.
Seems to work fine for me.
Interesting information Skydiver. I may have to try the BIC congestion algorithm myself. Although many use the 'vegas' option, it would be interesting to see if another one improves the flow on my router. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Thu Nov 04, 2010 23:15 Post subject:
crashfly wrote:
..., it would be interesting to see if another one improves the flow on my router.
On this note, does any one know of a way to test these algorithms other than anecdotal evidence of "my connection appears much faster"?
I switched over to the 'bic' congestion control. In some instances the connection appears faster, but I would like some testing parameters to see if one is better than another.
Side note: Is there any chance that DD-WRT supports the cubic on v2.4 or is that just a v2.6 kernel option? _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
I 2nd this- would be great if someone knows of a guide for testing these algo's to see which is best. It seems with such a wide variety of broadband connection types, that there is no "one size fits all" or "use xxxx it's best". I am thinking that somehow iperf/jperf might be useful here, but I guess that you would need a very fast machine somewhere outside of your network to test against.
I have switched to CUBIC also. I was getting unbearable lag and connection drops on Xbox Live. My campus has 200mbps out of a gigabit link from Cogent. I'm located in a rural area so my pings are somewhat high. After doing some research, I found that CUBIC is the default selection for modern Linux kernels. After testing, I can tell you that all of my issues have disappeared. I can now play Xbox Live without issue and Netflix seems to stream better also.
My research has told me that CUBIC can dynamically adjust the TCP window size and is an improved variant of BIC. I have a WRT610N version 1 with 64mb of ram and a 300mhz processor so I'm sure that the extra calculations can be handled fine.
Hello from Romania!
I have an ASUS RT-N16 router. My ISP have PPoE connection with 100Mbps fiberlink (FTTB). Cubic is the best solution for me or should i use something else?
Thank you and a happy new year!
I would just like to add the following point. I was having problems with receiving email from my POP3 account. This started when I switched from my WRT54G router running DDWRT build 12966 to my brand new WRT610Nv2 router running DDWRT build 15508. At first I thought it was a firewall problem, because through testing I found that I could receive email from the POP server when the PC was in the DMZ of the router. Then I noticed this new setting in the configuration and began to look for more information on it. I stumbled on this thread and decided to change the setting from the default VEGAS setting to the CUBIC setting. Suddenly my problem with receiving email from the POP server was solved! Therefore this setting can be useful for some who are encountering problems like mine.
The question I now have is which of the possible settings will be the best? WESTWOOD setting would also seem to be a good choice for some. Has any one tested other settings?
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Sat Jan 29, 2011 18:19 Post subject:
oxygenx wrote:
i already said it in other threads. changing the TCP congestion control algorithm only affects TCP connection which have a endpoint on that host.
changing it on a router is completely useless (running ftp or sth else on the router might be an other story)
I just noticed, but this person is completely wrong. Congestion control affects everything that goes from the local network to the ISP/internet. Every router/gateway has a buffer of sorts. Congestion control helps to keep the 'buffer' from getting stuck. Congestion control reduces prioritization strain on some time sensitive packets. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
I wrote something similar, but deleted my post...
pfffff _________________ Asus RT16N + OTRW
Kingston 4GB USB-disk 128 MB swap + 1.4GB ext3 on /opt + 2 GB ext3 on /mnt
Copperjet 1616 modem in ZipB-config
Asterisk, pixelserv & Pound running on router
Another Asus RT16N as WDS-bridge
I just noticed, but this person is completely wrong. Congestion control affects everything that goes from the local network to the ISP/internet. Every router/gateway has a buffer of sorts. Congestion control helps to keep the 'buffer' from getting stuck. Congestion control reduces prioritization strain on some time sensitive packets.
that is completely nonsense. guys, stop writing such shit. read the docu, read the rfcs, read the linux kernel source. _________________ Router: WNDR3300 (wl0: n-Only 5Ghz, WPA2-AES, wl1: g-Only, WPA-Mixed-Mixed)
WDS Node 1: WNDR3300 (wl0: n-Only 5Ghz, WPA2-AES, WDS-connected Router, wl1: g-Only WPA-Mixed-Mixed)
WDS Node 2: WRT54GL (g-Only, WPA-Mixed-Mixed WDS-connected to Router)
Modem: Cisco EPC3202
clients: Notebook 1, D-Link 323, PS3 Slim, Kathrein UFC960 connected to WDS Node 1 via Gigabit Switch. Notebook 2, Deskjet 6980 connected to WDS Node 2