This looks very interesting, @Hudra! I've been happily using DSCP Classify by @yelreve, but I'm comparing features to see what more QoSmate brings to the table.
What would be a compelling reason to switch to QoSmate from DSCPClassify?
FWIW, I always like to check out how things are working using Netdata + my little add-on I put together for Netdata.
Update:
@Hudra I gave QoSmate a try and hit an issue when setting up a rule for IPv6. Is this a known issue? I created a corresponding issue with the project on github.
Snippet from /etc/config/qosmate
config rule
option name 'NextDNS6'
option proto 'tcp'
list dest_ip '2001:19f0:5401:1d93:5400:2ff:fece:25e9'
list dest_ip '2605:380:57:613::5'
list dest_ip '2605:6c80:1:60::'
list dest_ip '2605:a880:0:7b:0:1:54d:2215'
list dest_ip '2a00:11c0:39:353::3'
list dest_ip '2a01:4ff:f0:ac5::1'
list dest_ip '2a07:a8c0::'
list dest_ip '2a07:a8c1::'
list dest_ip '2a0b:4342:1a32:f:5054:ff:fe48:d17f'
list dest_ip '2a0e:6902:2002:12b:5054:ff:fed7:6b78'
list dest_port '443'
option class 'cs5'
option counter '1'
option enabled '1'
Error Message
...
Automatically including '/usr/share/nftables.d/ruleset-post/dscptag.nft'
In file included from /dev/stdin:6562:1-57:
/usr/share/nftables.d/ruleset-post/dscptag.nft:121:30-67: Error: Could not resolve hostname: Name has no usable address
meta l4proto tcp ip daddr { 2001:19f0:5401:1d93:5400:2ff:fece:25e9,2605:380:57:613::5,2605:6c80:1:60::,2605:a880:0:7b:0:1:54d:2215,2a00:11c0:39:353::3,2a01:4ff:f0:ac5::1,2a07:a8c0::,2a07:a8c1::,2a0b:4342:1a32:f:5054:ff:fe48:d17f,2a0e:6902:2002:12b:5054:ff:fed7:6b78 } th dport 443 ip dscp set cs5 counter comment "NextDNS6";
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I believe ip daddr will need to be ip6 daddr for IPv6 addresses.