From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: tool to search within cidr blocks
Date: Wed, 22 Oct 2008 18:07:31 -0500 [thread overview]
Message-ID: <48FFB233.1070706@riverviewtech.net> (raw)
In-Reply-To: <004301c9347c$6ab0a3c0$4011eb40$@net>
On 10/22/2008 2:28 PM, Joey wrote:
> I have several ranges of IP’s being put into iptables.
> The IP ranges look like this:
> 62.29.0.0/17
> 62.68.192.0/19
> 62.108.64.0/19
> 62.244.192.0/18
> 62.248.0.0/17
> 77.67.128.0/17
> 77.72.184.0/21
> 77.73.216.0/21
> 77.75.32.0/21
> 77.75.216.0/21
> 77.79.64.0/18
> 77.92.0.0/19
> 77.92.96.0/19
> 77.92.128.0/19
> 77.223.128.0/19
> 77.245.144.0/20
> 78.40.224.0/21
> 78.111.96.0/20
> 78.135.0.0/17
>
> I am blocking a specific IP from the firewall as logged in messages
> 71.74.56.125.
> In looking at each block of ip’s and using a CIDR calculator I can’t figure
> out what range it’s really coming from. The list I have is pretty huge.
> Is there a tool or a way to ask iptables what rule it matches? Based on all
> my calculations I don’t have anything declared that would block that IP.
>
> Thanks!
Um, 71.74.56.125 is not part of any of the Class A ranges that you are
blocking (62., 77., 78.). So... that sort of implies that something
else is blocking it.
Do you care to provide the (sanitized) output of an 'iptables-save' for
us to look at?
Grant. . . .
next prev parent reply other threads:[~2008-10-22 23:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Ack0fGqkMfM1syJxRQCXdIAkNZSCIQ==>
2008-10-22 19:28 ` tool to search within cidr blocks Joey
2008-10-22 19:28 ` Matt Zagrabelny
2008-10-22 22:40 ` Joey
2008-10-22 23:07 ` Grant Taylor [this message]
2008-10-23 20:51 ` Joey
2008-10-23 20:58 ` Eljas Alakulppi
2008-10-24 0:38 ` Joey
2008-10-24 3:01 ` Grant Taylor
2008-10-24 4:14 ` Joey
2008-10-24 5:01 ` Grant Taylor
2008-10-24 22:24 ` Joey
2008-10-26 19:08 ` Grant Taylor
2008-10-26 21:13 ` Elvir Kuric
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=48FFB233.1070706@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@vger.kernel.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