From: "Peter Müller" <peter.mueller@ipfire.org>
To: location@lists.ipfire.org
Subject: [PATCH 1/2] override-other: Fix netcup IP ranges actually located in AT
Date: Sat, 05 Feb 2022 17:17:57 +0000 [thread overview]
Message-ID: <c8dc1ed3-fdf3-eee1-92a5-f2e0e68bac13@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
See: https://lists.ipfire.org/pipermail/location/2022-January/000519.html
Reported-by: Martin Gebhardt <martin.gebhardt(a)linkspartei.org>
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
overrides/override-other.txt | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/overrides/override-other.txt b/overrides/override-other.txt
index b74c1e3..01cd324 100644
--- a/overrides/override-other.txt
+++ b/overrides/override-other.txt
@@ -1518,6 +1518,11 @@ descr: Amarutu Technology Ltd. / KoDDoS / ESecurity
remarks: fake offshore location (BZ), traces back to US
country: US
+net: 89.58.16.0/22
+descr: netcup GmbH
+remarks: https://lists.ipfire.org/pipermail/location/2022-January/000519.html
+country: AT
+
net: 91.90.120.0/24
descr: M247 LTD, Greenland Infrastructure
remarks: ... traces back to CA
@@ -1773,6 +1778,11 @@ descr: Securebit AG
remarks: ... who thinks assigning networks to unpopulated Bouvet Island (BV) is funny :-/
country: CH
+net: 2a0a:4cc0::/40
+descr: netcup GmbH
+remarks: https://lists.ipfire.org/pipermail/location/2022-January/000519.html
+country: AT
+
net: 2a0e:b100:3000::/40
descr: 4b42 UG (haftungsbeschränkt)
remarks: ... who thinks assigning networks to unpopulated Bouvet Island (BV) is funny :-/
--
2.34.1
next reply other threads:[~2022-02-05 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 17:17 Peter Müller [this message]
2022-02-05 17:18 ` [PATCH 2/2] override-{a1,a3,other}: Regular batch of various overrides Peter Müller
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=c8dc1ed3-fdf3-eee1-92a5-f2e0e68bac13@ipfire.org \
--to=peter.mueller@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