![]() Because DNSMasq is daemonized, the script continues on. IOW, DNSMasq is always monitoring that file for changes.īy adding the DNSMasq restart, that has introduced an intermittent DNS leak. Unless DNSMasq is configured w/ the no-poll directive, it will reread resolv.dnsmasq should its timestamp change. But it's certainly not necessary for the purposes of updating the active DNS servers. Iptables -I POSTROUTING -t nat -o tun1 -j MASQUERADEĬat /tmp/resolv.dnsmasq > /tmp/resolv.dnsmasq_ispĮnv | grep 'dhcp-option DNS' | awk '' > /tmp/resolv.dnsmasqĬat /tmp/resolv.dnsmasq_isp > /tmp/resolv.dnsmasqįrankly, I don't know why a DNSMasq restart was added. Iptables -D POSTROUTING -t nat -o tun1 -j MASQUERADE On my own (older) dd-wrt router (Asus RT-N10+ rev D1,įirmware Version DD-WRT v24-sp2 (12/13/14) kong - build 25630M), that script is as follows (and works fine): The OpenVPN client uses a route-up script to add the VPN's DNS servers to DNSMasq. It was discovered while dealing w/ the following thread. There's a bug in the OpenVPN client that causes intermittent DNS leaks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |