qos: source/destination ip address priority

[tatsuya46]

like how we have the ability to enter in ports for qos, having that same functionality for ip addresses instead would be helpful especially for gaming where a single ip or subnet range is connected to multiple times with different ports. would also help in managing priority for gaming only without interfering with torrents or etc, as setting all udp traffic with priority is great for games, but also gets bloated with lots of p2p/torrent traffic being prioritized with it.

something such as, like how it is for custom port ranges:

service name:

protocol:

ip &/or ip range (instead of "port range":

so entering in 159.153.26.225 or 159.153.0.0/24 with premium priority would prioritize all traffic regardless if tcp/udp/icmp, to & from that ip address or ip address range respectively, with the selected priority. or limit it to xxx kbps if the user entered it in services under interface priority.

[cookieboyeli]

Excellent idea, that helps take some of that unnecessary sorting work away from QoS by allowing you to set per device priority. A lot of traffic is broken up by device anyway, NAS/file server/torrent box, Roku, smartphone and other gadgets, all their traffic has to be looked at in addition to your gaming rig.

Being able to set priority by IP address essentially allows you to section up the work QoS has to handle into much easier chunks.

QoS could certainly use the help.