From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gisle Vanem <gisle.vanem@gmail.com>
To: location@lists.ipfire.org
Subject: Re: Checking for Bogons
Date: Sat, 23 Oct 2021 13:40:46 +0200
Message-ID: <24dfb438-6ff2-9e4f-a51b-d19cc7f1a288@gmail.com>
In-Reply-To: <6dfd8ae4-2a76-b713-0610-91ca314358b9@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1471574831554328335=="
List-Id: <location.lists.ipfire.org>

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

Peter M=C3=BCller wrote:

>> This flag 'LOC_NETWORK_FLAG_BOGON' does not exist (yet).
>> Would it be possible?
>=20
> In theory, yes, but there is no need for another flag: If there is
> is no announcement for a network, it is considered to be a bogon.

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

> So, all you need to do is to check if loc_database_lookup() gives
> you an ASN for the queried IP address. :-)

So no ASN result, means a "Bogon"?
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 Prov=
ince

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.

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

Thanks for your answer.


--=20
--gv

--===============1471574831554328335==--