DNS adblocking ignored on connected clients with Internet access provided over WiFi in 'Client' modeopenwrt: dns resolving error from wifi connected devicesHow to configure Linux Mint 18.2 for a Captive WiFi Access Point with no Internet AccessMap DNS requests coming from specific client MAC with dnsmasqUse DHCP-provided DNS or not based on connected network
What historical events would have to change in order to make 19th century "steampunk" technology possible?
How to enclose theorems and definition in rectangles?
Does int main() need a declaration on C++?
How to install cross-compiler on Ubuntu 18.04?
How to find if SQL server backup is encrypted with TDE without restoring the backup
Is it possible to map the firing of neurons in the human brain so as to stimulate artificial memories in someone else?
What are the G forces leaving Earth orbit?
Implication of namely
Mathematica command that allows it to read my intentions
What's the meaning of "Sollensaussagen"?
Convert seconds to minutes
How to travel to Japan while expressing milk?
My ex-girlfriend uses my Apple ID to log in to her iPad. Do I have to give her my Apple ID password to reset it?
How does a dynamic QR code work?
In Bayesian inference, why are some terms dropped from the posterior predictive?
What is the opposite of "eschatology"?
Am I breaking OOP practice with this architecture?
How do conventional missiles fly?
What does the same-ish mean?
Unlock My Phone! February 2018
Different meanings of こわい
How badly should I try to prevent a user from XSSing themselves?
Why is the sentence "Das ist eine Nase" correct?
Is this draw by repetition?
DNS adblocking ignored on connected clients with Internet access provided over WiFi in 'Client' mode
openwrt: dns resolving error from wifi connected devicesHow to configure Linux Mint 18.2 for a Captive WiFi Access Point with no Internet AccessMap DNS requests coming from specific client MAC with dnsmasqUse DHCP-provided DNS or not based on connected network
Ad-blocking is done through 'dnsmasq' which reads a hosts
file, when logged into the OpenWrt device blocking works as expected:
PING s0.2mdn.net (0.0.0.0): 56 data bytes
64 bytes from 127.0.0.1: seq=0 ttl=64 time=0.268 ms
...
However on a computer that is connected to the OpenWrt router (wired or wireless) blocking does not work.
danielsokolowski@DANDC-OFFICE:~$ ping s0.2mdn.net
Pinging s0-2mdn-net.l.google.com [172.217.1.166] with 32 bytes of data:
Reply from 172.217.1.166: bytes=32 time=22ms TTL=56
..
Some info :
root@481:~# cat /etc/resolv.conf
search lan
nameserver 127.0.0.1
root@481:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
10.4.81.0 * 255.255.255.0 U 0 0 0 br-lan
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
root@481:~# netstat -lp | grep dnsmasq
tcp 0 0 192.168.0.103:domain 0.0.0.0:* LISTEN 1890/dnsmasq
tcp 0 0 localhost:domain 0.0.0.0:* LISTEN 1890/dnsmasq
tcp 0 0 481.lan:domain 0.0.0.0:* LISTEN 1890/dnsmasq
tcp 0 0 fe80::ccd3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::c8d3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 localhost:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::3818:b0ff:fe7f:7cc6:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
udp 0 0 192.168.0.103:domain 0.0.0.0:* 1890/dnsmasq
udp 0 0 localhost:domain 0.0.0.0:* 1890/dnsmasq
udp 0 0 481.lan:domain 0.0.0.0:* 1890/dnsmasq
udp 0 0 0.0.0.0:bootps 0.0.0.0:* 1890/dnsmasq
udp 0 0 fe80::ccd3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 fe80::c8d3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 localhost:domain :::* 1890/dnsmasq
udp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 fe80::3818:b0ff:fe7f:7cc6:domain :::* 1890/dnsmasq
udp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
root@481:~#
openwrt dnsmasq hosts
add a comment |
Ad-blocking is done through 'dnsmasq' which reads a hosts
file, when logged into the OpenWrt device blocking works as expected:
PING s0.2mdn.net (0.0.0.0): 56 data bytes
64 bytes from 127.0.0.1: seq=0 ttl=64 time=0.268 ms
...
However on a computer that is connected to the OpenWrt router (wired or wireless) blocking does not work.
danielsokolowski@DANDC-OFFICE:~$ ping s0.2mdn.net
Pinging s0-2mdn-net.l.google.com [172.217.1.166] with 32 bytes of data:
Reply from 172.217.1.166: bytes=32 time=22ms TTL=56
..
Some info :
root@481:~# cat /etc/resolv.conf
search lan
nameserver 127.0.0.1
root@481:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
10.4.81.0 * 255.255.255.0 U 0 0 0 br-lan
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
root@481:~# netstat -lp | grep dnsmasq
tcp 0 0 192.168.0.103:domain 0.0.0.0:* LISTEN 1890/dnsmasq
tcp 0 0 localhost:domain 0.0.0.0:* LISTEN 1890/dnsmasq
tcp 0 0 481.lan:domain 0.0.0.0:* LISTEN 1890/dnsmasq
tcp 0 0 fe80::ccd3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::c8d3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 localhost:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::3818:b0ff:fe7f:7cc6:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
udp 0 0 192.168.0.103:domain 0.0.0.0:* 1890/dnsmasq
udp 0 0 localhost:domain 0.0.0.0:* 1890/dnsmasq
udp 0 0 481.lan:domain 0.0.0.0:* 1890/dnsmasq
udp 0 0 0.0.0.0:bootps 0.0.0.0:* 1890/dnsmasq
udp 0 0 fe80::ccd3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 fe80::c8d3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 localhost:domain :::* 1890/dnsmasq
udp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 fe80::3818:b0ff:fe7f:7cc6:domain :::* 1890/dnsmasq
udp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
root@481:~#
openwrt dnsmasq hosts
@roaima I'm sorry I can't test the wired setup any more....I've updated the question.
– Daniel Sokolowski
2 days ago
dnsmasq
is on the router, see updated answer.
– Daniel Sokolowski
2 days ago
So, it's effectively DNS-based ad-blocking, and so the clients would have to be configured to use the router's DNS service in order to take advantage of the ad-blocking. Check which DNS nameserver(s) the WiFi clients are actually using.
– telcoM
yesterday
add a comment |
Ad-blocking is done through 'dnsmasq' which reads a hosts
file, when logged into the OpenWrt device blocking works as expected:
PING s0.2mdn.net (0.0.0.0): 56 data bytes
64 bytes from 127.0.0.1: seq=0 ttl=64 time=0.268 ms
...
However on a computer that is connected to the OpenWrt router (wired or wireless) blocking does not work.
danielsokolowski@DANDC-OFFICE:~$ ping s0.2mdn.net
Pinging s0-2mdn-net.l.google.com [172.217.1.166] with 32 bytes of data:
Reply from 172.217.1.166: bytes=32 time=22ms TTL=56
..
Some info :
root@481:~# cat /etc/resolv.conf
search lan
nameserver 127.0.0.1
root@481:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
10.4.81.0 * 255.255.255.0 U 0 0 0 br-lan
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
root@481:~# netstat -lp | grep dnsmasq
tcp 0 0 192.168.0.103:domain 0.0.0.0:* LISTEN 1890/dnsmasq
tcp 0 0 localhost:domain 0.0.0.0:* LISTEN 1890/dnsmasq
tcp 0 0 481.lan:domain 0.0.0.0:* LISTEN 1890/dnsmasq
tcp 0 0 fe80::ccd3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::c8d3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 localhost:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::3818:b0ff:fe7f:7cc6:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
udp 0 0 192.168.0.103:domain 0.0.0.0:* 1890/dnsmasq
udp 0 0 localhost:domain 0.0.0.0:* 1890/dnsmasq
udp 0 0 481.lan:domain 0.0.0.0:* 1890/dnsmasq
udp 0 0 0.0.0.0:bootps 0.0.0.0:* 1890/dnsmasq
udp 0 0 fe80::ccd3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 fe80::c8d3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 localhost:domain :::* 1890/dnsmasq
udp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 fe80::3818:b0ff:fe7f:7cc6:domain :::* 1890/dnsmasq
udp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
root@481:~#
openwrt dnsmasq hosts
Ad-blocking is done through 'dnsmasq' which reads a hosts
file, when logged into the OpenWrt device blocking works as expected:
PING s0.2mdn.net (0.0.0.0): 56 data bytes
64 bytes from 127.0.0.1: seq=0 ttl=64 time=0.268 ms
...
However on a computer that is connected to the OpenWrt router (wired or wireless) blocking does not work.
danielsokolowski@DANDC-OFFICE:~$ ping s0.2mdn.net
Pinging s0-2mdn-net.l.google.com [172.217.1.166] with 32 bytes of data:
Reply from 172.217.1.166: bytes=32 time=22ms TTL=56
..
Some info :
root@481:~# cat /etc/resolv.conf
search lan
nameserver 127.0.0.1
root@481:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
10.4.81.0 * 255.255.255.0 U 0 0 0 br-lan
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
root@481:~# netstat -lp | grep dnsmasq
tcp 0 0 192.168.0.103:domain 0.0.0.0:* LISTEN 1890/dnsmasq
tcp 0 0 localhost:domain 0.0.0.0:* LISTEN 1890/dnsmasq
tcp 0 0 481.lan:domain 0.0.0.0:* LISTEN 1890/dnsmasq
tcp 0 0 fe80::ccd3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::c8d3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 localhost:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::3818:b0ff:fe7f:7cc6:domain :::* LISTEN 1890/dnsmasq
tcp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* LISTEN 1890/dnsmasq
udp 0 0 192.168.0.103:domain 0.0.0.0:* 1890/dnsmasq
udp 0 0 localhost:domain 0.0.0.0:* 1890/dnsmasq
udp 0 0 481.lan:domain 0.0.0.0:* 1890/dnsmasq
udp 0 0 0.0.0.0:bootps 0.0.0.0:* 1890/dnsmasq
udp 0 0 fe80::ccd3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 fe80::c8d3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 localhost:domain :::* 1890/dnsmasq
udp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
udp 0 0 fe80::3818:b0ff:fe7f:7cc6:domain :::* 1890/dnsmasq
udp 0 0 fe80::cad3:a3ff:fe66:284d:domain :::* 1890/dnsmasq
root@481:~#
openwrt dnsmasq hosts
openwrt dnsmasq hosts
edited yesterday
Rui F Ribeiro
41.8k1483142
41.8k1483142
asked 2 days ago
Daniel SokolowskiDaniel Sokolowski
1355
1355
@roaima I'm sorry I can't test the wired setup any more....I've updated the question.
– Daniel Sokolowski
2 days ago
dnsmasq
is on the router, see updated answer.
– Daniel Sokolowski
2 days ago
So, it's effectively DNS-based ad-blocking, and so the clients would have to be configured to use the router's DNS service in order to take advantage of the ad-blocking. Check which DNS nameserver(s) the WiFi clients are actually using.
– telcoM
yesterday
add a comment |
@roaima I'm sorry I can't test the wired setup any more....I've updated the question.
– Daniel Sokolowski
2 days ago
dnsmasq
is on the router, see updated answer.
– Daniel Sokolowski
2 days ago
So, it's effectively DNS-based ad-blocking, and so the clients would have to be configured to use the router's DNS service in order to take advantage of the ad-blocking. Check which DNS nameserver(s) the WiFi clients are actually using.
– telcoM
yesterday
@roaima I'm sorry I can't test the wired setup any more....I've updated the question.
– Daniel Sokolowski
2 days ago
@roaima I'm sorry I can't test the wired setup any more....I've updated the question.
– Daniel Sokolowski
2 days ago
dnsmasq
is on the router, see updated answer.– Daniel Sokolowski
2 days ago
dnsmasq
is on the router, see updated answer.– Daniel Sokolowski
2 days ago
So, it's effectively DNS-based ad-blocking, and so the clients would have to be configured to use the router's DNS service in order to take advantage of the ad-blocking. Check which DNS nameserver(s) the WiFi clients are actually using.
– telcoM
yesterday
So, it's effectively DNS-based ad-blocking, and so the clients would have to be configured to use the router's DNS service in order to take advantage of the ad-blocking. Check which DNS nameserver(s) the WiFi clients are actually using.
– telcoM
yesterday
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509757%2fdns-adblocking-ignored-on-connected-clients-with-internet-access-provided-over-w%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509757%2fdns-adblocking-ignored-on-connected-clients-with-internet-access-provided-over-w%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
@roaima I'm sorry I can't test the wired setup any more....I've updated the question.
– Daniel Sokolowski
2 days ago
dnsmasq
is on the router, see updated answer.– Daniel Sokolowski
2 days ago
So, it's effectively DNS-based ad-blocking, and so the clients would have to be configured to use the router's DNS service in order to take advantage of the ad-blocking. Check which DNS nameserver(s) the WiFi clients are actually using.
– telcoM
yesterday