From: Michael Gale <michael.gale@utilitran.com>
To: netfilter@lists.netfilter.org
Subject: Re: IPs blocked still able to connect
Date: Mon, 14 Jun 2004 09:32:14 -0600 [thread overview]
Message-ID: <20040614093214.4e35cf16@mgalepc.utilitran.com> (raw)
In-Reply-To: <200406140853.i5E8rsqE031321@ylpvm43.prodigy.net>
Hello,
I did not mean you should be using -I for all your inserts .... when you load
you rules from a script ... a "-A" will work fine. But when adding a rules on
the fly later .. you most likely want to do a "-I" so it is at the top of the
list.
Example:
From script:
iptables -A INPUT -i eth0 -p tcp --dport 25 -j ACCEPT
iptables -A INPUT -i eth0 -j DROP
Now you find that you want to block spam from mai.hotmail.com (1.1.1.1)
Doing this:
iptables -A INPUT -i eth0 -s 1.1.1.1 -p tcp --dport 25 -j DROP
Would cause the following to happen:
INPUT -i eth0 -p tcp --dport 25 -j ACCEPT
INPUT -i eth0 -j DROP
INPUT -i eth0 -s 1.1.1.1 -p tcp --dport 25 -j DROP
This has the port 25 ACCEPT happening before the DROP rule for 1.1.1.1 ... so it
would be accepted.
If you run:
iptables -I INPUT -i eth0 -s 1.1.1.1 -p tcp --dport 25 -j DROP
Then you would of had:
INPUT -i eth0 -s 1.1.1.1 -p tcp --dport 25 -j DROP
INPUT -i eth0 -p tcp --dport 25 -j ACCEPT
INPUT -i eth0 -j DROP
As you can see the DROP for 1.1.1.1 comes first .. so SMTP from 1.1.1.1 would be
dropped before the ACCEPT ... blocking SMTP from 1.1.1.1
Michael.
On Mon, 14 Jun 2004 01:54:19 -0700
"Spiro Azkoul" <spiro@snacorp.net> wrote:
> By doing the -I transition no one could connect to my server anymore.
>
> Knowing that I had a bunch of rules such as
>
> [root@linux root]# iptables -L INPUT
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
> DROP all -- YahooBB219000000000.bbtec.net/8 anywhere
> DROP all -- AAnnecy-204-1-27-120.w81-249.abo.wanadoo.fr anywhere
>
> DROP all -- 61.178.0.0/16 anywhere
> DROP all -- 53-bem-10.acn.waw.pl anywhere
> DROP all -- 216.155.64.0/19 anywhere
> RH-Lokkit-0-50-INPUT all -- anywhere anywhere
> ACCEPT tcp -- anywhere anywhere tcp dpt:ssh
> ACCEPT tcp -- anywhere anywhere tcp dpt:http
> ACCEPT tcp -- anywhere anywhere tcp dpt:smtp
> ACCEPT tcp -- anywhere anywhere tcp dpt:pop3
>
> That did not work
> No one could connect for POP or SMTP.
> What is wrong with that config?
> Thanks
>
>
>
>
>
>
>
--
Michael Gale
Network Administrator
Utilitran Corporation
prev parent reply other threads:[~2004-06-14 15:32 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
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 [this message]
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=20040614093214.4e35cf16@mgalepc.utilitran.com \
--to=michael.gale@utilitran.com \
--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