Hi,
I have several VLAN echa with dhcp, diferen ip pools for difent group of bandwidh, use private ip scheme and nat
the porblem is
traficc shaping is woking in the upload of mi cliente but not in the download so the cliente with 512 Kb Tx and 1024 kb ir reciving like 4 Mb or even 5 mb using a external bandwith tester like speedtest.net
I tired to copy the queue and change que que type to pcq but still not working, i’m not using queue tree but I’m planiang to in my next dising.
any idea what can cause that the simple queue is not working in the donwload/
routerboard 1000 runing os 4.13
Feklar
December 13, 2010, 2:56pm
2
We would have to see your mangle and queue rules to see what is going on there honestly. If you are just using Simple Queues, the order of the queues is very important, they are processed just like the firewall rules, as soon as a packet finds one that it fits, it fires and nothing else is processed.
I have only One moth working with Mikrotik, and this is how I found the configuration,
I know the configuration is very wrong, I’m working on a new one just waiting for the other miktrotik to arrive.
I would like to use queue tree instead simple, the problem is that we use DHCP and different ip pools
Regrds,
Feklar
December 13, 2010, 5:35pm
4
When I say we need to see the rules, I mean an /export of the relevant parts of your configuration. Winbox screen shots really don’t have enough detail to tell us much of anything. But here we go based off of what I have seen. Review this document and see if helps any.http://wiki.mikrotik.com/wiki/Packet_Flow#Diagram
1.) If at all possible move away from using the Global-x for your parents. They work, but I find them confusing, and I feel like you loose some of the finer control, if you place the queues on the interfaces themselves you are able to control what each interface is capable of instead of just globally. Global total restricts the total upload and download you allow as well. You also need to keep in mind, that the router cannot limit what it is receiving on an interface, it can only control what it sends out of the interface. So your UPLOAD queue(s) goes on the WAN(s) and your DOWNLOAD queue(s) go on the LAN(s).
HERE ARE ALL THE SIMPLE QUEUE
th3 one with pcq are test
So what is the best practice to do the traffic shaping mark packet or connection, also I need to implement QoS on the P2P traffic with best effort and all the VoIP with priority 1 or CBR.
Regards
Queue applied to physical interface question
I have 10 vlan on my LAN interface, will the traffic be shaped on the vlans?
other question the simple queue depend of the queue tree? because all my queue are simple and still not working.. are the simple queue working globaly in - out?
Feklar
December 13, 2010, 8:33pm
7
Marking by connection makes things easier on you since it is bi-directional, and I think it may take up fewer resources when done right. It all depends on your setup however, since you can only have one connection mark per packet, if you are using connection marks for other services you either need to modify that setup to take that into account or only use packet marks directly.
p2p is going to be tricky for you to do if you want to specifically classify that. The p2p identifier in MikroTik is out of date and does not pick up nearly all that is out there, and using layer7 is very resource heavy and will be difficult to get the regex you need to match what is out there. It is also impossible to really catch everything that way since it is very easy to change the client around. The best thing to do is to classify everything that you want/like and then assume everything else is something you don’t want and limit it accordingly. VoIP is going to be easier for you to classify since most implementations use the standard src-ports of 5060 and 5061 for SIP, however there are other services out there that don’t use the standards, such as Skype, that will throw a wrench into the works for doing QoS on them all of the time. If they are IP phones instead of clients, it becomes even easier as you will be able to assign them static IP addresses and mark their packets based off of that.
As to why you’re only able to limit people that are uploading traffic and not their downloads, I’m almost completely certain it is because of the reason I listed above, you are only marking packets with a dst-port of whatever, and therefore are only getting a part of the connection. If you swap over to connection marks and then mark packets based off of those, or make a mirror of your current packet marks on the forward chain to take into account the return part of the connection, you will start seeing the result that you want.
Feklar
December 13, 2010, 8:39pm
8
Simple queues happen just after global-x. So by having queue’s on global-x you override your simple queues if I remember correctly. Otherwise the two of them are separate for the most part. On my setups, I let the simple queues handle rate limiting on a per-user basis when they sign into a hotspot and let queue trees take care of the priority.
As to the VLANs, it all depends on what your goals are for the VLANs. If you want to limit what each VLAN is allowed to do for the traffic it sends out differnetly, then set up a tree for each VLAN. If however you don’t care about that and want to set up a global limit that applies to the physical interface and don’t care what each VLAN does within those limits, place one queue tree on the interface that all the VLANs are a part of.
GLOBAL IN - GLOBAL - OUT
as far I learn in the advance training
Global - IN is were you put all your Internet provider
Global - OUT is were you put all your Clients for example if I have several Vlans which is my case I have about 22 vlan from different sites and i need to do traffic shaping in need to put the in global IN
any comments?
Feklar
December 13, 2010, 9:28pm
10
Let’s make sure you understand what I am saying for parents/locations of queues.
1.) There MikroTik has no control and can do nothing about the traffic it receives on any interface. It can only control how it processes that data and what it sends out.
I don’t know what interface(s) you have your VLANs set up on. If they all reside on the same physical interface, you can place a queue tree on that ethernet interface, and each VLAN will do whatever it will do within the restrictions of that ethernet interface (much like having it on a global-x but having the control closer to the interface itself). If you want to control each VLAN differently, then place a tree on each VLAN. If you like to use the globals then more power to you. Everything in the MikroTik is queued behind the scenes, i.e. traffic is going to leave by ether2 and gets queued there waiting to leave, leaves that queue and hits VLAN20 queue, then leaves the router. By setting up simple queues or queue trees you are just placing artificial limits on these packets and reordering them to suite your needs.
Here are the vlans
/interface vlan
I don’t really understand very well how the traffic shaping work on this router, is allot complicated and no clear explanation on the wiki support.
Feklar
December 14, 2010, 3:03pm
12
QoS is definitely one of those things that is very very hard to get your head wrapped around. I basically used this as my starting point:http://wiki.mikrotik.com/wiki/Manual:Connection_Rate
Answer this question for your current configuration and we can move on from there.
Once we get your basic config working, we can start to work on the more advanced one with queue trees. Answer this and it will tell you how complicated your queue tree and mangle rules need to be.
