Search the Community
Showing results for tags 'dnsmasq'.
Found 2 results
Hello, have a ASUS RT-AC68P with the latest Merlin firmware with an unRAID server running behind it with Nextcloud. Trying to setup DNSMasq on the router and followed the guide here. I am using AirVPN for the VPN service. Have the following in my jffs partition with port forwarding already setup on AirVPN and IP tables setup. 192.168.1.75 being my unRAID server. Code:address=/airdns.org/192.168.1.75This works fine so when on LAN and type in the DDNS Nextcloud server address ***.airdns.org:PORT it redirects to the internal server. Externally it works fine also. However, this breaks the WAN access and keeps me from accessing any websites, etc. Actually the WiFi even stops working - i had to hardwire to get it all reset. In the WAN -> WAN DNS Setting - i have it set to Yes, automatic AiProtection -> Enable DNS-based Filtering is OFF LAN -> DNS Server 1 -> 192.168.1.1 VPN -> OpenVPN Clients -> Accept DNS Configuration to "Exclusive" and Redirect Internet traffic to "Policy Rules" Any ideas? **SOLVED** Need to setup DNSMasq on the router side and reverse proxy on the server side. Works fine that way in case other had similar issues. I'm sure there are better ways to do this but this is what worked for me.
The resolv-conf-update script uses bash-specific variable substitutions so won't work on my dd-wrt router, firmware v3.0-r28112 so, having followed the Air setup guide, I've made the following changes to action the pushed dns value. - remove the static dns entry for 10.x.0.1 from the Basic setup page. I do have an OpenNIC static dns ip there too. - added the following script to the Admin,Commands,Startup to edit the resolver config file # Ensure client enabled [ `nvram get openvpncl_enable` ] || exit OVPN='/tmp/openvpncl' DNSMQ='/tmp/dnsmasq.conf' echo "#!/bin/sh # Fetch dnsmasq's 'resolv.conf' RSLV=\`sed '/resolv-file/!d ; s/.*=//' $DNSMQ\` # Edit resolver conf - (only works for single pushed dns server) case \$script_type in up) # Get pushed dns from env PDNS=\`set | sed '/foreign_option_.*dhcp-option DNS /!d ; s/.* \([0-9.]*\).*/nameserver \1/'\` sed -i \"1s/^/\$PDNS\n/\" \$RSLV echo \$PDNS >$OVPN/pdns ;; down) PDNS=\`set | cat $OVPN/pdns\` sed -i \"/\$PDNS/d\" \$RSLV ;; esac " > $OVPN/updown.sh # Hack redundant, problem rules sed -i 's/\(.*-I INPUT\)\(.*j \).*/\1 2 \2REJECT/' $OVPN/route-*.sh sed -i 's/\(.*-D INPUT\)\(.*j \).*/\1 \2REJECT/' $OVPN/route-*.sh sed -i '/FORWARD/d' $OVPN/route-*.sh chmod 600 $OVPN/* chmod 700 $OVPN/*.sh killall openvpn ; openvpn --config /tmp/openvpncl/openvpn.conf --route-up /tmp/openvpncl/route-up.sh --down-pre /tmp/openvpncl/route-down.sh --daemon dnsmasq polls its resolver file, resolv.dnsmasq, and acts on changes, so doesn't require any explicit update instructions. Note: **added** openvpn restart - there's currently a timing issue (updown.sh isn't created until after the initial start of openvpn, which consequently fails) - add the following directives to the openvpn config up /tmp/openvpncl/updown.sh down /tmp/openvpncl/updown.sh - check it works by visiting ipleak.net or look at /tmp/resolv.dnsmasq on the dd-wrt