From: Tom Rymes <tom@rymes.net>
To: development@lists.ipfire.org
Subject: Re: [PATCH] location-functions.pl: Recognise XD / LOC_NETWORK_FLAG_DROP
Date: Thu, 14 Oct 2021 15:08:56 -0400 [thread overview]
Message-ID: <867B5E27-DD53-42D1-BE4C-E6D21E6A0DA8@rymes.net> (raw)
In-Reply-To: <2AA9AF20-B04A-4D64-82B2-ADF8ED39408F@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
> On Oct 14, 2021, at 2:28 PM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>
> Hello,
>
>> On 13 Oct 2021, at 17:21, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>
[ snip]
>> Yes. My imagination of bug #12031 is to have three new checkboxes on the firewall options CGI
>> to drop all traffic from and to
>> (a) IP networks not being globally routable ("martians")
[snip]
>> (a) is something we (I) can implement straight away. As soon as this patch has been merged,
>
>
> (a) will need a lot of exceptions:
>
> * Networks that are locally connected (GREEN, BLUE, ORANGE, RED)
> * All VPNs (OpenVPN, IPsec, H2N and N2N)
> * All static routes
> * Maybe some SNAT/DNAT rules?
>
> These will have to be auto-generated and not bother the admins.
>
> Maybe it would be better to solve this in another way than using iptables.
[snip]
Is “carrier-grade NAT” no longer a thing?
Also, users behind a NAT router/modem/whatever will run into issues, though that’s maybe handled by excluding Locally connected networks as mentioned above?
Tom
next prev parent reply other threads:[~2021-10-14 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 17:13 Peter Müller
2021-10-12 11:30 ` Michael Tremer
2021-10-13 16:21 ` Peter Müller
2021-10-14 18:28 ` Michael Tremer
2021-10-14 19:08 ` Tom Rymes [this message]
2021-10-14 19:26 ` Michael Tremer
2021-10-15 9:16 ` Peter Müller
2021-10-15 14:49 ` 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=867B5E27-DD53-42D1-BE4C-E6D21E6A0DA8@rymes.net \
--to=tom@rymes.net \
--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