I am having a problem with the QoS rule for downloads. I have my max available bandwidth set to 6000 for my connection. Downloads are at the default of 80% which equals out to 4,800kb. However, when I run a speed test I am getting almost the whole 6000kb. Sometimes I am getting over 6000kb. Sometimes however the max download speed is right around 3500kb. It seams very inaccurate or something. Can someone tell me why this is happening? Also, I was thinking about just disabling the inbound QoS since I have enough download speed to go around about 7mb. To me the real bottleneck seams to be my upload speed of roughly 700kb. However, when I put a 0 in the Inbound Max available bandwidth I get a error the field "QoS IBW" is invalid. Anyone have any solutions or ideas?
You can effectively disable the incoming limits by putting in a very large number, 999999 or whatever. The correct way, however, would be simply to enter "None" - or no limit - for the class.
http://www.toastmanfirmware.yolasite.com http://www.4shared.com/dir/v1BuINP3/Toastman_Builds.html
Thanks Toastman. The incoming shaping is off sometimes due to QoS is not very effective on incoming data right?
Hmm.
I made a few cosmetic changes to the QOS setup page to make things a bit clearer. At the moment entering "None" in outgoing QOS means no bandwidth. But entering it into incoming setup actually means "ignore the limit" or FULL bandwidth.
Re the QOS, yes, it's by no means finished, although it functions very well.
You do have to juggle the incoming limits. The problem is that there is no proper ingress system on Tomato - there are no "priorities" and no "overall" limit. There are only class limits. It is possible for traffic to hit the limit on more than one class at the same time. Then, these classes together can exceed the maximum available incoming bandwidth and cause a bottleneck. UDP can also be a problem. We have to cut down the bandwidth on classes to preempt this. The result is that we can't use all our bandwidth - we have traded bandwidth for performance.
What it needs is for someone with the necessary skills to add IMQ device to the incoming data, implement the necessary magic, and then it would be nice to also output the data to a third, incoming pie chart etc.
I don't possess much more coding skill than the average monkey, but for someone good at this stuff it probably isn't very difficult. Once the hard work has been done, tuning the QOS ingress would be relatively easy. It's just getting the basics installed that is the problem.
If you're interested in the subject, take a look here:
http://www.linksysinfo.org/forums/showthread.php?t=64144
http://www.toastmanfirmware.yolasite.com http://www.4shared.com/dir/v1BuINP3/Toastman_Builds.html
My cousin has a Bachelor of Science in Information Technology. According to Wikipedia they do programming, networking, and all kinds of stuff. She is also a server admin. I'm pretty sure she does this stuff. I will see what I can find out.
Also my son is playing on Xbox live right now, and the traffic is going to P2P/bulk for some reason. I have the Xbox live l7 in place.
l7 filters are often pretty useless. Looks like it's not doing much.
The best way to classify XBox is probably to implement the port numbers in the rules. This is my best guess:
Ports used by XBox Live:
53 TCP/UDP
80 TCP
88 UDP
3074 (TCP/UDP)
1863 TCP/UDP (for video Kinect)
(Easy way - may be source port TCP/UDP 53/80/88/3074)
1863 is already covered by one of my rules but you could also add it in here if it helps. You may wish to remove port 80 from this rule and leave it to be covered by your normal WWW rule.
I assume XBox stuff opens ports itself by UPnP?
There are several people on here who use XBox Live, they could probably tell you more.
http://www.toastmanfirmware.yolasite.com http://www.4shared.com/dir/v1BuINP3/Toastman_Builds.html
I noticed that sometimes and I repeat sometimes when my son is actually in a multiplayer game it will work. However, last night he was in a multiplayer game and it didn't work.
I was thinking the same thing about setting up rules the rules without the l7 filter for the Xbox. I am was a little confused though. Mostly due to the fact like you said some of the ports are already covered by other rules. This is what I was thinking, and please correct me if I am wrong. Due to the fact I am not really sure if this would be the proper way to set them up.
I assume port 53 is for DNS for the Xbox so leave that alone.
Also port 80 would be covered already by the WWW rule as you mentioned.
Leave port 1863 be classified under the Messenger class.
As far as port 88 UDP and 3074 could I just setup a rule for TCP/UDP with ports 88,3074 the IP address of the Xbox? Then classify it as Game/VOIP? Should I create two separate rules one for TCP/UDP 3074 and one for 88 since one uses both TCP and UDP and the other uses just UDP? Sorry I'm new to this, but I am trying hard =)
I do have all those ports forwarded even though UPNP is enabled. I am pretty sure the Xbox will open the ports itself through UPNP. I noticed that according to Microsoft port 1863 is suppose to be for video Kinect. However I have seen this port in use while my son is not only playing mutiplayer games but watching Netflix as well. I assume that the reason why this port is in use is due to the voice chat on the Xbox to be able to function properly. Thanks for the help I and explanations I greatly appreciate it.
PS. The link you posted about the development of the incoming QoS it has the code with IMQ implemented for OpenWRT? Now its just a matter of getting a similar code that will work with Tomato?
UPnP opening ports - and speeding up connections using those ports by using QOS - are two separate issues. But we can use the "port opening" information to deduce what to include in QOS.
Take port 53 for example. If a port has to be opened to reach it, then it is port 53 on the local Xbox PC (source port). You need to address that differently to DNS which is on a remote PC (destination port).
You could just change the DNS rule to include both source and destination. However, I didn't advise that because we don't actually know what traffic port 53 would be carrying. You might end up with something you didn't want taking up all your bandwidth!
Putting the ports into it's own Xbox rule (even though some ports are duplicated) allows you to move that rule up or down in the list or delete it without affecting other rules. The first rule to be reached will be the one that is used. But you can see where the ports are being classified, so all you have to do now is to adjust them to suit what you want to achieve, what works for you.
Make a rule for each port, combine ports, use TCP and UDP both (to reduce the numbers of rules) as you feel appropriate. That's up to you.
I think you've got the idea now.
http://www.toastmanfirmware.yolasite.com http://www.4shared.com/dir/v1BuINP3/Toastman_Builds.html
Copyright © 2012
Capable Networks LLC.. All Rights Reserved.
RSS |
Privacy Policy |
Advertise With Us |
Terms of Use |
About Us |
Contact Us |
Site Map
Our Capable Community Network:
DVR playground |
Explore3DTV |
MediaSmart Home |
MotoDash |
My Open Router |
Pogoplugged |
DijitCommunity |
Robo Community |
Sansa Community |
TechLore |
TiVo Community |
TouchSmartDevZone
MyOpenRouter.com is not affiliated with NETGEAR®. NETGEAR is a registered trademark of NETGEAR, Inc. in the United States and/or other countries. Other brand names mentioned herein are for identification purposes only and may be trademarks of their respective holder(s). © 2011 NETGEAR, Inc. All rights reserved.
Did you forget your password?
You can also log in using OpenID.
Previous Thread
