![]() Start by going to the router's GUI with your web browser and checking what the router's WAN IP is. If you have a lot of changes then you'll likely want to test other possibilities first since most problems are user error anyways. If you have made few changes from the default configuration then you should try this first. The only cases I've seen of genuine bugs with port forwards in DD-WRT have been unexplainable behavior of the underlying iptables rules that was fixed by hard resetting and reconfiguring from scratch. Basic Troubleshooting Did You Hard Reset? You should first familiarize yourself with how to configure Port Forwarding before trying to troubleshoot it. There can be many problems including multiple layers of NAT (router behind another router), misconfiguration of the port forward, software firewalls on the host being forwarded to, unexplainable behavior caused by not hard resetting the router, etc. Iptables -t filter -I FORWARD -s 192.168.1.30/32 -p tcp -d yahoo.This page explains how to troubleshoot common port forwarding troubles to figure out what the problem really is so that you can fix it. For changeing name he needs rooted android).Įnable DNSMasq and local dns option (but disable "No DNS Rebind" option!)ĭhcp-host=android1234579,192.168.1.30,infinite (he can change android's MAC easily with free MAC changer but not the name. I would bind that android device name with local IP first but for learning purposes I would do it like this: Stubby for DNS over TLS I DNSCrypt v2 by mac913 Netgear R7000 -DD-WRT 52671 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN Netgear R9000 -DD-WRT 52459 Gateway/StubbyDoT/DNS,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla Netgear R7800 -DD-WRT 52671 Gateway/DoT DNS,AD-Block,AP&Net Isolation,x3VLAN,Firewall,Vanilla TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas TP-Link WR1043NDv2 -DD-WRT 52459 Gateway/DoT DNS,Ad-Block,Firewall,Forced DNS,x4VLAN(no-wifi) TP-Link WR1043NDv2 -DD-WRT 52671 Gateway/DoT DNS,AP Isolation,Ad-Block,Firewall,Forced DNS,VPN,VLAN Location: UK, London, just across the river.įor better site/ip blocking use either IPtables or Advanced DNSmasq rules.Īccess restriction is working but only for http sites it does not block https in that way its expected How do get the router to actually block the root of a site added to the blocked URL list? This could be a problem if the root of an page redirection is infected with malware because the router will still allow the site to load initially. So I added another non-https capable site and it appears to be working, however the filter does not block the root of the site, only when a user navigates onto a directory within the site.įor instance even with /*,, / (etc.) added to the banned URL lists, the router still allows, but blocks any other subdirectory on that page such as /page1, /page2, /downloads. The problem is automatic https redirection that is built into firefox. I'll tr it on my wired PC and see it it works. OK, but regular http access should be blocked, but it seems to no to working at ALL. sites will not be blocked due to encryption. Nexx WT3020F Openwrt #4.14.167 (OpenVPN server, Wireguard server, AD blocking, SQM QOS, USB) Sites will not be blocked due to encryption.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |