From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernhard Bitsch To: development@lists.ipfire.org Subject: Re: IPFire 2.27 - Core Update 160 released Date: Tue, 05 Oct 2021 22:10:08 +0200 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6451644800978707214==" List-Id: --===============6451644800978707214== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi all, Thanks. So it was only a misunderstanding. I thought, there would be options to=20 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=20 and report about the results. Regards, Bernhard Am 05.10.2021 um 18:28 schrieb Michael Tremer: > Hello, >=20 > Simply using -j REDIRECT. >=20 > This was always part of the firewall engine, but the UI was broken and did = not allow to create these rules. >=20 > -Michael >=20 >> On 5 Oct 2021, at 14:55, Bernhard Bitsch 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 >>> The IPFire Project >>> Don't like these emails? Unsubscribe . >=20 --===============6451644800978707214==--