In our office, everything runs on HTTPS. We have softphones and web-based clients which are high priority. We also have Google search, maps and other low priority websites that should work on best-effort basis.

But there is no way to differentiate between this traffic. We can't do it based on IP because most of the hosts have dynamic IPs.

How do you deal with this?

  • You can differentiate by destination address. IP phones talk to a PBX; other traffic goes to the Internet. Or you can use ports. You can filter on that.
    – Ron Trunk
    Oct 23 '19 at 0:20
  • I have got IP phones covered but the web-based clients don't have static IPs.
    – user36337
    Oct 23 '19 at 0:22
  • 2
    You use ACLs to differentiate the traffic. You do not need to know the source IP addresses, so it doesn't matter that the sources do not have static addresses. You want to mark as close to the source as possible, probably on the access switches, so that you can treat the traffic during its entire life inside your network..
    – Ron Maupin
    Oct 23 '19 at 2:12
  • There's no way to differentiate as I said. Traffic goes to dynamic IPs and all of them have the same port.
    – user36337
    Oct 23 '19 at 15:46
  • You could segment out the high priority clients into their own VLAN. Then you could apply the proper QoS policy to entire IP range and still use dynamic addressing. However, is it really needed? QoS does nothing unless there is congestion. If you have a bandwidth problem, I'd solve that before I'd attempt to micro manage traffic like that.
    – Jeremy
    Oct 25 '19 at 14:27