From: Ralf Spenneberg <lists@spenneberg.org>
To: Juan Hernandez <alucard@kanux.com>
Cc: Lista de netfilter <netfilter@lists.netfilter.org>
Subject: Re: simple questions to finally understand netfilter
Date: 27 Nov 2003 18:49:53 +0100 [thread overview]
Message-ID: <1069955392.28653.96.camel@kermit> (raw)
In-Reply-To: <1069949657.9126.55.camel@webmail.aeropostal.com.ve>
Am Don, 2003-11-27 um 17.14 schrieb Juan Hernandez:
> Another question...
>
> On Thu, 2003-11-27 at 12:04, Ralf Spenneberg wrote:
> > Am Don, 2003-11-27 um 16.41 schrieb Juan Hernandez:
> >
> > > 1) This rule tells netfilter to drop any packet forwarding I guess
> > > iptables -P FORWARD DROP
> > This is a default rule. All packets not accepted or dropped by other
> > rules will be dropped by this one.
>
> If this drops everything else, how come there's access to the webserver
> in that same machine?? It's not that I dont want it, its just that im
> curious on what does this rule drops exactly cause I can still access my
> webserver
Because the FORWARD chain only covers packets to be forwarded to other
machines. Packets destined to the local machine are filtered in the
INPUT chain. Do a
iptables -P INPUT DROP
and you webserver should stop responding (if there are no other INPUT
rules).
Cheers,
Ralf
--
Ralf Spenneberg
RHCE, RHCX
Book: VPN mit Linux
Book: Intrusion Detection für Linux Server http://www.spenneberg.com
IPsec-Howto http://www.ipsec-howto.org
Honeynet Project Mirror: http://honeynet.spenneberg.org
next prev parent reply other threads:[~2003-11-27 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 15:41 simple questions to finally understand netfilter Juan Hernandez
2003-11-27 16:04 ` Ralf Spenneberg
2003-11-27 16:08 ` Juan Hernandez
2003-11-27 16:14 ` Juan Hernandez
2003-11-27 10:33 ` Jamie Pratt
2003-11-27 17:17 ` Jeffrey Laramie
2003-11-27 17:49 ` Ralf Spenneberg [this message]
2003-11-27 17:53 ` Juan Hernandez
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=1069955392.28653.96.camel@kermit \
--to=lists@spenneberg.org \
--cc=alucard@kanux.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