We have a corporate customer that we need to guarantee bandwidth for. Ok that is in the manual simple queuing but I am wondering if I should do something a little more advanced? Setup below.
Corporate customer application uses ports: 80, 443, and 1494 for Citrix.
Several questions I have are.
When I create a simple queue do I still need to create a mangle in winbox?
Will a single queue just doing guaranteed bandwidth for this customer be the best method for their application?
Will this queue mean that is always 1.5mb less bandwidth for everyone else or can that bandwidth be used by others when they are not using the full amount?
Does the queue I created look correct? And do I have to somehow create a mangle for it?
Queue Settings:
target: 192.168.5.150/32
destination: 0.0.0.0/0
interface: ALL
priority: 8
limit at: 65536
max limit: 1536000
Or should I be also setting up queues for them ports individually? And if so what is a good thread on how to setup queues by application ports?
Current setup is mp firewall changes made.. all bridges bridged using wds.. customer ip is set at 192.168.5.150/24 with gateway 192.168.5.1. Should the individual customers be set at /24 or will they work set at /32?
When you mangle traffic all it does is add a “Flow-mark” an identifier if you will that allows specific traffic to be identified by the router for firewalling and bandwidth shaping (queue tree). Mangling has nothing to do with simple queues. Simple queues work just as they look, you specify the target IP address and select the bandwidth you’d like to guarentee and set a priority.
If you want to provide QoS for your customer for the ports you mentioned, you can do this, however you’d need a MT at the Customer Premise. You could setup queues for this kind of traffic on your main MT router, but this will apply those queues to all traffic going in/out of your network. Usually it’s a good idea to setup queue trees for common protocols that you want to guarentee to your users, and restrict other applications that would cause network performance to degrade.
Usually HTTP is given higher priority and more bandwidth as it is a very commonly used protocol. Peer2Peer networking applications should be given lower priorities and you should limit the outgoing traffic (people downloading off users on your network) to a very low bandwidth setting (mines at 256kbps). I could write a novell on how to shape traffic, but it’s already been done, search around on google.com for bandwidth shaping and read the mikrotik manual on Queues.
Yeah been reading the manual. But the problem with the manual it’s all text command lines and not the winbox configuration so they are hard to duplicate and follow.
my little contribution is that u should note how to mark packets when being masqueraded and how to mark when not masqueraded… i think that is the only confusing thing in the manual.
if the wireless LAN is masqueraded on the access concentrator, mark the packets with connection mark and then u can now start marking individaul IPs with flow mark and move on to the queue tree for the BW allocation.
On the queue tree. have a proper design that will specify the parent (qdiscs) and the child (classid).hence u can make the child a parent for all the services u want to guarantee in the child BW.
Just make sure u read well and also be innovative.