All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike <1100100@gmail.com>
To: Alistair Tonner <alistair@nerdnet.ca>
Cc: netfilter@lists.netfilter.org
Subject: Re: Policy Misunderstanding: RTFM Guidance Requested.
Date: Wed, 1 Sep 2004 14:12:56 -0400	[thread overview]
Message-ID: <8ca4228204090111127401567b@mail.gmail.com> (raw)
In-Reply-To: <200409011253.52931.Alistair@nerdnet.ca>

> Better to let things through the mangle and nat tables, and do filtering in
> the filter table.  There have been folks who like to drop things in the
> mangle and nat tables, but setting actual DROP policies makes life very
> difficult.

This seems like sound advice after what I've been through.  Maybe the
folks in The Matrix can bend the laws of physics with relative ease,
but for myself, I can barely achieve 'dude' status.  I think I'll
ACCEPT mangle and nat, and get some sleep tonight.  :-)

>         There is no definition of the SOURCE that you want to drop ICMP echorequests
> from.  Thus this rule drops all ping echorequests.
>         iptables -t filter -A INPUT -p icmp -i [internet pipe device] -icmp-type \
> echo-request -j DROP
>         will allow your LAN users to ping the box, but prevent pings from the
> internet from getting in.

Oh I see.  By stating specifically the internet-facing device, you
make it possible for LAN clients to ping the box through the gateway
NIC - eth1, while the rule blocks all the other echo requests.

>         Really and truely -- Oskar's tutorials are great and easy to read... and even
> the sample firewalls there are decent enough to start with for a newbie.
> 
I definitely feel more secure about working on my firewall knowing
that this reference material is around.  It's packed.

Thanks again, Alistair.
It's great to have your assistance.

Mike


  reply	other threads:[~2004-09-01 18:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-01  1:01 Mail Server Behind IPTABLES Ajen Diwakar
2004-09-01  4:22 ` George Alexandru Dragoi
2004-09-01 11:54   ` Policy Misunderstanding: RTFM Guidance Requested Mike
2004-09-01 13:27     ` Deepak Seshadri
2004-09-01 15:46       ` Mike
2004-09-01 16:50         ` Jason Opperisano
2004-09-01 17:53           ` Mike
2004-09-01 17:38         ` Deepak Seshadri
2004-09-01 16:40       ` Mike
2004-09-01 14:44     ` Alistair Tonner
2004-09-01 16:20       ` Mike
2004-09-01 16:53         ` Alistair Tonner
2004-09-01 18:12           ` Mike [this message]
2004-09-01 16:43     ` Jason Opperisano
2004-09-01 14:50 ` Mail Server Behind IPTABLES Alistair Tonner
     [not found]   ` <1094054540.5456.16.camel@matevz.net>
2004-09-01 16:27     ` Alistair Tonner
2004-09-01 18:12       ` Matevz
2004-09-01 18:19         ` Jason Opperisano
2004-09-01 18:25           ` Jason Opperisano
2004-09-01 18:23         ` Alistair Tonner

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=8ca4228204090111127401567b@mail.gmail.com \
    --to=1100100@gmail.com \
    --cc=alistair@nerdnet.ca \
    --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 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.