Joined: 25 Feb 2012
Joined: 03 Jan 2010
Location: Winnipeg, Canada
|Posted: Tue Mar 27, 2012 5:13 Post subject:
|8000 Kbps is 7.81 Mbps for up/down, are you use thats near what you ACTUALLY get from the ISP? With a 10/10 synchronous line usually they are fiber lines with optimal quality, at least ISPs here are..
I see several issues with your setup.. first you didn't say your build, if its not up to date as of this build, update to it. Several QoS fixes put it in a useable state finally, many CPU/RAM usage optimizations so a weak unit such as yours will enjoy that too.
Following is for after you update..
Next is your packet scheduler, HFSC is what you want for the mix of usage with your line. HFSC significantly helps regulate latency ALONG WITH the raw throughput.
Next is rtp and rtsp protocols, they should be on express. The mobile version of YouTube uses rtp/rtsp protocol and so does many other video streaming sites and software, keep them on par with httpvideo priority.
Next, sip, put to premium but not exempt, sip is not a bandwidth intensive protocol but needs good latency. Premium will give sip max priority while still taken into consideration of the max ingress/egress limits above if others are using the line.
Protocols gnutella, ftp, shoutcast may want to be added and set to bulk, skype and skypetoskype may also want to be added and set to premium.
Alternatively, as I believe your netmask priority is by priority as well and not per user speed control, is to remove ALL services and just enter the IPs using your bandwidth as bulk/standard accordingly, and your VOIP phone IP to premium, that will take ALL traffic from the phone as premium and ALL traffic from others as bulk or whatever you set them to. IF YOU TRY NETMASK YOU MUST REMOVE ALL SERVICES AS SERVICES OVERRIDE NETMASK, THEY DON'T WORK TOGETHER.
Timeouts, your TCP timeout is way too low, several sites and wikis are wrong hawking at users saying "300 seconds for 16mb RAM units 300 seconds or i kill your famery!!11", at least 900 for TCP, and UDP can go down to 90, but NO lower than 60. Max connections to 2048 and especially with the latest builds, really should handle that fine. Disable any non used features such as USB if it even has one, make sure filter multicast is checked in security settings.
[QUALCOMM ATHEROS] D-Link DIR-825 B1 -----------> DD-WRT v24-sp2 (12/15/14) std - build 25648
[QUALCOMM ATHEROS] TP-LINK TL-WDR4900 v1.3 --> DD-WRT v24-sp2 (12/13/14) std - build 25639 (private test) *BRICKED*
[QUALCOMM ATHEROS] NETGEAR WNDR3700 v1 -----> DD-WRT v24-sp2 (12/17/14) std - build 25657 (private test)
[QUALCOMM ATHEROS] NETGEAR WNDR4300 v1 -----> DD-WRT v24-sp2 (12/17/14) std - build 25657 (private test)
LATEST FIRMWARE(S) --> ftp://ftp.dd-wrt.com/betas/
Qualcomm Atheros Wi-Fi Settings --> http://dd-wrt.com/wiki/index.php/QCA_wireless_settings
Qualcomm Atheros Client/Repeater Bridge --> http://dd-wrt.com/wiki/index.php/Repeater_Bridge#Qualcomm_Atheros
|BrainSlayer wrote: |
|we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers |
Joined: 15 Jul 2010
|Posted: Wed May 30, 2012 21:14 Post subject:
|For what its worth,
I have had reasonable luck by subnetting my phones to a specific IP range and giving priority to those IPs, either on the same subnet for a few handsets or a complete /24 for larger deployments (30-50)
Works great on a 10Mbit Ethernet on Copper service.
My hardware is an E3000 and firmware is v15962
Hope this helps