The various options you listed (except speed) let you identify the traffic that will be affected by the QoS rule. The values you should provide will depend on your specific requirements.
For example, if you wanted to affect only traffic sent by a device at IP address 10.0.0.1 from port 5000 to port 80 on the device at IP 172.16.0.2 the fields you're inquiring about would look like this:
Src IP: 10.0.0.1
Src Mask: 255.255.255.255
Dest IP: 172.16.0.2
Dest Mask: 255.255.255.255
Src Port: 5000
Dest Port: 80
Note: Most devices treat a wildcard mask of 255 as requiring the corresponding octet in the IP address to match exactly. Therefore 255.255.255.255
means the entire IP address would have to match before the rule applies but the mask 255.255.0.0
would mean the rule applies as long as the first two octets match. Check your product's documentation for its specific requirements.
To have the rule affect all traffic from your local network of 10.0.0.1/24 destined to any IP address in the world you'd use:
Src IP: 10.0.0.1
Src Mask: 255.255.255.0
Dest IP: 1.1.1.1 (this value wouldn't matter)
Dest Mask: 0.0.0.0 (this means any address will match)
Src Port: ?
Dest Port: ?
I don't know what values your device accepts in the Source & Destination Port fields when they should match all ports. Your manual or the device's online help should explain this.
More Information
sometimes the mask entry is just a single number like
24
which means/24
or255.255.255.0
see CIDR for more info – Jasen – 2018-02-27T00:25:22.140@Jasen that is possible too. It depends on the product. I'm used to Cisco equipment which set the standard for using the wildcard mask as described here. – I say Reinstate Monica – 2018-02-27T00:28:15.133