public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Tapani Tarvainen <ipfire@tapanitarvainen.fi>
To: development@lists.ipfire.org
Subject: Re: Forcing all DNS traffic from the LAN to the firewall
Date: Sun, 15 Nov 2020 17:33:18 +0200	[thread overview]
Message-ID: <20201115153318.GB727329@vesikko.tarvainen.info> (raw)
In-Reply-To: <008da5bd-4700-e382-c228-1faf3895dfb1@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2082 bytes --]

On Sun, Nov 15, 2020 at 02:16:46PM +0100, Matthias Fischer (matthias.fischer(a)ipfire.org) wrote:

> > But I guess the situation some people have in mind is that you have
> > *users* in your network you can't really control or trust not to mess
> > up with DNS settings in their machines. As in, children.
> 
> Or you have *machines* (in this case, Apps) you can't control, because
> they don't even have an input field for "DNS".

... and have their own hardcoded DNS servers instead of trusting what
DHCP says nor any Private DNS configuration in the phone (I presume
you've tried that). Yeah, such abominations do exist.

And if you really can't avoid using them and still really need to be
able to control which addresses they see, I guess port 53 redirection
in the firewall makes sense.

I doubt that's a common enough case to warrant a custom setting in
IPFire, but I don't mind having one (I'm not doing the work after
all).

> > But any kid smart enough to change DNS settings in their laptop or
> > whatever is also smart enough to work around such redirection.

> I'm curious. How could this be done? I have tested the REDIRECT rules
> with various arbitrary entries, even with non-existing addresses. So
> far, DNS queries were always redirected to the DNS servers specified in
> IPFire until now. I even didn't notice that I tested with irregular or
> invalid addresses.

Well, today the easy way is to use DoH.

Or DoT, if you don't block port 853.

Other ways exist for the more nerdy types, from just /etc/hosts to
tunneling DNS via some other port or another app, even over Facebook.
(I was in working Saudi Arabia some 20 years ago when they introduced
Internet there, along with DNS-based censorship - people can be pretty
creative.)

Wardriving isn't an entirely forgotten art either.

And today's kids... you could find a 10-year-old running a virtual
machine in his laptop or a Raspberry Pi with a custom DNS+DHCP server
that fetches the forbidden addresses from his friends over WhatsApp.

-- 
Tapani Tarvainen

  parent reply	other threads:[~2020-11-15 15:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 17:47 Matthias Fischer
2020-11-10 13:07 ` Tapani Tarvainen
2020-11-13 14:24   ` Michael Tremer
2020-11-13 14:35     ` Tapani Tarvainen
2020-11-11 15:02 ` Rainer Kemme
2020-11-13 14:23 ` Michael Tremer
2020-11-13 14:55   ` Tapani Tarvainen
2020-11-15 13:16     ` Matthias Fischer
2020-11-15 14:45       ` Michael Tremer
2020-11-15 15:33       ` Tapani Tarvainen [this message]
2020-11-16 10:32         ` Michael Tremer
2020-11-15 14:40     ` Michael Tremer
2020-11-13 16:57   ` Matthias Fischer
2020-11-13 17:08     ` Paul Simmons
2020-11-15 13:36     ` Matthias Fischer
2020-11-15 14:50       ` Michael Tremer
2020-11-15 15:44         ` Tapani Tarvainen
2020-11-16 10:34           ` Michael Tremer
2020-11-23  9:08         ` Matthias Fischer
2020-12-25 16:57           ` Matthias Fischer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201115153318.GB727329@vesikko.tarvainen.info \
    --to=ipfire@tapanitarvainen.fi \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox