From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Forcing all DNS traffic from the LAN to the firewall
Date: Sun, 15 Nov 2020 14:45:35 +0000 [thread overview]
Message-ID: <98A8702B-307A-42B3-B10E-9B0D028E4C07@ipfire.org> (raw)
In-Reply-To: <008da5bd-4700-e382-c228-1faf3895dfb1@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1956 bytes --]
> On 15 Nov 2020, at 13:16, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> On 13.11.2020 15:55, Tapani Tarvainen wrote:
>> On Fri, Nov 13, 2020 at 02:23:10PM +0000, Michael Tremer (michael.tremer(a)ipfire.org) wrote:
>> ...
>>> 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.
>
> Or you have *machines* (in this case, Apps) you can't control, because
> they don't even have an input field for "DNS".
Do you have any examples?
I have never encountered that, because if they allow static configuration of the IP address, they won’t get a DNS server at all.
For devices that only support DHCP, this might make sense. I have a Philips Hue bridge that does not support static configuration and simply gets a lease from the DHCP server. The intention probably is being all zero-configuration.
>> 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 withirregular or
> invalid addresses.
Proxies. VPNs. Tor. Remotely logging in to another computer - like RDP, VNC, etc.
> ...
>
> Best,
> Matthias
next prev parent reply other threads:[~2020-11-15 14:45 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 [this message]
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=98A8702B-307A-42B3-B10E-9B0D028E4C07@ipfire.org \
--to=michael.tremer@ipfire.org \
--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