TCP Vegas makes QoS unnecessary?

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3 ... 12, 13, 14, 15  Next
Author Message
phuzi0n
DD-WRT Guru


Joined: 10 Oct 2006
Posts: 10141

PostPosted: Wed Jun 24, 2009 12:24    Post subject: Reply with quote
What build are you using?
_________________
Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Sponsor
Marla
DD-WRT Novice


Joined: 15 Jun 2009
Posts: 10

PostPosted: Fri Jun 26, 2009 19:38    Post subject: Reply with quote
phuzi0n wrote:
What build are you using?


I'm using the version by Brainslayer from 19.06.09 v24 SP2 build 12319M. Before that I used the version linked in the database.

Both version didn't had support for vegas...
redhawk0
DD-WRT Guru


Joined: 04 Jan 2007
Posts: 11564
Location: Wherever the wind blows- North America

PostPosted: Fri Jun 26, 2009 20:29    Post subject: Reply with quote
vegas is enabled by default...I haven't seen any issues since it was implemented by BS...I am currently running 12360 std build.

go to

/proc/sys/net/ipv4


cat tcp_westwood
0
cat tcp_vegas_alpha
3
cat tcp_vegas_beta
3
cat tcp_vegas_cong_avoid
1
cat tcp_vegas_gamma
2

This indicates that the tcp_vegas is active...and it has been working for me since BrainSlayer implemented it with the V24-Final.

redhawk

_________________
The only stupid question....is the unasked one.
Marla
DD-WRT Novice


Joined: 15 Jun 2009
Posts: 10

PostPosted: Fri Jun 26, 2009 22:03    Post subject: Reply with quote
redhawk0 wrote:
vegas is enabled by default...I haven't seen any issues since it was implemented by BS...I am currently running 12360 std build.

go to

/proc/sys/net/ipv4


cat tcp_westwood
0
cat tcp_vegas_alpha
3
cat tcp_vegas_beta
3
cat tcp_vegas_cong_avoid
1
cat tcp_vegas_gamma
2

This indicates that the tcp_vegas is active...and it has been working for me since BrainSlayer implemented it with the V24-Final.


Please read my post.

It is NOT there! Otherwise I wouldn't have asked. No westwood, no vegas, nothing in the whole proc dir!

Edit: Maybe it's just missing in the DIR-300 images?
redhawk0
DD-WRT Guru


Joined: 04 Jan 2007
Posts: 11564
Location: Wherever the wind blows- North America

PostPosted: Fri Jun 26, 2009 23:09    Post subject: Reply with quote
Marla...your unit is Atheros based...not Broadcom. I suggest you ask your question in the Atheros forum. They might be able to shed some light on this for you.

http://www.dd-wrt.com/phpBB2/viewforum.php?f=28

redhawk

_________________
The only stupid question....is the unasked one.
Marla
DD-WRT Novice


Joined: 15 Jun 2009
Posts: 10

PostPosted: Sun Jun 28, 2009 8:51    Post subject: Reply with quote
redhawk0 wrote:
Marla...your unit is Atheros based...not Broadcom. I suggest you ask your question in the Atheros forum.


Thanks for the hint redhawk, didn't know that this is chipset-based... Embarassed
docbill
DD-WRT Novice


Joined: 22 Aug 2008
Posts: 24

PostPosted: Mon Jun 07, 2010 0:04    Post subject: Reply with quote
Hmmm. Interesting. I notice if I use vegas and QOS at the same time, I get the same download speeds as just QOS. I've also noticed that with ftp set as Bulk, my download tests are always 71% of my maximum downlink speed.

However, based on what other people have been saying about QOS being able to prioritize even if it does not know my download speeds, I have set my downlink speed 40% higher than my maximum download speed without QOS. So now my download test give the same speeds with or without QOS enabled. That should give a fair comparison to find out if QOS really does anything useful when it is not throttling the total through put.

Bill
bill1228
DD-WRT Novice


Joined: 21 Jul 2010
Posts: 28
Location: SE Michigan USA

PostPosted: Fri Jul 23, 2010 0:33    Post subject: Reply with quote
Am thinking that tcp vegas has been removed from the build I am running. Running eko build 14826M dd-wrt v24-sp2big (7/18/10) on a Asus RT-N16. If I ls /proc/sys/net/ipv4 none of the tcp vegas files are there.
Thoughts?
--bill
crashfly
DD-WRT Guru


Joined: 24 Feb 2009
Posts: 2026
Location: Sol System > Earth > USA > Arkansas

