From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Adding Gold Zone to IPFire
Date: Wed, 05 Mar 2025 11:48:41 +0000 [thread overview]
Message-ID: <FA4AB4FF-998C-43DF-9664-1EE71D249297@ipfire.org> (raw)
In-Reply-To: <CANoCWNKeSK5W69bdHUsCQ9csBk5wBHtQBpB6aO8HuZhFk_4Vqw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
Hello Mike,
Thank you for your suggestion.
This has been brought forward a couple of times in the past, but as it stands, the networking code is way too complicated to add more zones. It has not been written to be easily extended and therefore adding another zone would be a lot of pain.
There is literally no sense in adding another zone that does not have any of the other features, like 100% firewall support, DHCP, proxy, and what else there is. We should not add second-class zones. Instead we should look at rewriting all networking and then build on top of that.
Best,
-Michael
> On 2 Mar 2025, at 18:22, fairmont <mikejohnhouse(a)gmail.com> wrote:
>
> Hello, I would like to add another zone to ipfire called the gold zone.
> The name for the network would be Devices.
> The default behaviour would be to deny all zones. No dhcp.
parent reply other threads:[~2025-03-05 11:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CANoCWNKeSK5W69bdHUsCQ9csBk5wBHtQBpB6aO8HuZhFk_4Vqw@mail.gmail.com>]
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=FA4AB4FF-998C-43DF-9664-1EE71D249297@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