Wichita's largest indoor sports and adventure facility. Trampolines, basketball, volleyball, parties and events all under one roof.
let's look at these two iptables rules which are often used to allow outgoing DNS: iptables -A OUTPUT -p udp --sport 1024:65535 --dport 53 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A
First give a -p option like -p tcp or -p udp. Examples: iptables -A INPUT -p tcp --dport 22 -m state --state NEW -j DROP iptables -A INPUT -p udp --dport 53 --sport 1024:65535 -j ACCEPT You could also try -p all but I've never done that and don't find too much support for it in the examples.
with "u32 match ip sport 80" in Linux tc I can match port 80, but how can I match a port range 10000 - 20000 ?
At first glance you're only allowing DNS responses to be received and don't create any DNS related rules in the OUTPUT chain to actually allow sending DNS queries out. You current rules: #DNS resolution input and output iptables -A INPUT -p udp --dport 53 -d 8.8.8.8,8.8.4.4 -j ACCEPT ^^^^^ iptables -A INPUT -p udp --sport 53 -s 8.8.8.8,8.8.4.4 -j ACCEPT ^^^^^ Additionally, DNS can also use TCP ...
I'm unable to comment due to too-low reputation, but I came across this post when trying to accomplish a similar goal. It's not entirely clear if the OP would prefer to keep local traffic local (i.e. accessing a network printer) or if the setup actually wishes to send ALL traffic to Wireguard. If trying to achieve the former, see How do I route all public traffic through Wireguard but not ...