public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <24dfb438-6ff2-9e4f-a51b-d19cc7f1a288@gmail.com> (raw)
In-Reply-To: <6dfd8ae4-2a76-b713-0610-91ca314358b9@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

Peter Müller wrote:

>> This flag 'LOC_NETWORK_FLAG_BOGON' does not exist (yet).
>> Would it be possible?
> 
> 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 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.

> Thanks, and best regards,
> Peter Müller

Thanks for your answer.


-- 
--gv

  reply	other threads:[~2021-10-23 11:40 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 [this message]
2021-10-23 15:55     ` 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=24dfb438-6ff2-9e4f-a51b-d19cc7f1a288@gmail.com \
    --to=gisle.vanem@gmail.com \
    --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