Joined: 21 Jul 2010 Posts: 28 Location: SE Michigan USA
Posted: Fri Jul 23, 2010 23:14 Post subject:
Theliel, thanks for the info. I installed this eve BS build DD-WRT-v24-sp2(07/16/10)mega 14815 on my Asus RT-N16. Went without problems I might add.
I did the checks you describe in your response and everything checks out as you said. So I guess I can assume that tcp_vegas is in fact running. Got confused by the other posts that had you doing echo commands to files that were in the /proc/sys/net/ipv4 directory, which are not there. Made me think that tcp_vegas was not installed or at least not active.
Just did a ps trying to see what daemon might be associated with this. I see one called ttraff which I assume it the one handling QOS??
Again thanks for the info. It looks like I have what I was looking for in this build. Probably in the eko build I had on just before this which was eko's latest.
Thanks again.
--bill
Joined: 21 Jul 2010 Posts: 28 Location: SE Michigan USA
Posted: Sat Jul 24, 2010 1:31 Post subject:
just a FYI. I have gone back to the eko build I was running and it shows, using the commands that Theliel provided, that tcp_vegas is enabled.
The build I am currently running after the BS build above is eko DD-WRT v24-sp2(07/18/10) 14826M-newd-2 k2.6 Eko.
I was using tomato latest teddy_bear build, but was having some wireless issues. Had used DD-WRT several years ago on a WRT54GL so figured I would give it a try again. Like most things so far. Only area that could use some work is on Tomato a USB drive will get auto mounted where as with DD-WRT needs a little help. So far DD-WRT has been rock solid.
Had some issues with DD-WRT on the WRT54GL but as I said that was several years ago and sp1 days as I recall.
So I am a happy camper. Which means if something doesn't come up in the next few days I will be clicking on the donate link. Well deserved for the work that has gone into this firmware!
Again thanks Theliel!!
--bill
Well, thank you for the info. However, I am not able to get *any* information out of the commands you have provided, Theliel. The "/sys/module" directory does not exist for me. And I have a different set of files in "/proc/sys/net/ipv4":
Joined: 21 Jul 2010 Posts: 28 Location: SE Michigan USA
Posted: Sat Jul 24, 2010 18:50 Post subject:
Crashfly, it looks to me like the build you are running has the "other" tcp_vegas install. The files you list are the ones that folks use the echo command to modify. Look at previous entries in this thread if you have not seen them already.
In my case the commands Theliel gave provided the results that was given. Therefore, I assume that tcp_vegas is running for me. Have not had any slowdowns so am guessing things are working.
--bill
Well, its very possible that some builds are different from other, specially k2.4 vs k2.6
On k2.6, configuration of algo congestion control are all in /sys/module, on k2.4 seems hold in /proc/sys/net/ipv4/
On k2.6, im sure vegas its used by default, if want check if vegas its used in your router, check tcp_vegas_cong_avoid first:
cat /proc/sys/net/ipv4/tcp_vegas_cong_avoid
If tcp_vegas_cong_avoid -> 1, then Vegas its in use
if tcp_vegas_cong_avoid -> 0, then vegas its disabled _________________ My Blog
wrt54GL 1.1 -> Resurrected eko 14471/MMC Mod
E2000 (wrt320n converted) 1.0 -> BS 15962M -> Resurrected WAN<Serial> BS r23919
RT-AC56U -> Merlin 374.42_2
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Sat Jul 24, 2010 19:39 Post subject:
Well, I appear to have not read the whole topic. Thank you both for informing me of my lack of knowledge.
Yes Theliel, I do appear to be running the 'vegas' routine. Works well I might add. Thanks again. _________________ 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.
This has been quite helpful. Still reading up on the thread. My main priority is for streaming video like youtube and hulu to provide a steady stream while being able to throttle bittorent traffic to do so. With Vegas alone, my results were pretty good. youtube would still do some buffering, but pretty smooth for the most part.
I thought maybe QoS could help balance things out better. First I decided to try QoS with 80% uplink and downlink. This seemed to work even better but my torrents dropped from 400-500kB/s average(max is usually about 515kB/s) to about 40-50kB/s average, atleast on a test with a 720p video. That was a little to much throttle for me. Yes I realize 720p is going to need more bandwidth then a 480p or below, but still a bit to much throttle. So my next step was to adjust the priorities for services a bit. Not sure which service youtube falls under so I have flash,http-video,rtsp,and rsp set to premium, torrents set to bulk. I thought if i dropped premium to express I could squeeze more out of my torrents while still getting a steady stream with a 720p video. For some reason it was doing a horrible job after switching to express. Youtube just buffered like crazy even on 480p videos.
On to the next test. So I decided to drop the uplink and downlink values to 0 in QoS as some others have mentioned here,and put the protocols above back to premium. My torrents were getting about about 300kB/s while streaming a 480p video and i think it was flawless unless I start ftping something to my NAS.
Moving on, keeping all the settings the same as above, I am now moving on to testing with a 720p video. So far this seems to be the only thing holding me back. 720 streams for about 45 seconds or so at a time, buffers very briefly and then resumes playing. The strange thing is the progress bar for youtube is showing that I have about [urlhttp://img440.imageshack.us/img440/4760/48499836.jpg]this much[/url] of the video cached already but yet it still stops and buffers even though it has already cached that much ahead of where I currently am in the video.
Does any one have any suggestions on what I could do to in regards to getting 720p youtube video to stream more smoothing?
I did this on my dd-wrt v24 RC3 enabled Linksys WRT54GL router. I believe that dd-wrt has always supported multiple tcp congestion control algorithms. This is a module in the linux kernel. By default, dd-wrt uses tcp_westwood while openwrt uses bic.
what a none-sense.
Changing the Congestion Control algorithm only applies to TCP endpoints on that machine (ergo you have to change it on your computer) _________________ 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
I noticed that in the latest K26 builds (15508 and later) the TCP Congestion Control Vegas is enabled by default and can be changed from Web GUI at Administration page. Well done! Thanks devs!
I noticed that in the latest K26 builds (15508 and later) the TCP Congestion Control Vegas is enabled by default and can be changed from Web GUI at Administration page. Well done! Thanks devs!
kudos to the person who brought this up and wasted so much developers time. _________________ 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
what a none-sense.
Changing the Congestion Control algorithm only applies to TCP endpoints on that machine (ergo you have to change it on your computer)
Yeah, sure!
Have you considered what happens on a gateway, like our wifi routers?
You connection gets split into 2 legs.
The first leg goes from your PC to the router. Then a second connection is build by the router to your destination on the internet.
Now we have 2 independant connections, on which the router can apply the selected congestion algorithm!
Have you considered what happens on a gateway, like our wifi routers?
You connection gets split into 2 legs.
The first leg goes from your PC to the router. Then a second connection is build by the router to your destination on the internet.
Now we have 2 independant connections, on which the router can apply the selected congestion algorithm!
no, thats just wrong, too. dont invent things. _________________ 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
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Mon Nov 15, 2010 23:11 Post subject:
adri wrote:
Yeah, sure!
Have you considered what happens on a gateway, like our wifi routers?
You connection gets split into 2 legs.
The first leg goes from your PC to the router. Then a second connection is build by the router to your destination on the internet.
Now we have 2 independant connections, on which the router can apply the selected congestion algorithm!
Adri.
oxygenx is correct. The two connections are not independent. They both depend on the router and it's kernel to make the connections. So your premise is flawed adri. _________________ 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.
Sorry for necro, I just couldn't believed my eyes.
The amount of ignorance around this topic is just... startling. Only one guy had some factual knowledge, but his words drowned in people's ignorance.
This lurking "Gurus" don't even know the basics of computer network operation (eg. OSI model). That a router operates on a Layer 3 (network layer: IP), and that it by default has no business on a Layer 4 (transport layer: TCP). Router does not create or intervene in any TCP connections that goes though when it does its routing duty, just because it's out of its scope by design.
Just installing a different TCP congestion algo on a router TCP protocol can't influence TCP connections passing though that router. Only when the router itself is an end-point of a TCP connection, for example when you access a service on it (telnet, web interface, etc), only on that link its TCP congestion algo will be used.