PostPosted: Fri Jul 23, 2010 4:38    Post subject: Reply with quote
bill1228 wrote:
Am thinking that tcp vegas has been removed from the build I am running. Running eko build 14826M dd-wrt v24-sp2big (7/18/10) on a Asus RT-N16. If I ls /proc/sys/net/ipv4 none of the tcp vegas files are there.
Thoughts?
--bill

It is listed on the k24 Brainslayer build of 14537. Could it be a limitation of the Eko builds? (or are you running the k26 firmware?)

_________________
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.
Masterman
DD-WRT Guru


Joined: 24 Aug 2009
Posts: 2070
Location: South Florida

PostPosted: Fri Jul 23, 2010 6:37    Post subject: Reply with quote
TCP Vegas IS in the newest Eko build:

Linux version 2.6.24.111 (eko@dd-wrt) (gcc version 4.1.2) #535 Sun Jul 18 22:12:06 CEST 2010
CPU revision is: 00019740
Found a 8MB ST compatible serial flash
Determined physical RAM map:
memory: 02000000 @ 00000000 (usable)
On node 0 totalpages: 8192
Normal zone: 64 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 8128 pages, LIFO batch:0
Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order. Total pages: 8128
Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd
Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 128 (order: 7, 512 bytes)
CPU: BCM4716 rev 1 at 354 MHz
Using 177.000 MHz high precision timer.
console [ttyS0] enabled
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 27344k/32768k available (3144k kernel code, 5424k reserved, 1479k data, 144k init, 0k highmem)
Calibrating delay loop... 176.53 BogoMIPS (lpj=882688)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Generic PHY: Registered new driver
PCI: Using membase 8000000
PCI: Disabled
PCI: Fixing up bus 0
PCI: Fixing up bus 1
NET: Registered protocol family 2
Time: MIPS clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
io scheduler noop registered
io scheduler deadline registered (default)
HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
N_HDLC line discipline registered.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = Cool is a 16550A
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
MPPE/MPPC encryption/compression module registered
NET: Registered protocol family 24
PPPoL2TP kernel driver, V1.0
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
PCI: Setting latency timer of device 0000:00:02.0 to 64
bcm_robo_attach: Using external reset in gpio pin 10
bcm_robo_attach: devid read succesfully via mii: 0x3115
bcm_robo_attach: mii access to switch works
bcm_robo_attach: devid: 0x3115
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.10.56.27
PCI: Setting latency timer of device 0000:00:01.0 to 64
pflash: found no supported devices
bootloader size: 262144
sflash: Filesystem type: squashfs, size=0x5b02bc
partition size = 5975040
Creating 5 MTD partitions on "sflash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x007f0000 : "linux"
0x0018d400-0x00740000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x007f0000-0x00800000 : "nvram"
0x00740000-0x007f0000 : "ddwrt"
Broadcom Watchdog Timer: 0.07 initialized.
u32 classifier
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
ctnetlink v0.93: registering with nfnetlink.
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
ClusterIP Version 0.8 loaded successfully
TCP bic registered
TCP cubic registered
TCP westwood registered
TCP highspeed registered
TCP hybla registered
TCP htcp registered
TCP vegas registered
TCP scalable registered

NET: Registered protocol family 1
NET: Registered protocol family 17
Welcome to PF_RING 3.2.1
(C) 2004-06 L.Deri <deri@ntop.org>
NET: Registered protocol family 27
PF_RING: bucket length 128 bytes
PF_RING: ring slots 4096
PF_RING: sample rate 1 [1=no sampling]
PF_RING: capture TX No [RX only]
PF_RING: transparent mode Yes
PF_RING initialized correctly.
PF_RING: registered /proc/net/pf_ring/
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
decode 1f02
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 144k freed
br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
device br0 entered promiscuous mode
Algorithmics/MIPS FPU Emulator v1.5
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
br0: port 2(eth1) entering learning state
br0: port 1(vlan1) entering learning state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
device br0 entered promiscuous mode
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
device vlan2 entered promiscuous mode
device vlan2 left promiscuous mode
etherip: Ethernet over IPv4 tunneling driver
br0: port 2(eth1) entering disabled state
br0: port 1(vlan1) entering disabled state
device vlan1 left promiscuous mode
br0: port 1(vlan1) entering disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entering disabled state
br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
device br0 entered promiscuous mode
device vlan1 entered promiscuous mode
device eth1 entered promiscuous mode
device vlan2 entered promiscuous mode
br0: port 3(vlan2) entering learning state
br0: port 2(eth1) entering learning state
br0: port 1(vlan1) entering learning state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
device br0 entered promiscuous mode
br0: topology change detected, propagating
br0: port 3(vlan2) entering forwarding state
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
root@DD-WRT:~#

_________________
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
bill1228
DD-WRT Novice


