Gargoyle and Pi-Hole (ad-blocking)

Report wireless and/or network connectivity problems in this forum.

Moderator: Moderators

Post Reply
darrepac
Posts: 31
Joined: Thu Dec 22, 2016 6:00 am

Re: Gargoyle and Pi-Hole (ad-blocking)

Post by darrepac »

From Pi-Hole forum (https://discourse.pi-hole.net/t/loop-be ... outer/1105):
Maybe your router does something silly like DNS catching (100% hypothetical):

First with router set to ISP DNS and one of your computers set to Pi-hole DNS

computer asks Pi-hole for address
Pi-hole asks ISP for address
Router catches/blocks this request and asks the ISP himself
Router gets the answer, redirects it to the Pi-hole which gives it to your computer
Name resolved
Now Pi-hole as DNS server in the router:

computer asks Pi-hole for address (as before)
Pi-hole asks ISP for address (as before)
Router catches/blocks this request and asks the Pi-hole himself
Pi-hole asks ISP for address
Router catches/blocks this request and asks the Pi-hole himself
Pi-hole asks ISP for address
Router catches/blocks this request and asks the Pi-hole himself
the never ending story
You get my point? Might be a firewall issue on Gargoyles side. We have many users which successfully use OpenWRT devices without a problem, so an experiences programmer on their side should know about if they have some special rule like this.
Top
Lantis
Moderator
Posts: 6783
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Gargoyle and Pi-Hole (ad-blocking)

Post by Lantis »

You could try the openwrt forum or IRC for a resolution. As far as I'm aware there is nothing special going on.
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Top
darrepac
Posts: 31
Joined: Thu Dec 22, 2016 6:00 am

Re: Gargoyle and Pi-Hole (ad-blocking)

Post by darrepac »

Is there a way to have more detailed log from Gargoyle?
Top
Lantis
Moderator
Posts: 6783
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Gargoyle and Pi-Hole (ad-blocking)

Post by Lantis »

You can manage the log levels in the system config
https://wiki.openwrt.org/doc/uci/system
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Top
tapper
Moderator
Posts: 1076
Joined: Sun Oct 13, 2013 5:49 pm
Location: Stoke-on-trent UK

Re: Gargoyle and Pi-Hole (ad-blocking)

Post by tapper »

Hi yes Gargoyle and OpenWRT does do DNS cashing.
the default is set to 150
in the file /etc/dnsmasq.conf you can set the cash size. I don't use pyhole so i have mine set to:
cache-size=5000
You mite be able to set:
cache-size=0
Linksys WRT3200ACM
NETGEAR Nighthawk R7800
NETGEAR R6260
Top
darrepac
Posts: 31
Joined: Thu Dec 22, 2016 6:00 am

Re: Gargoyle and Pi-Hole (ad-blocking)

Post by darrepac »

I am lost..
Here the log from the moment I change the DNS server up to the first warning about the number of concurrent DNS request.
I am not expert enough..the sole strange thing I see is all this "nameserver" line with IP that I don't know and look weird... Is this normal?
using nameserver 95.142.171.235#53 for domain micro
using nameserver 95.211.32.162#53 for domain micro
using nameserver 66.244.95.20#53 for domain micro
using nameserver 95.142.171.235#53 for domain oss
using nameserver 95.211.32.162#53 for domain oss
using nameserver 66.244.95.20#53 for domain oss
using nameserver 95.142.171.235#53 for domain null
using nameserver 95.211.32.162#53 for domain null
using nameserver 66.244.95.20#53 for domain null
...

Code: Select all

logread -f
Fri Jan  6 23:32:41 2017 daemon.err uhttpd[1018]: uci: Entry not found
Fri Jan  6 23:32:41 2017 daemon.err uhttpd[1018]: uci: Entry not found
Fri Jan  6 23:32:42 2017 daemon.err uhttpd[1018]: uci: Invalid argument
Fri Jan  6 23:32:45 2017 daemon.info dnsmasq[25491]: exiting on receipt of SIGTERM
Fri Jan  6 23:32:45 2017 daemon.err uhttpd[1018]: ls: /sys/bus/mdio_bus/drivers/Marvell*/0:*: No such file or directory
Fri Jan  6 23:32:47 2017 kern.info kernel: [367930.130000] eth0: link down
Fri Jan  6 23:32:47 2017 kern.info kernel: [367930.130000] br-lan: port 1(eth0) entered disabled state
Fri Jan  6 23:32:47 2017 kern.info kernel: [367930.670000] eth1: link down
Fri Jan  6 23:32:48 2017 kern.info kernel: [367930.860000] device wlan0 left promiscuous mode
Fri Jan  6 23:32:48 2017 kern.info kernel: [367930.860000] br-lan: port 2(wlan0) entered disabled state
Fri Jan  6 23:32:48 2017 daemon.err uhttpd[1018]: Error: There is no such init script like 'miniupnpd'.
Fri Jan  6 23:32:48 2017 kern.info kernel: [367931.630000] eth0: link up (1000Mbps/Full duplex)
Fri Jan  6 23:32:48 2017 kern.info kernel: [367931.630000] br-lan: port 1(eth0) entered forwarding state
Fri Jan  6 23:32:48 2017 kern.info kernel: [367931.640000] br-lan: port 1(eth0) entered forwarding state
Fri Jan  6 23:32:48 2017 kern.info kernel: [367931.670000] eth1: link up (100Mbps/Full duplex)
Fri Jan  6 23:32:49 2017 kern.info kernel: [367932.380000] br-lan: port 1(eth0) entered disabled state
Fri Jan  6 23:32:49 2017 kern.info kernel: [367932.390000] device eth0 left promiscuous mode
Fri Jan  6 23:32:49 2017 kern.info kernel: [367932.390000] br-lan: port 1(eth0) entered disabled state
Fri Jan  6 23:32:49 2017 kern.info kernel: [367932.400000] eth1: link down
Fri Jan  6 23:32:49 2017 kern.info kernel: [367932.430000] eth0: link down
Fri Jan  6 23:32:49 2017 kern.info kernel: [367932.500000] device eth0 entered promiscuous mode
Fri Jan  6 23:32:49 2017 kern.info kernel: [367932.500000] br-lan: port 1(eth0) entered forwarding state
Fri Jan  6 23:32:49 2017 kern.info kernel: [367932.510000] br-lan: port 1(eth0) entered forwarding state
Fri Jan  6 23:32:49 2017 daemon.notice netifd: Interface 'lan' is enabled
Fri Jan  6 23:32:49 2017 daemon.notice netifd: Interface 'lan' is setting up now
Fri Jan  6 23:32:49 2017 daemon.notice netifd: Interface 'lan' is now up
Fri Jan  6 23:32:49 2017 daemon.notice netifd: Interface 'loopback' is enabled
Fri Jan  6 23:32:49 2017 daemon.notice netifd: Interface 'loopback' is setting up now
Fri Jan  6 23:32:49 2017 daemon.notice netifd: Interface 'loopback' is now up
Fri Jan  6 23:32:49 2017 daemon.notice netifd: Interface 'wan' is enabled
Fri Jan  6 23:32:49 2017 daemon.notice netifd: Interface 'wan6' is enabled
Fri Jan  6 23:32:49 2017 daemon.notice netifd: Network device 'lo' link is up
Fri Jan  6 23:32:49 2017 daemon.notice netifd: Interface 'loopback' has link connectivity
Fri Jan  6 23:32:49 2017 daemon.notice netifd: Bridge 'br-lan' link is up
Fri Jan  6 23:32:49 2017 daemon.notice netifd: Interface 'lan' has link connectivity
Fri Jan  6 23:32:50 2017 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Fri Jan  6 23:32:50 2017 daemon.notice netifd: Bridge 'br-lan' link is down
Fri Jan  6 23:32:50 2017 daemon.notice netifd: Interface 'lan' has link connectivity loss
Fri Jan  6 23:32:50 2017 kern.info kernel: [367933.390000] br-lan: port 1(eth0) entered disabled state
Fri Jan  6 23:32:50 2017 daemon.notice netifd: radio0 (27225): Configuration file: /var/run/hostapd-phy0.conf
Fri Jan  6 23:32:50 2017 kern.info kernel: [367933.640000] device wlan0 entered promiscuous mode
Fri Jan  6 23:32:50 2017 kern.info kernel: [367933.640000] br-lan: port 2(wlan0) entered forwarding state
Fri Jan  6 23:32:50 2017 kern.info kernel: [367933.650000] br-lan: port 2(wlan0) entered forwarding state
Fri Jan  6 23:32:50 2017 daemon.notice netifd: Bridge 'br-lan' link is up
Fri Jan  6 23:32:50 2017 daemon.notice netifd: Interface 'lan' has link connectivity
Fri Jan  6 23:32:50 2017 daemon.notice netifd: radio0 (27225): Using interface wlan0 with hwaddr f4:f2:6d:49:d1:ee and ssid "XXXXXXXX"
Fri Jan  6 23:32:51 2017 kern.info kernel: [367934.090000] eth0: link up (1000Mbps/Full duplex)
Fri Jan  6 23:32:51 2017 kern.info kernel: [367934.090000] br-lan: port 1(eth0) entered forwarding state
Fri Jan  6 23:32:51 2017 kern.info kernel: [367934.100000] br-lan: port 1(eth0) entered forwarding state
Fri Jan  6 23:32:51 2017 daemon.notice netifd: Network device 'eth0' link is up
Fri Jan  6 23:32:51 2017 kern.info kernel: [367934.390000] br-lan: port 2(wlan0) entered disabled state
Fri Jan  6 23:32:51 2017 kern.info kernel: [367934.600000] br-lan: port 2(wlan0) entered forwarding state
Fri Jan  6 23:32:51 2017 kern.info kernel: [367934.610000] br-lan: port 2(wlan0) entered forwarding state
Fri Jan  6 23:32:51 2017 daemon.notice netifd: radio0 (27225): wlan0: interface state UNINITIALIZED->ENABLED
Fri Jan  6 23:32:51 2017 daemon.notice netifd: radio0 (27225): wlan0: AP-ENABLED
Fri Jan  6 23:32:51 2017 daemon.notice netifd: Network device 'eth1' link is up
Fri Jan  6 23:32:51 2017 kern.info kernel: [367934.680000] eth1: link up (100Mbps/Full duplex)
Fri Jan  6 23:32:51 2017 daemon.notice netifd: Interface 'wan' has link connectivity
Fri Jan  6 23:32:51 2017 daemon.notice netifd: Interface 'wan' is setting up now
Fri Jan  6 23:32:51 2017 daemon.notice netifd: Interface 'wan6' has link connectivity
Fri Jan  6 23:32:51 2017 daemon.notice netifd: Interface 'wan6' is setting up now
Fri Jan  6 23:32:51 2017 daemon.notice netifd: Interface 'wan6' is now up
Fri Jan  6 23:32:52 2017 daemon.notice netifd: wan (27465): udhcpc (v1.23.2) started
Fri Jan  6 23:32:52 2017 daemon.notice netifd: Network device 'wlan0' link is up
Fri Jan  6 23:32:52 2017 daemon.notice netifd: wan (27465): Sending discover...
Fri Jan  6 23:32:52 2017 daemon.notice netifd: wan (27465): Sending select for "MYIP"...
Fri Jan  6 23:32:52 2017 daemon.notice netifd: wan (27465): Lease of "MYIP" obtained, lease time 604800
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: started, version 2.73 cachesize 150
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: compile time options: no-IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: DNS service limited to local subnets
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq-dhcp[27511]: DHCP, IP range 192.168.0.10 -- 192.168.0.80, lease time 12h
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain micro
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain micro
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain micro
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain oss
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain oss
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain oss
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain null
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain null
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain null
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain ing
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain ing
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain ing
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain indy
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain indy
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain indy
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain gopher
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain gopher
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain gopher
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain geek
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain geek
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain geek
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain fur
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain fur
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain fur
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain free
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain free
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain free
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain bbs
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain bbs
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain bbs
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain dyn
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain dyn
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain dyn
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain parody
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain parody
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain parody
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain glue
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain glue
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain glue
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 176.58.118.172#53 for domain bit
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 106.187.47.17#53 for domain bit
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 178.32.31.41#53 for domain bit
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using local addresses only for domain lan
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: reading /tmp/resolv.conf.auto
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain micro
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain micro
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain micro
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain oss
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain oss
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain oss
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain null
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain null
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain null
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain ing
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain ing
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain ing
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain indy
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain indy
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain indy
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain gopher
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain gopher
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain gopher
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain geek
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain geek
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain geek
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain fur
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain fur
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain fur
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain free
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain free
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain free
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain bbs
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain bbs
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain bbs
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain dyn
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain dyn
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain dyn
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain parody
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain parody
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain parody
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain glue
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain glue
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain glue
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 176.58.118.172#53 for domain bit
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 106.187.47.17#53 for domain bit
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 178.32.31.41#53 for domain bit
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using local addresses only for domain lan
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 192.168.0.88#53
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: read /etc/hosts - 19 addresses
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: read /tmp/hosts/dhcp - 1 addresses
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq-dhcp[27511]: read /etc/ethers - 17 addresses
Fri Jan  6 23:32:52 2017 daemon.notice netifd: Interface 'wan' is now up
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: reading /tmp/resolv.conf.auto
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain micro
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain micro
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain micro
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain oss
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain oss
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain oss
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain null
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain null
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain null
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain ing
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain ing
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain ing
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain indy
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain indy
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain indy
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain gopher
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain gopher
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain gopher
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain geek
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain geek
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain geek
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain fur
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain fur
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain fur
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain free
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain free
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain free
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain bbs
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain bbs
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain bbs
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain dyn
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain dyn
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain dyn
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain parody
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain parody
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain parody
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.142.171.235#53 for domain glue
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 95.211.32.162#53 for domain glue
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 66.244.95.20#53 for domain glue
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 176.58.118.172#53 for domain bit
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 106.187.47.17#53 for domain bit
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 178.32.31.41#53 for domain bit
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using local addresses only for domain lan
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 192.168.0.88#53
Fri Jan  6 23:32:52 2017 daemon.info dnsmasq[27511]: using nameserver 192.168.0.88#53
Fri Jan  6 23:32:53 2017 daemon.info hostapd: wlan0: STA fc:f8:ae:b9:5e:74 IEEE 802.11: authenticated
Fri Jan  6 23:32:53 2017 daemon.info hostapd: wlan0: STA fc:f8:ae:b9:5e:74 IEEE 802.11: associated (aid 1)
Fri Jan  6 23:32:53 2017 kern.info kernel: [367936.100000] br-lan: port 1(eth0) entered forwarding state
Fri Jan  6 23:32:53 2017 daemon.err uhttpd[1018]: Another app is currently holding the xtables lock. Perhaps you want to use the -w option?
Fri Jan  6 23:32:53 2017 authpriv.info dropbear[27595]: Child connection from 116.31.116.47:22555
Fri Jan  6 23:32:53 2017 daemon.info hostapd: wlan0: STA 80:1f:02:e2:6a:0a IEEE 802.11: authenticated
Fri Jan  6 23:32:53 2017 daemon.info hostapd: wlan0: STA 80:1f:02:e2:6a:0a IEEE 802.11: associated (aid 2)
Fri Jan  6 23:32:53 2017 daemon.info hostapd: wlan0: STA 80:1f:02:e2:6a:0a WPA: pairwise key handshake completed (RSN)
Fri Jan  6 23:32:53 2017 daemon.info hostapd: wlan0: STA fc:f8:ae:b9:5e:74 WPA: pairwise key handshake completed (RSN)
Fri Jan  6 23:32:53 2017 daemon.info dnsmasq-dhcp[27511]: DHCPREQUEST(br-lan) 192.168.0.16 fc:f8:ae:b9:5e:74
Fri Jan  6 23:32:53 2017 daemon.info dnsmasq-dhcp[27511]: DHCPACK(br-lan) 192.168.0.16 fc:f8:ae:b9:5e:74 Sommital_PC
Fri Jan  6 23:32:53 2017 kern.info kernel: [367936.610000] br-lan: port 2(wlan0) entered forwarding state
Fri Jan  6 23:32:53 2017 daemon.err uhttpd[1018]: uci: Entry not found
Fri Jan  6 23:32:54 2017 daemon.err uhttpd[1018]: arping: interface eth0 not found: No such device
Fri Jan  6 23:32:54 2017 daemon.info hostapd: wlan0: STA 14:8f:c6:51:e3:75 IEEE 802.11: authenticated
Fri Jan  6 23:32:54 2017 daemon.info hostapd: wlan0: STA 14:8f:c6:51:e3:75 IEEE 802.11: associated (aid 3)
Fri Jan  6 23:32:54 2017 daemon.info hostapd: wlan0: STA 14:8f:c6:51:e3:75 WPA: pairwise key handshake completed (RSN)
Fri Jan  6 23:32:54 2017 daemon.info dnsmasq-dhcp[27511]: DHCPREQUEST(br-lan) 192.168.0.11 14:8f:c6:51:e3:75
Fri Jan  6 23:32:54 2017 daemon.info dnsmasq-dhcp[27511]: DHCPACK(br-lan) 192.168.0.11 14:8f:c6:51:e3:75 iPhone-de-Fleur
Fri Jan  6 23:32:56 2017 daemon.err uhttpd[1018]: sh: write error: Broken pipe
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27511]: exiting on receipt of SIGTERM
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: started, version 2.73 cachesize 150
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: compile time options: no-IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: DNS service limited to local subnets
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq-dhcp[27854]: DHCP, IP range 192.168.0.10 -- 192.168.0.80, lease time 12h
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain micro
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain micro
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain micro
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain oss
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain oss
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain oss
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain null
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain null
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain null
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain ing
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain ing
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain ing
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain indy
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain indy
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain indy
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain gopher
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain gopher
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain gopher
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain geek
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain geek
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain geek
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain fur
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain fur
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain fur
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain free
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain free
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain free
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain bbs
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain bbs
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain bbs
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain dyn
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain dyn
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain dyn
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain parody
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain parody
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain parody
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain glue
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain glue
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain glue
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 176.58.118.172#53 for domain bit
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 106.187.47.17#53 for domain bit
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 178.32.31.41#53 for domain bit
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using local addresses only for domain lan
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: reading /tmp/resolv.conf.auto
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain micro
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain micro
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain micro
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain oss
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain oss
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain oss
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain null
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain null
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain null
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain ing
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain ing
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain ing
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain indy
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain indy
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain indy
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain gopher
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain gopher
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain gopher
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain geek
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain geek
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain geek
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain fur
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain fur
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain fur
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain free
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain free
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain free
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain bbs
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain bbs
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain bbs
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain dyn
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain dyn
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain dyn
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain parody
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain parody
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain parody
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.142.171.235#53 for domain glue
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 95.211.32.162#53 for domain glue
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 66.244.95.20#53 for domain glue
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 176.58.118.172#53 for domain bit
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 106.187.47.17#53 for domain bit
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 178.32.31.41#53 for domain bit
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using local addresses only for domain lan
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 192.168.0.88#53
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: using nameserver 192.168.0.88#53
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: read /etc/hosts - 19 addresses
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq[27854]: read /tmp/hosts/dhcp - 1 addresses
Fri Jan  6 23:32:56 2017 daemon.info dnsmasq-dhcp[27854]: read /etc/ethers - 17 addresses
Fri Jan  6 23:32:59 2017 authpriv.info dropbear[27595]: Exit before auth: Disconnect received
Fri Jan  6 23:33:01 2017 daemon.info hostapd: wlan0: STA 00:11:f6:8e:b8:70 IEEE 802.11: authenticated
Fri Jan  6 23:33:01 2017 daemon.info hostapd: wlan0: STA 00:11:f6:8e:b8:70 IEEE 802.11: associated (aid 4)
Fri Jan  6 23:33:02 2017 daemon.info hostapd: wlan0: STA 00:11:f6:8e:b8:70 WPA: pairwise key handshake completed (RSN)
Fri Jan  6 23:33:02 2017 daemon.info dnsmasq-dhcp[27854]: DHCPDISCOVER(br-lan) 00:11:f6:8e:b8:70
Fri Jan  6 23:33:02 2017 daemon.info dnsmasq-dhcp[27854]: DHCPOFFER(br-lan) 192.168.0.15 00:11:f6:8e:b8:70
Fri Jan  6 23:33:02 2017 daemon.info dnsmasq-dhcp[27854]: DHCPREQUEST(br-lan) 192.168.0.15 00:11:f6:8e:b8:70
Fri Jan  6 23:33:02 2017 daemon.info dnsmasq-dhcp[27854]: DHCPACK(br-lan) 192.168.0.15 00:11:f6:8e:b8:70 tablette_domotique
Fri Jan  6 23:33:05 2017 daemon.warn dnsmasq[27854]: Maximum number of concurrent DNS queries reached (max: 150)
Top
Lantis
Moderator
Posts: 6783
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Gargoyle and Pi-Hole (ad-blocking)

