This software blocks and filters, effectively 'Pi-Holing' all the adds and various malware/trackers from all requests coming from my local clients. The only thing that is unusual out of this setup is my use of an Adware/Tracker blocker called Pi-Hole which I run on a Raspberry Pi Zero and forward ALL my LAN clients to it as the primary DNS. It may be an issue with my DD-WRT firmware which I am going to try and update this weekend but it is a Kong build which seems much more 'feature rich' and working than standard DD-WRT builds at times. Iptables -t nat -I PREROUTING -i tun1 -p udp -match multiport -dports xxxxx -j DNAT -to-destination 192.168.1.100Īt all costs, I cannot get any torrent app, nor the AirVPN check to work since starting. Iptables -t nat -I PREROUTING -i tun1 -p tcp -match multiport -dports xxxxx -j DNAT -to-destination 192.168.1.100 Iptables -I FORWARD -i tun1 -p tcp -d 192.168.1.100 -match multiport -dports xxxxx -j ACCEPT Iptables -I FORWARD -i tun1 -p udp -d 192.168.1.100 -match multiport -dports xxxxx -j ACCEPT Any advice? Sorry that I'm struggling so much with this. Iptables -t nat -A POSTROUTING -o tun1 -j MASQUERADE Iptables -I FORWARD -i tun1 -o br0 -j ACCEPT
Iptables -I FORWARD -i br0 -o tun1 -j ACCEPT Iptables -t nat -I PREROUTING -i tun1 -p udp -dport xxxxx -j DNAT -to-destination 192.168.11.13Īnd then I realized the firewall rules that I got from AirVPN's DD-WRT tutorial used tun0. Iptables -t nat -I PREROUTING -i tun1 -p tcp -dport xxxxx -j DNAT -to-destination 192.168.11.13 Iptables -I FORWARD -i tun1 -p tcp -d 192.168.11.13 -dport xxxxx -j ACCEPT Iptables -I FORWARD -i tun1 -p udp -d 192.168.11.13 -dport xxxxx -j ACCEPT So I updated the command to (note that I'm entering this via Administration > Commands) : I SSHed into the router and found that the VPN is tun1. There must be a device in your ifconfig that represents your VPN adapter.
0 kommentar(er)
