All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Klemen Kecman" <klemen@sting.si>
To: netfilter@lists.netfilter.org
Cc: Ben <nigma@nigma.info>
Subject: Re: Trouble rejecting connections
Date: Thu, 29 Jan 2004 10:00:03 +0100	[thread overview]
Message-ID: <006101c3e646$49e8f950$6a02a8c0@klemen> (raw)
In-Reply-To: E1AlxPY-00033X-P8@aphex.cyberpixels.com

Still I think your problem will go away if you move LOG target above "# Open
ports for server/services"

Klemen Kecman
Sting d.o.o.
Computer I.T.

Slackware user till the grave!

----- Original Message -----
From: "Ben" <nigma@nigma.info>
To: <netfilter@lists.netfilter.org>
Sent: Wednesday, January 28, 2004 10:39 PM
Subject: RE: Trouble rejecting connections


> Perhaps I explained incorrectly.  I want to be able to specifically deny
an
> IP address all access to the server at all.  I'm doing this with a line
that
> looks something like this
>
> $IPTABLES -A INPUT -s blocked.ip.address.here -j DROP
>
> However, when I do that, I am able to still connect from from
> blocked.ip.address.here.  That's the main thing I am concerned with.
>
> Otherwise, my logging and lo lines work, so I'm going to stick with
leaving
> well enough alone.
>
> Thanks for your help,
>
> Ben Prince
>
> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org
> [mailto:netfilter-admin@lists.netfilter.org] On Behalf Of Klemen Kecman
> Sent: Wednesday, January 28, 2004 4:49 AM
> To: netfilter@lists.netfilter.org
> Cc: Ben
> Subject: Re: Trouble rejecting connections
>
> Place log target above all rules or create LOG chain.
> Why use double drop?
> If the default policy is set to DROP, there is no need for aditional drop
> rules.
> Allso fix the lo line .. it can be writen much simpler like $IPT -A
INPUT -p
> ALL -i $IF_LO -j ACCEPT $IPT -A OUTPUT -p ALL -o $IF_LO -j ACCEPT
>
> ----- Original Message -----
> From: "Ben" <nigma@nigma.info>
> To: <netfilter@lists.netfilter.org>
> Sent: Wednesday, January 28, 2004 10:19 AM
> Subject: Trouble rejecting connections
>
>
> > Hello all,
> >
> > I'm having trouble rejecting connections using iptables.  I am using
> cPanel
> > / WHM on a RedHat 7.3 a machine and iptables installed from
> > iptables-1.2.8-8.72.3.i386.rpm .  I am using a script for my policy,
> > it looks like this.
> >
> >
> > //Start script
> > IPTABLES="/sbin/iptables"
> >
> > #Flush everything, start from scratch
> > $IPTABLES -F
> >
> > #Set default policies to DROP
> > $IPTABLES -P INPUT DROP
> > $IPTABLES -P FORWARD DROP
> >
> > #Allow all lo traffic
> > $IPTABLES -A INPUT -i lo -s 0.0.0.0/0 -d 0.0.0.0/0 -j ACCEPT
> >
> > #Allow all related and established connections $IPTABLES -A INPUT -m
> > state --state RELATED,ESTABLISHED -j ACCEPT
> >
> > #Set default OUTPUT policy to ACCEPT
> > $IPTABLES -P OUTPUT ACCEPT
> >
> > # Open ports for server/services
> > $IPTABLES -A INPUT -p tcp --dport 20 -j ACCEPT $IPTABLES -A INPUT -p
> > tcp --dport 21 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 22 -j
> > ACCEPT $IPTABLES -A INPUT -p tcp --dport 25 -j ACCEPT $IPTABLES -A
> > INPUT -p tcp --dport 37 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 43
> > -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 53 -j ACCEPT $IPTABLES -A
> > INPUT -p udp --dport 53 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 80
> > -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 110 -j ACCEPT $IPTABLES -A
> > INPUT -p tcp --dport 113 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport
> > 143 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 443 -j ACCEPT
> > $IPTABLES -A INPUT -p tcp --dport 465 -j ACCEPT $IPTABLES -A INPUT -p
> > udp --dport 465 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 873 -j
> > ACCEPT $IPTABLES -A INPUT -p udp --dport 873 -j ACCEPT $IPTABLES -A
> > INPUT -p tcp --dport 993 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport
> > 995 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 2082 -j ACCEPT
> > $IPTABLES -A INPUT -p tcp --dport 2083 -j ACCEPT $IPTABLES -A INPUT -p
> > tcp --dport 2086 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 2087 -j
> > ACCEPT $IPTABLES -A INPUT -p tcp --dport 2089 -j ACCEPT $IPTABLES -A
> > INPUT -p tcp --dport 2095 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport
> > 3306 -j ACCEPT $IPTABLES -A INPUT -p tcp --dport 6666 -j ACCEPT
> >
> > #Enable Blogger support (non-standards compliant piece of dogshit that
> > it
> > is)
> > $IPTABLES -A INPUT -s 66.102.15.83 -j ACCEPT $IPTABLES -A INPUT -s
> > 216.34.7.186 -j ACCEPT
> >
> > #Add passive-mode people here
> > #$IPTABLES -A INPUT -s xxx.xxx.xxx.xxx -j ACCEPT
> >
> > #Add DENY people here
> > #$IPTABLES -A INPUT -s 000.000.000.000 -j DROP $IPTABLES -A INPUT -s
> > blocked.ip.address.here -j DROP
> >
> > #Logging
> > $IPTABLES -A INPUT -j LOG --log-prefix "INPUTDEFAULT: "
> >
> > #Save rules
> > iptables-save > /etc/sysconfig/iptables
> >
> > #Restart for rules to take effect
> > service iptables restart
> > //End script
> >
> > The problem is that I can still connect from blocked.ip.address.here.
> What
> > did I miss?
> >
> > Ben Prince
> > Cyber Pixels
> > Systems Administrator
> > ben@cyberpixels.com
> >
> >
>
>
>
>
>



  reply	other threads:[~2004-01-29  9:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28  9:19 Trouble rejecting connections Ben
2004-01-28  9:48 ` Klemen Kecman
2004-01-28 21:39   ` Ben
2004-01-29  9:00     ` Klemen Kecman [this message]
2004-01-28 13:21 ` Jeffrey Laramie
2004-01-28 21:50   ` Ben
2004-01-29 13:55     ` Jeffrey Laramie

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='006101c3e646$49e8f950$6a02a8c0@klemen' \
    --to=klemen@sting.si \
    --cc=netfilter@lists.netfilter.org \
    --cc=nigma@nigma.info \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.