Joined: 21 Jul 2010
Posts: 28
Location: SE Michigan USA

PostPosted: Fri Jul 23, 2010 12:46    Post subject: Reply with quote
Thanks for the quick response.
Crashfly, am using eko's latest k26 firmware. Have been wondering if perhaps Brainslayer's latest might have it. I'll brobably load it up and see. Again using the k26 build as this is a Asus RT-N16 router.
Masterman, I saw tcp vegas registered in dmesg but the files for tcp vegas are not in the /proc/sys/net/ip4.
Is there a step that needs to be done to activate besides registration? While I can fumble my way around Linux I am far from an expert.
Is it as simple as using touch to create the files and then doing the echo commands given in this thread?
Again thanks for any insite you can give.
--bill
crashfly
DD-WRT Guru


Joined: 24 Feb 2009
Posts: 2026
Location: Sol System > Earth > USA > Arkansas

PostPosted: Fri Jul 23, 2010 18:24    Post subject: Reply with quote
Assuming that the K26 version has the capability, you can put the following commands (or variations there of) into your firewall script:
Code:
echo 0 > /proc/sys/net/ipv4/tcp_westwood
echo 1 > /proc/sys/net/ipv4/tcp_vegas_cong_avoid
echo 2 > /proc/sys/net/ipv4/tcp_vegas_alpha
echo 6 > /proc/sys/net/ipv4/tcp_vegas_beta
echo 2 > /proc/sys/net/ipv4/tcp_vegas_gamma

I forget why I used the certain variables, but I am sure there was a "performance" reason related to them.

_________________
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.
bill1228
DD-WRT Novice


Joined: 21 Jul 2010
Posts: 28
Location: SE Michigan USA

PostPosted: Fri Jul 23, 2010 18:55    Post subject: Reply with quote
crashfly wrote:
Assuming that the K26 version has the capability, you can put the following commands (or variations there of) into your firewall script:
Code:
echo 0 > /proc/sys/net/ipv4/tcp_westwood
echo 1 > /proc/sys/net/ipv4/tcp_vegas_cong_avoid
echo 2 > /proc/sys/net/ipv4/tcp_vegas_alpha
echo 6 > /proc/sys/net/ipv4/tcp_vegas_beta
echo 2 > /proc/sys/net/ipv4/tcp_vegas_gamma

I forget why I used the certain variables, but I am sure there was a "performance" reason related to them.


Crashfly, as I stated in the previous message none of the tcp_vegas files exist in the /proc/sys/net/ipv4 directory. Am wondering if creating with touch and then doing the script is all that is required since tcp_vegas support appears to be registered when doing a dmesg.
crashfly
DD-WRT Guru


Joined: 24 Feb 2009
Posts: 2026
Location: Sol System > Earth > USA > Arkansas

PostPosted: Fri Jul 23, 2010 20:46    Post subject: Reply with quote
bill1228 wrote:
Crashfly, as I stated in the previous message none of the tcp_vegas files exist in the /proc/sys/net/ipv4 directory. Am wondering if creating with touch and then doing the script is all that is required since tcp_vegas support appears to be registered when doing a dmesg.

Well ... honestly, I have not considered if those "files" even exist on a normal K24 bootup. Further thinking, those files *would* exist only if because I put numbers on them when the firewall is setup. I guess it would be good to try seeing if those files exist in the first place. I will try some testing this weekend on it.

The worst you could do is to put those commands in your firewall script. Although I do not know how one would test if it was working (or at least find out if it is working).

_________________
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.
Theliel
DD-WRT User


Joined: 08 Jun 2008
Posts: 81

PostPosted: Fri Jul 23, 2010 22:24    Post subject: Reply with quote
Vegas its on by default, at least in BS builds. Im sure on eko builds too. You can check this:

Path to Modules:

ls /sys/module/ -la

drwxr-xr-x 3 root root 0 Jul 24 00:14 tcp_bic
drwxr-xr-x 3 root root 0 Jul 24 00:14 tcp_cubic
drwxr-xr-x 3 root root 0 Jul 24 00:14 tcp_htcp
drwxr-xr-x 3 root root 0 Jul 24 00:14 tcp_hybla
drwxr-xr-x 3 root root 0 Jul 24 00:14 tcp_vegas


cat /proc/sys/net/ipv4/tcp_allowed_congestion_control

vegas westwood reno


cat /proc/sys/net/ipv4/tcp_available_congestion_control

vegas westwood reno bic cubic highspeed hybla htcp scalable


cat /proc/sys/net/ipv4/tcp_congestion_control

vegas

_________________
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
Goto page Previous  1, 2, 3 ... 12, 13, 14, 15  Next Display posts from previous:    Page 13 of 15
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum