public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Rainer Kemme <news@panamail.de>
To: development@lists.ipfire.org
Subject: Re: Forcing all DNS traffic from the LAN to the firewall
Date: Wed, 11 Nov 2020 16:02:43 +0100	[thread overview]
Message-ID: <a26409a7-65c5-8172-da07-ea066d482e65@panamail.de> (raw)
In-Reply-To: <893404c4-16eb-2055-5702-7a3b44377443@ipfire.org>

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

Hello,

Am 09.11.2020 um 18:47 schrieb Matthias Fischer:
> 
> "...I am trying to redirect all of my DNS traffic to go thru the
> IPFire DNS instead of directly to an outside DNS server...".
Before I replaced the old ZyXEL ZyWALL 35 by IPFire I intercepted / 
Redirected UDP 53 (DNS) and UDP 123 (NTP) using the ZyWALLs so called 
policy routing:

Based on the policy I redirected UDP 53,123 to one of my Linux machines.

On the Linux maschine I defined IPTABLE rules in order to redirect the 
requests to my favorite (internal) DNS-Server.

A rule for the request:
   iptables -t nat
            -A PREROUTING
            -p udp
            -s 172.22.100.0/22
          ! -d 172.22.0.0/16
           --dport 53
            -j DNAT
          --to 172.22.10.181

A rule for the reply:
   iptables -t nat
            -A POSTROUTING
            -p udp
            -s 172.22.100.0/22
            -d 172.22.10.181
           --dport 53
            -j SNAT
           --to 172.22.10.179

My LAN:
   172.22.0.0/16
The requesting range:
   172.22.100.0/22
The Linux machine
   172.22.10.179
My DNS-Server
   172.22.10.181

So, what I would appreciate in IPFire is a policy based routing :-)

Regards,
   Rainer

  parent reply	other threads:[~2020-11-11 15:02 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 [this message]
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
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=a26409a7-65c5-8172-da07-ea066d482e65@panamail.de \
    --to=news@panamail.de \
    --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