Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: IPs blocked still able to connect
Date: Sat, 12 Jun 2004 21:38:44 +0100	[thread overview]
Message-ID: <200406122138.45223.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <200406122017.i5CKHpnI030899@ylpvm01.prodigy.net>

On Saturday 12 June 2004 9:18 pm, Spiro Azkoul wrote:

> Hello
>
> I blocked a subnet by using the following command:
> iptables -A INPUT -s 222.0.0.0/8 -j DROP
> I then saved it to file
> iptables-save > /etc/sysconfig/iptables
> and did an iptables -L INPUT to verify that it is in
> DROP       all  --  222.0.0.0/8          anywhere
>
> However, i am still receiving SPAM from IPs within that subnet (and others)
> long after I thought I completely blocked them from connecting to my
> server.

Can you show us the headers of such an email, showing that the server which 
directly sent it to you is in that address range?

Try adding a LOG rule immediately after the above DROP rule:

iptables -A INPUT -s 222.0.0.0/8 -j LOG

After you get some more spam, try "iptables -L INPUT -nvx" and see what the 
packet & byte counts are for the two rules.

What are your other rules (output of "iptables -L -nvx")?

Regards,

Antony.

-- 
Wanted: telepath.   You know where to apply.

                                                     Please reply to the list;
                                                           please don't CC me.



  reply	other threads:[~2004-06-12 20:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-12 20:18 IPs blocked still able to connect Spiro Azkoul
2004-06-12 20:38 ` Antony Stone [this message]
2004-06-12 20:46   ` Spiro Azkoul
2004-06-13 19:22 ` Michael Gale
2004-06-13 19:36   ` Spiro Azkoul
2004-06-13 19:58     ` Michael Gale
2004-06-13 23:59       ` Spiro Azkoul
2004-06-14  1:02         ` Alexis
2004-06-14  8:54       ` Spiro Azkoul
2004-06-14 15:32         ` Michael Gale

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=200406122138.45223.Antony@Soft-Solutions.co.uk \
    --to=antony@soft-solutions.co.uk \
    --cc=netfilter@lists.netfilter.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