Yup, capped it around 13M instead of 15M. Getting around 1.4-1.5MB/s instead of 1.5-1.6MB/s. Its worth trading up some speed for this kind of manageability though. Thanks again for all your help! :) hi ganniii would you mind to share your queue tree :) thanks Hey there, its mostly similar to what F...
Yup, capped it around 13M instead of 15M. Getting around 1.4-1.5MB/s instead of 1.5-1.6MB/s. Its worth trading up some speed for this kind of manageability though.
The Queued bytes/packets are just how many packets/bytes are currently in memory waiting to be sent out of the queue. If they are empty that means it has had no reason to hold that information in memory waiting to be sent. Keep in mind that the router board can only queue and control traffic that i...
I'm going through some testing again and I noticed that the queued bytes fields are always empty. Could my problem be caused by this? And how do I get bytes to be queued for management?
You are missing the "Global Traffic In" and "Global Traffic Out" queue's in there so I can't see what they are attached to. Stupid me I missed to fill in the packet marks in the Out rules, they're being logged now. Here's the code: /queue tree add burst-limit=0 burst-threshold=0...
Ok, maybe your torrent is fully taking up your upload and causing problems there so your HTTP cannot send back that it got the packet and is ready for the next. Set a similar queue tree for your out interface and see how that goes. I think you mentioned that it was a 1 meg upload correct? So set 1M...
Ok, that all sounds right, so lets go back to some very basics. 1.) Where are you downloading the files from? Are they on your local network, or are they out on the internet? 2.) If they are out on the internet, are you able to get full HTTP download speeds without the torrent running? 3.) Do you s...
In your mangle rules, change the chain from prerouting to forward. For your test, I would open up a torch session on Ether2 and see if you are really getting the file via HTTP or some other method then. Be sure you check protocol and port and let it run. Set up torch on ether2, tried the http downl...
Well it looks right to me, so I'm not sure why it's not working for you. I would be curios to try a few things. 1.) See what happens when you move the mangle rules to the forward chain 2.) See what happens when you put it on the Global-out interface 3.) See what happens when you turn off the switch...
Post the results of the following commands. We should be able to spot what is going on. /ip firewall mangle export /queue export add action=mark-connection chain=prerouting comment="Mark HTTP" disabled=no dst-port=80,443 new-connection-mark=http_conn passthrough=yes protocol=tcp add actio...
This is just a home setup, sorry if I didn't mention that earlier. Basically I have the DSL modem connected to ether1 and 4 clients including a wireless AP to ports ether2-5. How should I go about setting the port pointing to the client? Should I choose ether2 since its the master port for ether3-5...
This is just a home setup, sorry if I didn't mention that earlier. Basically I have the DSL modem connected to ether1 and 4 clients including a wireless AP to ports ether2-5. How should I go about setting the port pointing to the client? Should I choose ether2 since its the master port for ether3-5?
Just an update, sorry for the influx of posts! Basically marking is working and traffic flow in the queue tree is showing up correctly. http://img209.imageshack.us/img209/5927/18443192.png Now when I have other traffic it can max out, but when theres HTTP traffic, other traffic should get lowered to...
It looks like you placed that on Ether1, is that the WAN or the LAN? By placing it on the WAN you are limiting the upload, place the rules on the LAN to limit the download. You could also make the parent Global-Download instead of the LAN, just by specifying the parent interface you are better able...
You are going to want to use Queue trees and not simple queues for what you want to do. Simple Queues are very simple, and basically just process their queue just like the firewall, each packet that comes in just goes down the list until it finds a queue that fits. This is probably more what you ar...
It looks like you're trying to do the prioritizing within PCQ queues. That will not work. You can only GLOBALLY prioritize one protocol over another, and then later strictly rate limit the user. If you have the situation that overall your router has plenty of bandwidth available but one user is tor...
It looks like you're trying to do the prioritizing within PCQ queues. That will not work. You can only GLOBALLY prioritize one protocol over another, and then later strictly rate limit the user. If you have the situation that overall your router has plenty of bandwidth available but one user is tor...