From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: Checking for Bogons
Date: Sat, 23 Oct 2021 17:55:48 +0200
Message-ID: <1b624632-f20d-68eb-fc3c-22b822dd7634@ipfire.org>
In-Reply-To: <24dfb438-6ff2-9e4f-a51b-d19cc7f1a288@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0242783802712101857=="
List-Id: <location.lists.ipfire.org>

--===============0242783802712101857==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Gisle,

thanks for your reply.

> What do you mean by "no announcement for a network" exactly?
> (kind of an alien term to me).=20

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 Coordinat=
ion Centre (RIPE NCC)        <<<<<

> So no ASN result, means a "Bogon"?=20

Yes.

> A command like:
>   location.py list-bogons --family ipv4
>=20
> 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 Pro=
vince
>=20
> Doesn't look like a "Bogon" to me.
>=20
> And trying a 'nmap -sA -p80 1.236.0.0/24', gave me 11 hosts up.
> Seems no router cares about Bogons.=20

Indeed, looks like this does not work properly. Bug #12712
(https://bugzilla.ipfire.org/show_bug.cgi?id=3D12712) has been raised for thi=
s.

Sorry to disappoint.

Thanks, and best regards,
Peter M=C3=BCller

--===============0242783802712101857==--