In most cases, floating rules we create for traffic shaping will attempt to match traffic based on protocol and/or port. There are, however, other possibilities for matching traffic:

• Source OS: If the rule takes effect on TCP packets, you can also try to match the OS of the packets. Several variants of Windows, Linux, and macOS are supported, along with a few less common options, such as BeOS, Dragonfly, and PalmOS, among others.
• TCP Flags: You can match packets based on which TCP flags are either set or cleared.
• VLAN Prio: If the packets originate on a VLAN, you can match the packets based on the VLAN priority setting.

As mentioned in Chapter 3, Firewall and NAT, you can use the scheduler to ensure that the rule only takes effect during certain hours. As a result, you can apply traffic shaping during specific times.