From: "Daniel Weismüller" <daniel.weismueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.27 - Core Update 160 released
Date: Wed, 06 Oct 2021 10:04:09 +0000 [thread overview]
Message-ID: <7605f0da8a920d67a569c9821d0a7c44@ipfire.org> (raw)
In-Reply-To: <d169494e-e95a-a8af-90bc-fd4b073515df@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2236 bytes --]
Hello
I have also had a look at this.
There are now two Wiki pages on this topic.
- A general one (https://wiki.ipfire.org/configuration/firewall/rules/redirect-services).
- A very specific one for DNS redirect (https://wiki.ipfire.org/configuration/firewall/dns).
Since core160 the general method works. This is equivalent to the method 1 described on the specific page.
Following the general instructions, I have created a few firewall rules to redirect DNS, DoT and NTP.
This works very well now.
In general, I think that general instructions are always better than specific step-by-step instructions.
In my eyes, the described method 2, which had to be taken as a temporary solution, is therefore obsolete. In addition, pure blocking can lead to some devices no longer working.
Do you see it the same way?
-
Daniel
5. Oktober 2021 22:10, "Bernhard Bitsch" <bbitsch(a)ipfire.org> schrieb:
> Hi all,
>
> Thanks.
> So it was only a misunderstanding. I thought, there would be options to redirect DNS requests and
> NTP requests.
> But this 'any port solution' is much mightier.
> I'll try to convert my actual firewall.local solution to the main stream and report about the
> results.
>
> Regards,
> Bernhard
>
> Am 05.10.2021 um 18:28 schrieb Michael Tremer:
>
>> Hello,
>> Simply using -j REDIRECT.
>> This was always part of the firewall engine, but the UI was broken and did not allow to create
>> these rules.
>> -Michael
>> On 5 Oct 2021, at 14:55, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
>>> Just a question. How is the activation of redirection implemented?
>>>
>>> Am 05.10.2021 um 12:45 schrieb IPFire Project:
>>
>> IPFire Logo
>> there is a new post from Michael Tremer on the IPFire Blog:
>> *IPFire 2.27 - Core Update 160 released*
>> This is the release announcement for IPFire 2.27 - Core Update 160.
>> It comes with a large number of bug fixes and package updates and
>> prepare for removing Python 2 which has reached its end of life.
>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-160-released>
>> The IPFire Project
>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
next prev parent reply other threads:[~2021-10-06 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <163343070641.5808.3538548201555802254.ipfire@ipfire.org>
2021-10-05 13:55 ` Bernhard Bitsch
2021-10-05 16:28 ` Michael Tremer
2021-10-05 20:10 ` Bernhard Bitsch
2021-10-06 10:04 ` Daniel Weismüller [this message]
2021-10-06 12:12 ` Bernhard Bitsch
2021-10-06 13:22 ` Daniel Weismüller
2021-10-06 13:49 ` Bernhard Bitsch
2021-10-09 12:41 ` Michael Tremer
[not found] <C50F4F4D-4BC3-4FD7-A628-B70765C416B9@gmail.com>
2021-10-09 12:42 ` Michael Tremer
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=7605f0da8a920d67a569c9821d0a7c44@ipfire.org \
--to=daniel.weismueller@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