From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] firewall.cgi: Allow to creating input rules from Orange to another zone.
Date: Sat, 17 Jul 2021 13:14:34 +0100 [thread overview]
Message-ID: <80F46D94-0E82-49D6-B7C8-2ECD2B9D889A@ipfire.org> (raw)
In-Reply-To: <20210716163558.3779-1-stefan.schantl@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 16 Jul 2021, at 17:35, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
>
> It was not able to create a firewall rule from the orange network to a
> different network address of the firewall. ( For example: Orange -> IPFire's green address)
>
> These rules always have been handled as FORWARD rules which is totaly
> wrong.
>
> Fixes #12265.
>
> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> Tested-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> html/cgi-bin/firewall.cgi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/html/cgi-bin/firewall.cgi b/html/cgi-bin/firewall.cgi
> index 70dee8d3c..e50a98179 100644
> --- a/html/cgi-bin/firewall.cgi
> +++ b/html/cgi-bin/firewall.cgi
> @@ -247,7 +247,7 @@ if ($fwdfwsettings{'ACTION'} eq 'saverule')
> $errormessage=$Lang::tr{'fwdfw err same'};
> }
> # INPUT part
> - if ($fwdfwsettings{'grp2'} eq 'ipfire' && $fwdfwsettings{$fwdfwsettings{'grp1'}} ne 'ORANGE'){
> + if ($fwdfwsettings{'grp2'} eq 'ipfire') {
> $fwdfwsettings{'config'}=$configinput;
> $fwdfwsettings{'chain'} = 'INPUTFW';
> $maxkey=&General::findhasharraykey(\%configinputfw);
> --
> 2.30.2
>
prev parent reply other threads:[~2021-07-17 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 16:35 Stefan Schantl
2021-07-17 12:14 ` Michael Tremer [this message]
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=80F46D94-0E82-49D6-B7C8-2ECD2B9D889A@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