From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: [PATCH] Add overrides for RFC1918
Date: Thu, 15 Oct 2020 16:29:27 +0100 [thread overview]
Message-ID: <DE443188-1AF6-47FA-ADA6-473E96521CDA@ipfire.org> (raw)
In-Reply-To: <20201015152712.12822-1-michael.tremer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]
I just pushed this as a hot fix because we are currently taking down a couple of networks for our users.
Please refer to
https://bugzilla.ipfire.org/show_bug.cgi?id=12499
and
https://bugzilla.ipfire.org/show_bug.cgi?id=12501
Best,
-Michael
> On 15 Oct 2020, at 16:27, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>
> Because of RIPE (or somebody else) adding 192.168.0.0/15, we are
> classifying those addresses as EU. This renders whole networks
> inaccessible and therefore we are adding those networks with a
> faked country until we find a better solution.
>
> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
> ---
> overrides/override-rfc1918.txt | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
> create mode 100644 overrides/override-rfc1918.txt
>
> diff --git a/overrides/override-rfc1918.txt b/overrides/override-rfc1918.txt
> new file mode 100644
> index 0000000..768ea92
> --- /dev/null
> +++ b/overrides/override-rfc1918.txt
> @@ -0,0 +1,18 @@
> +#
> +# override-rfc1918 [.txt]
> +#
> +# This files contains networks from RFC1918 (and other similar standards)
> +# which are added to the database with special attributes
> +#
> +
> +net: 10.0.0.0/8
> +descr: Private address space from RFC1918
> +country: XX
> +
> +net: 172.16.0.0/12
> +descr: Private address space from RFC1918
> +country: XX
> +
> +net: 192.168.0.0/16
> +descr: Private address space from RFC1918
> +country: XX
> --
> 2.20.1
>
prev parent reply other threads:[~2020-10-15 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 15:27 Michael Tremer
2020-10-15 15:29 ` 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=DE443188-1AF6-47FA-ADA6-473E96521CDA@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=location@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