How is traffic matched for voip?
-
Hi everyone. I'm playing around with the traffic shaper in version 2.3.1 in trying to prioritize my voip traffic at home. I've gone through the wizard using HSFC but I'm curious about how the traffic is matched. When I look at the floating rule for voip, it has parameters like match any source/destination but I don't see anything else selected. However, when I view the queues and make a call, there's definitely traffic that starts showing up on the voip queue.
Am I missing something?
LoboTiger
-
Check the port range. The floating rule can either target the IP address of the SIP server (this is how I do it), or it can capture all traffic on standard VoIP ports like 5060, 5061. Post your floating rule for voip and someone can take a look.
-
Here's my voip floating rule.
-
OK, it's doing it by protocol. Basically, it's shunting all UDP traffic to your VoIP queue, whether it's actual VoIP traffic or not. This is a sloppy way to do it as you may have other UDP traffic that gets placed into the VoIP queue with possible consequences. Better to find out your actual SIP server address and then modify your rules to use the SIP server as source and destination along with UDP protocol to ensure only VoIP traffic goes into qVoIP.
Here is how I do it:
-
Yeah this is basically what the wizard spit out but I was curious as to why it wasn't matching anything other than ipv4 UDP. I use a Cisco PAP2T adapter on my LAN which talks to the SIP provider on the internet. I should be able to match its LAN IP and prioritize everything on it for outbound traffic.
BTW, should all of the rules be setup so that they reference both ipv4 and ipv6 if I have the latter enabled?
Thank you!
LoboTiger
-
I noticed an interesting thing. I tried matching traffic with a source IP of 192.168.0.2 and nothing would match it when I made phone calls. The shaping is only being done on the upload (WAN) side so I'm wondering if NAT has already occurred and therefore it can't see the private IP address any more? I tried selecting the LAN interface for the interface but again, no go.
I ended up matching UDP traffic with EF DSCP and that seemed to do it but I'm still wondering if there's any way to match private IP addresses?
Another thing I noticed is that the traffic shaper if very finicky. There were times where I would wipe it away and redo the wizard with generic settings but it would not work until I reloaded the firewall.
LoboTiger
-
What do you mean by "reloaded the firewall"? You do need to apply/reload the firewall rules when you make updates to the firewall.
-
Yes I know I have to apply/reload the firewall rules. I actually had to reboot the entire box in order to get things working properly again. Not sure if it's a bug or something.
LoboTiger
