1st: QoS is meant mainly to be used on the slow WAN link. For use on the LAN / WLAN interfaces, the CPU
might be too slow (at least, it might cost so much thoughput that running without QoS could be the better option)
2nd: I didn't specify the Up / Download speeds on the
LAN and WLAN interfaces. While on the LAN one could
easily find the numbers (as it is 10/100/1000 mbps
Ethernet, on the WLAN the actual speed will always vary if you move your Laptop around). It seems like some of the internal queuing parameters are calculated as percentages from the up / down speeds.
That makes a valid QoS config on the WLAN side almost impossible.
3rd: i am not 100% sure, but doesn't 802.11N's WMM provide some sort of QoS / optimization for real-time traffic on the WLAN already?
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Mon Jan 31, 2011 23:19 Post subject:
Just found this out... certain channels when on HT40 force N clients DOWN to 65Mbps..... with stock firmware ALL channels on HT40 give the proper N speeds.. this is for theoretical and actual.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
DD-WRT QoS is also a mess, anyday now its going to just stop working altogether. Over the last year I seen 1 QoS commit to trac, and after it it got worse. The more noise is made with this ticket the better chance we have... QoS affects EVERY router with EVERY build type.
@schnullimaus Yes you only have to set QOS for the Wan port not the your Lan traffic. For WMM see Don't Mess With WMM! _________________ Upgraded to
DD-WRT v24-sp2 (03/25/13) std -
build 21061
just chiming in with my QoS problems. When I turn it on it floods my connections and pretty much locks up the router. goes from 150 connections to 600+ and stops traffic.
DO NOT INSTALL THIS if you expect it to just work perfectly. It is still a Beta and so will have problems and might brick your router. You have been warned.
CURRENTLY WIRELESS DOES WORK, THOUGH SOME REPORT NOT AS STRONG SIGNAL STRENGTH AS STOCK F/W, If you mess with the wireless strength or other settings you can destroy the wireless config information and render wireless dead until a fix is discovered. the fix may be very complicated and require special cables. The fix has still not been found for this problem.
- (No reports of this lately but be careful) raising wireless strength in the config is also reported that it will cause the wireless to fail and set all MAC addresses to FF:FF:FF:FF:FF:FF. BE careful when changing it and be aware that it can cause some issues.
- example: http://www.dd-wrt.com/phpBB2/viewtopic.php?p=431255#431255
- The regulatory domain has to be in the US to get the transmit power up to 26 (though reported at 23)
- OpenWrt has a Dump of caldata and it shows that is where the mac addresses for the interfaces are along with the other data needed for the interfaces https://forum.openwrt.org/viewtopic.php?id=22311&p=3
*Thanks wired57*
-Possible use to re-add the MAC addresses to the wireless and other loss of configs.
I am only collecting what i see other people report, I cannot test anything on my router as it is critical and cannot be down. I dont know everything about this stuff, I am just trying to centralize where the info is kept so we can share the issues and problems we are running into with the developers in a format they can easily use.
If there are errors or you want to add something to the list please PM me with info and i shall.
hey :) just wondering if i can get a current status on this stuff - has the current build fixed these problems? or can someone link me to release notes for the latest build?
cheers
I moved to open-wrt to run my wireless connections. It handles the HD video streams I send over it with higher rates and fewers lock-ups than either dd-wrt or the stock FW.
I moved to open-wrt to run my wireless connections. It handles the HD video streams I send over it with higher rates and fewers lock-ups than either dd-wrt or the stock FW.
on an old PC I had lying around. It takes some tinkering to get set up properly, but holy cow is it full featured.
Kent
And now you have a like what, 40watt pc running al day instead of a 6.5watt router appliance? Might be full-featured, but here in NL that costs a fortune to run all day 24/7
I moved to open-wrt to run my wireless connections. It handles the HD video streams I send over it with higher rates and fewers lock-ups than either dd-wrt or the stock FW.
And now you have a like what, 40watt pc running al day instead of a 6.5watt router appliance? Might be full-featured, but here in NL that costs a fortune to run all day 24/7
It doesn't have to run on a power hungry machine. The SOHO hardware they sell consumes 18 W max and 13 W nominal and handles 35 MB/sec doing full UTM packet scans and 200 MB/Sec running just its firewall. There are many posts on their forum about building low power fan-less systems.
I have recently moved to a 40 MBit/s down and 20 MBit/s up internet connection and I did not want to be hardware limited. Not to mention the fact that my kids are getting to the age where I need a good set of tools to protect them and my systems. I like that this software is hardware/power scalable to match your needs. Right now I am using an old power hungry P4 PC to run it, but I will probably at some point move to a cheap dual core low power Atom based system
Quote:
Openwrt on a PC ?
Essentially yes, but it has more features and is more polished than OpenWRT. It is a package that companies pay ~1K a year to use, so it has considerable dev resources to accomplish this.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sat Feb 05, 2011 20:55 Post subject:
I have received r16157 from the support department. Wireless seems fine, too early to comment on my P2P over wireless issue yet. This build includes all of those Atheros commits we saw in the timeline. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
I have received r16157 from the support department. Wireless seems fine, too early to comment on my P2P over wireless issue yet. This build includes all of those Atheros commits we saw in the timeline.
Sweet Uploading it right now, I'll do some testing tomorrow. Thanks for sharing!
