From: "Peter Müller" <peter.mueller@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: Checking for Bogons
Date: Sat, 23 Oct 2021 17:55:48 +0200 [thread overview]
Message-ID: <1b624632-f20d-68eb-fc3c-22b822dd7634@ipfire.org> (raw)
In-Reply-To: <24dfb438-6ff2-9e4f-a51b-d19cc7f1a288@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
Hello Gisle,
thanks for your reply.
> What do you mean by "no announcement for a network" exactly?
> (kind of an alien term to me).
I meant a BGP announcement, such as this one:
> [root(a)maverick ~]# location lookup 193.0.6.139
> 193.0.6.139:
> Network : 193.0.0.0/21
> Country : Netherlands
> Autonomous System : AS3333 - Reseaux IP Europeens Network Coordination Centre (RIPE NCC) <<<<<
> So no ASN result, means a "Bogon"?
Yes.
> A command like:
> location.py list-bogons --family ipv4
>
> returns for example '1.236.0.0/18'. And
> 'location.py lookup ::ffff:1.236.0.0' returns an ASN:
> Network : 1.236.0.0/24
> Country : Korea, Republic of
> Autonomous System : AS38396 - Paju office of Education Gyeonggi Province
>
> Doesn't look like a "Bogon" to me.
>
> And trying a 'nmap -sA -p80 1.236.0.0/24', gave me 11 hosts up.
> Seems no router cares about Bogons.
Indeed, looks like this does not work properly. Bug #12712
(https://bugzilla.ipfire.org/show_bug.cgi?id=12712) has been raised for this.
Sorry to disappoint.
Thanks, and best regards,
Peter Müller
prev parent reply other threads:[~2021-10-23 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 10:18 Gisle Vanem
2021-10-23 10:40 ` Peter Müller
2021-10-23 11:40 ` Gisle Vanem
2021-10-23 15:55 ` Peter Müller [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=1b624632-f20d-68eb-fc3c-22b822dd7634@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