I’ve been trying to get qosify to work for the last 2 days.. without any success. It would be nice if you could provide a more detailed instruction on how to run it.
For example, I don’t actually know if I should run it with sqm enabled or if it replaces sqm and I should disable it and how to actually run it? It never made any difference for me in tagging packets or reducing bandwidth.
For testing I tried to tag 8.8.8.8 with CS7 and pinged it but no packets are tagged.
and in this picture is cod priorisiation possibility to add in qosify ? like that generaly 3074 to 30000-45000 and inverse which source or destination ...
@Dopam-IT_1987 regarding the source/destination port: you should just add the 2035 port. Port matching works like this: For egress traffic, the port is compared against the destination port, for ingress traffic against the source port.
Any udp not identified by another rule will be marked as CS4. See what happens after you fix the range syntax from udp:10000:30000 +CS5 to udp:10000-30000 CS5 (try with and without the + sign before CS5).
for add this information i download the packages "tee"
and i write on firewall.user for example
iptables -A POSTROUTING -t mangle -o br-lan ! -s 192.168.2.160 -j TEE --gateway 192myip of PC wired
iptables -A PREROUTING -t mangle -i br-lan ! -d 192.168.2.160 -j TEE --gateway 192.168.my ip of pc wired
I’m not 100% certain since I don’t use TEE or Wireshark much, but if you’re taking the traffic input on br-lan before it is sent through the wan tc filter with bpf (qosify) you won’t see the modified dscp yet.
The PREROUTING rule captures the original traffic before qosify can modify it. So I think this is just a flaw in the wireshark capture setup.
Others with more experience may correct me if I’m wrong.