public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Web Site blocked as hostile. Not sure if this is correct or not
Date: Tue, 15 Aug 2023 15:37:31 +0200	[thread overview]
Message-ID: <2a4342e8-257b-4f3f-8ff0-c05031165f61@ipfire.org> (raw)

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

Hi Peter,

I am getting a DROP_HOSTILE for a web site, oldlinux.org

Looking in libloc it shows up as hostile

location lookup 107.148.241.134
107.148.241.134:
   Network                 : 107.148.0.0/15
   Country                 : United States of America
   Autonomous System       : AS54600 - PEGTECHINC
   Hostile Network safe to drop: yes

However in spamhaus it says that oldlinux.org and 107.148.241.134 have 
no issues.

I ran a couple of blacklist checkers on the ip.
blacklistchecker.com came back with a pass on everything.
dnschecker.org came back with a pass on everything except from 
dnsbl.spfbl.net who have it flagged because it doesn't have an rDNS

With the problems we are having currently with selective announcements 
of networks, I wasn't sure if this problem I have encountered is coming 
from the libloc database or is a real problem.

oldlinux is hosted on the network from Peg Tech Inc hosting so maybe 
they are a hoster of hostile networks but I don't know how to confirm this.

I wasn't sure about raising a new bug on this, or adding it to 
bug#13236, in case it was a real hostile network and should be blocked.


Hoping you can help me with this.

Regards,

Adolf.

-- 

Sent from my laptop


             reply	other threads:[~2023-08-15 13:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 13:37 Adolf Belka [this message]
2023-08-15 14:32 ` Adolf Belka
2023-08-15 15:51   ` Peter Müller
2023-08-15 16:39     ` Adolf Belka

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=2a4342e8-257b-4f3f-8ff0-c05031165f61@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@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