From: Tapani Tarvainen <ipfire@tapanitarvainen.fi>
To: development@lists.ipfire.org
Subject: Re: Forcing all DNS traffic from the LAN to the firewall
Date: Fri, 13 Nov 2020 16:55:33 +0200 [thread overview]
Message-ID: <20201113145533.GB218744@vesikko.tarvainen.info> (raw)
In-Reply-To: <BB314BB5-C153-411E-8823-5E13A835E0A9@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2238 bytes --]
On Fri, Nov 13, 2020 at 02:23:10PM +0000, Michael Tremer (michael.tremer(a)ipfire.org) wrote:
> > - Do we need this?
> > [Hm. ;-) As I heard, some folks do.]
>
> Very good question.
>
> I do not entirely understand the use-case for this. And I think
> nobody has shown an example at all here.
Agreed. The use case has been dubious to begin with, and as noted
DoH is making it increasingly so.
> So what I could come up with is this:
>
> * You have a host on your network that does not use your DNS servers.
>
> * You have a host on your network that does not allow you to put in custom DNS servers.
>
> I would simply say: Throw them away. That is not network equipment.
> It simply is a bug, and that should not be fixed by us.
Agreed.
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.
But any kid smart enough to change DNS settings in their laptop or
whatever is also smart enough to work around such redirection.
> I would say that that checkbox that you have added should block
> using any other DNS server except the ones configured by the DHCP
> server.
Yes. That'd be better, although even its usefulness is doubtful.
> As an admin you want to know what is going wrong and not silently
> redirect this.
You should. At best it would give you an excuse, a way to claim you
tried to prevent <whatever>. Might be useful in a school or a library
in some places...
But I seriously dislike such reasons and don't think IPFire should
cave in even if someone actually argues for them (not that people
are likely to, as it'd obviously undermine them!).
> If you really really want to redirect, I think the best option is to
> add that functionality to the firewall UI that users can create a
> rule that redirects this traffic. That way it is absolutely explicit
> and the admin hopefully knows what they are doing.
I could live with that, even if I doubt the need.
Actually I'd prefer a generic mechanism for setting redirections
for whatever types of packets. But not a high priority for me.
--
Tapani Tarvainen
next prev parent reply other threads:[~2020-11-13 14:55 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 [this message]
2020-11-15 13:16 ` Matthias Fischer
2020-11-15 14:45 ` Michael Tremer
2020-11-15 15:33 ` Tapani Tarvainen
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=20201113145533.GB218744@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