We're finding more and more people want VoIP, and on the bonded DSL connections, this is workable since we have 2Mb/s upload (for the US, this is a decent speed for a soho office or the like). It is slow enough that phones and things like Dropbox compete for that limited upload and the phones then tend to suffer.
We give the phones static DHCP assignments at one end of the LAN block and everything else gets IPs out of a pool at the beginning of the block. This, I hope, simplifies things - rather than trying to match SIP and RTP ports and always-changing RTP endpoint IPs, I can just match on a subnet.
All I want to do is give the phones priority. After reading up on "simple queues", I tried this:
It's after hours, so I don't know if it's working since no one is in that office. But am I on the right track?
Code: Select all
0 name="deprio-other" target=192.168.1.0/25 parent=none packet-marks="" priority=4/8 queue=default-small/default-small limit-at=1500k/0 max-limit=1500k/0 burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s 1 name="prio-voip" target=192.168.1.192/26 parent=none packet-marks="" priority=1/1 queue=default-small/default-small limit-at=1600k/0 max-limit=1600k/0 burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s
192.168.1.0/25 is everything that's not a phone.
192.168.1.192/26 has only phones.
Available upload is about 1.9Mb/s. I don't necessarily want to limit as I want to prioritize. Should this work?
Also on the RB750, if I want to apply an interface-based rule, what interface encompasses the entire switch? Is it ether2-master or do I enable the firewall on the bridge interface and refer to that in any interface-based QoS rules (and where does one find that sort of model-specific info)?