Post by Lantis »

Those are for namecoin resolution.
Normal behaviour
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Top
tapper
Moderator
Posts: 1076
Joined: Sun Oct 13, 2013 5:49 pm
Location: Stoke-on-trent UK

Re: Gargoyle and Pi-Hole (ad-blocking)

Post by tapper »

Hi if you would like to stop that untik the box for   Allow NameCoin/OpenNIC Resolution
on the Connection page.
Linksys WRT3200ACM
NETGEAR Nighthawk R7800
NETGEAR R6260
Top
darrepac
Posts: 31
Joined: Thu Dec 22, 2016 6:00 am

Re: Gargoyle and Pi-Hole (ad-blocking)

Post by darrepac »

Ok, in order to better understand what was going on, I put logqueries to 1 in order to see the DNS queries into the log of the router and ... I discover that once pi-hole (192.168.0.88) is forwarding a request from a computer (192.168.0.10) to DNS server of my ISP, the router seems to catch it and make the same request (which explain why there is a loop once I put pi-hole as DNS server)...see below:

Code: Select all

pi-hole:
Jan  7 18:04:51 dnsmasq[451]: query[A] www.prout.fr from 192.168.0.10
Jan  7 18:04:51 dnsmasq[451]: forwarded www.prout.fr to 212.27.40.241
Jan  7 18:04:51 dnsmasq[451]: query[A] www.prout.fr from 192.168.0.10
Jan  7 18:04:51 dnsmasq[451]: forwarded www.prout.fr to 212.27.40.240
Jan  7 18:04:51 dnsmasq[451]: forwarded www.prout.fr to 212.27.40.241
Jan  7 18:04:51 dnsmasq[451]: reply www.prout.fr is 149.202.133.35

