All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Basic IPTables / firewall help?
Date: Wed, 20 Feb 2008 18:45:51 -0600	[thread overview]
Message-ID: <47BCC9BF.9050509@riverviewtech.net> (raw)
In-Reply-To: <47BCA565.3000309@libertytrek.org>

On 02/20/08 16:10, Simon Jester wrote:
> Is there a list somewhere that is more for newbies where I can ask dumb 
> questions and not feel like I just stepped off a bus at Times Square 
> with no clothes on?

I don't know if there is another list elsewhere or not.  I'm sure there 
are lists but I would have no idea where to look other than Google or 
distribution support pages.

> Really - IPTables rules mystify me. What I need is some help translating 
> plain english (ie, I want to block everything except x, y and z) to the 
> appropriate IPTables command/rule. This list appears to be far too 
> technical for my needs...

IPTables is not that bad.  The thing that you really need is an 
understanding of what you are working with (and trying to filter).  The 
next thing you need is an understanding of how identify what you are 
trying to filter and then decide what to do with it.  Third, you need to 
understand the different ways that you can arrange things in an if match 
accept / drop / jump type logic structure.  (How to translate individual 
packet matching rules in to the """Business Logic""" of IPTables 
firewall rules.)

To sort of answer what you want, you could do something like this:

If <packet(s)> match "x" do "this"
If <packet(s)> match "y" do "that"
If <packet(s)> match "z" do "something"

"this", "that", and "something" can be the same or different actions. 
If you are happy with the simple match(s) you can decide to ACCEPT or 
DROP the packet(s) then and there.  If you need to run other tests on 
just packets you can jump to a different chain where you start your 
different set of matches against just the packets that matched the first 
set.

> Tia for any pointers or suggestions...

*nod*

I guess you can ask away with your questions.  Or if you want to talk 
off list, email me directly.



Grant. . . .

  reply	other threads:[~2008-02-21  0:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 22:10 Basic IPTables / firewall help? Simon Jester
2008-02-21  0:45 ` Grant Taylor [this message]
2008-02-21  6:19   ` Rob Sterenborg
2008-02-22 14:19     ` Simon Jester
2008-02-22 14:22   ` Simon Jester
2008-02-21  3:53 ` terry white

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=47BCC9BF.9050509@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=netfilter@vger.kernel.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.