Try adding another processor. IF you have one, use an Intel NIC. Not heard good things about the realtek. If you didn't specify the type it defaults to e1000 for FreeBSD VMs which is good.
Ok. Btw. it would be nice if theres a different symbol for match rules in the rules list. At the moment its the same like pass rules. In the firewall log match too (theres the block icon used afair)
EDIT: question removed, did mix up my voip/vpn problem with the traffic shaper rules (thought its necessary to direct traffic to in AND out queue)
Problem exists on 2.1.0, 2.1.1 and 2.1.2. Below is another example. We have a 90 Mbps symmetrical link.
[image: QueueNumbers1.jpg]
[image: QueueNumbers1.jpg_thumb]
I'm on the same boat.
My first advice is play with the traffic shaper wizard. Its a start!
Mine works for awhile with traffic shaper but not the way I wanted yet.
Its difficult to work with .
match in on ovpns9 inet from 172.16.20.0/24 to 192.168.0.240 label "USER_RULE: Queue VideoConferencia" queue qVoIP_ext
The rule above seems to work, since the queue is applied to the state, so the traffic coming back would fall into the right queue.