Router:
Sat Jan  7 18:04:51 2017 daemon.info dnsmasq[6049]: query[A] www.prout.fr from 192.168.0.88
Sat Jan  7 18:04:51 2017 daemon.info dnsmasq[6049]: forwarded www.prout.fr to 212.27.40.240
Sat Jan  7 18:04:51 2017 daemon.info dnsmasq[6049]: query[A] www.prout.fr from 192.168.0.88
Sat Jan  7 18:04:51 2017 daemon.info dnsmasq[6049]: forwarded www.prout.fr to 212.27.40.240
Sat Jan  7 18:04:51 2017 daemon.info dnsmasq[6049]: query[A] www.prout.fr from 192.168.0.88
Sat Jan  7 18:04:51 2017 daemon.info dnsmasq[6049]: forwarded www.prout.fr to 212.27.40.241
Sat Jan  7 18:04:51 2017 daemon.info dnsmasq[6049]: forwarded www.prout.fr to 212.27.40.240
Sat Jan  7 18:04:51 2017 daemon.info dnsmasq[6049]: reply www.prout.fr is 149.202.133.35
Sat Jan  7 18:04:51 2017 daemon.info dnsmasq[6049]: reply www.prout.fr is 149.202.133.35
Is this normal?
Top
Lantis
Moderator
Posts: 6783
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Gargoyle and Pi-Hole (ad-blocking)

Post by Lantis »

What DNS server are the devices set to use?
They should be pointing at the router, which will do the forwarding.

If that is the current scenario, try pointing them directly at the Pi-hole.
If that resolves the issue, we could change dnsmasq to advertise the pi-hole directly rather than itself (I believe it's an option "6")
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Top
Post Reply

Return to “Network / Wireless Issues”