Hello,
i’m breaking my head trying to figure out how to do a very very simple QoS priorization of traffic.
there are 3 selectors: HTTP, Games, P2P
i only want to priorize traffic, games priority 1, rest 8 and even more, P2P restricted to 128kbps upload
internal network is NATtes via masquerading.
i’ve done mangle rules for gaming and port 80, the rules are mark connection first, then use that mark to mark the packets. Mangle seems to work fine(albeit inverted). “juegos” is games
#
/queue type
set default kind=pfifo name=default pfifo-limit=50
set ethernet-default kind=pfifo name=ethernet-default pfifo-limit=50
set wireless-default kind=sfq name=wireless-default sfq-allot=1514 sfq-perturb=5
set synchronous-default kind=red name=synchronous-default red-avg-packet=1000 red-burst=20 red-limit=60 red-max-threshold=50 red-min-threshold=10
set hotspot-default kind=sfq name=hotspot-default sfq-allot=1514 sfq-perturb=5
set default-small kind=pfifo name=default-small pfifo-limit=10
/queue simple
add burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s comment="" direction=both disabled=no dst-address=0.0.0.0/0 interface=all limit-at=0/0 \
max-limit=0/0 name=Juegos packet-marks=juegos parent=none priority=1 queue=default-small/default-small total-queue=default-small
add burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s comment="" direction=both disabled=no dst-address=0.0.0.0/0 interface=all limit-at=\
128000/0 max-limit=128000/0 name="emule y p2p" packet-marks=emule parent=none priority=8 queue=default-small/default-small total-queue=\
default-small
add burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s comment="" direction=both disabled=no dst-address=0.0.0.0/0 interface=ciudad limit-at=0/0 \
max-limit=0/0 name=queue1 packet-marks=http parent=none priority=8 queue=default-small/default total-queue=default
/queue interface
set internet queue=ethernet-default
set ether2 queue=ethernet-default
set ether3 queue=ethernet-default
set ether4 queue=ethernet-default
set ether5 queue=ethernet-default
set ciudad queue=default
The problem is that queues ain’t working, in the queue1(the http one) it’s only showing upload traffic(~29kbps for full download) and nothing in download.
Now the questions:
this is a DSL line, 2.5mbps/256K, which queue type is more beneficial?
in simple queues there is the “queue type” and then there’s another queue type in total per each rule, how do this types relate to each other and to the interface queue?
regards,
Guillermo
Note to mikrotik: The state of the official docuemntation is sad at best, it’s totally outdated, ROS is approaching 4.0 and 3.0 documentation hasn’t been touched in months, there are lots of obscure and undocumented(or poorly documented) features
wrong about documentation point maybe,
but that was not the main point of my situation which i detailed prviously and which i haven’t resolved and it’s not working at all.
besides there’s weirdness in how it works, if i use one type of queue, it doesn’t show traffic at all, if i use small, it shows the same upload and download, if i choose to not use upload or download, the traffic gets reversed(all this while shaping nothing as the speeds don’t change and latencies keep sucking under heavy download)
*) changed behaviour of simple queues - queues with no limit and type default-small
and no children actually do not get installed, as if there was no queue;
then what’s the point of the ros accepting them, mark it as invalid instead!
even so, the problem of duplicated inbound and outbound traffic is still there with other queues.
is it so hard to do what i need to?
prioritize small ACK packets, prioritize gaming traffic, depriorize P2P and large downloads with larger queues.
i don’t wnat to do any kind of BW control, only priorization.
In order to have control one must limit the bandwidth. To have control only your packet queue must be operative on the link and to avoid packet queue on the ISP equipment and bottleneck equipment you must limit the bandwidth between 62% to 99% depending on case. What’s your internet connection?
ADSL, 2.5mb down, 256K up
i don’t want to do BW control(or 99% as you say) because i need max speed in any given task, but the ability to game with ultra-low ping(as it where running alone) when using P2P and heavy downloading+uploading at the same time.
my current “home” router can do this more or less fine(when gaming, it fragments large packets into smaller ones, and drop upload+download speed for P2P and http/ftp) and maintains good ping, this RB should be able to do it even better(but alas, it’s not currently)
What is your home router, make, model, firmware, QoS settings? If it can do it, why not put it between the ADSL line and the MikroTik router? How are you sure it keeps low ping with fragmenting packets? Is it connected to the ADSL modem or is it the ADSL modem?
it’s a D-LINK gaming router, and i’ll never put it in between, what’s the point on doing that if i’m testing mikrotik for this matter, it’s a router connected to a modem, i’m sure because i monitor in-game lag and have transfer graphs for downloads.
chupaka: what do you mean exactly?, i don’t see that property at all
Dude, some of those small little thingies (home routers) are using completely different TCP protocol (for example: TCP Vegas (A)) and I’m not sure (yet) but in RouterOS I think queue-type=RED does a similar thing. Is your gaming router with stock firmware? Can you telnet into it and issue these commands:
In this example the returned codes are 1 0 3 3 and 2, and we need to look at the return codes in your case. If the first is 1 then there’s your explanation for gaming success. And there’s something for all the MikroTik pros to think about as well, especially the development team.
my home router doesn’t have telnet, it’s closed in that aspect, most likely based in that network processor ASIC with packet shaping(can’t remember the name now).
normis: like i’ve said, i want to priorize EVERYTHING, be it incoming and outgoing for ANY source/destination address, then what, should it put “0.0.0.0/0” in traget-address or build 100 different rules for each game server, client, network and you-name-it that i want to priorize?
besides, all examples in the manual are of bandwidth limiting/control, which are not applicable in my case
etc …
Is this is right way or I need to mark connection also?
And is chain prerouting and postrouting OK , or to use also input output?
Also does is need to specify interface in mangle (if not it will be used on all interfaces right)?
OK i have simple queue … only one static for my server and dynamic which is create hotspot and pppoe server … so because queue-tree is aplyed before here is which I was done for now and it is look OK … now I will be test for few day and see is good … so far so good looks to me … tell one blind men
What do you think guys ?
Here is mangle:
target-address is probably the most important setting for queues. it means “what are you going to limit” ?