All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike <1100100@gmail.com>
To: Deepak Seshadri <dseshadri@broadbandmaritime.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Policy Misunderstanding: RTFM Guidance Requested.
Date: Wed, 1 Sep 2004 11:46:02 -0400	[thread overview]
Message-ID: <8ca4228204090108466549b5f3@mail.gmail.com> (raw)
In-Reply-To: <200409011323.i81DNQAi040521@jkcpub.iserver.net>

Hi Deepak,

Thank you for your response.

On Wed, 1 Sep 2004 09:27:22 -0400, Deepak Seshadri
<dseshadri@broadbandmaritime.com> wrote:
> 
> If the default policy on your mangle & Nat chain is set to DROP & if you
> have no rules to classify traffic in these tables, all your packets will get
> dropped here. They will not make it to the FILTER table.

This is a good point and shows where maybe I am starting to MIS-understand.  

1.  Can appended rules override default polices? 
2.  Do you need to include appended rules to parts of the iptables
chain that you are not using, or else all the packets will get
dropped?  For example, do you have to set Mangle rules even if you are
not using any Mangling but have set a DROP policy for mangling.

> 
> In your commands, first you have set the default policy to DROP on all
> chains in the filter table. Then you have set policies to accept all the
> traffic in the INPUT & OUTPUT chains. I do not get this. If you are aiming
> to accept all packets in the INPUT & OUTPUT chain you might as well set the
> default policy in these chains to ACCEPT.

I understand your point here.  I used those -j ACCPT rules because
everything else has failed so far to override the DROP policy, so that
was a last resort desperately trying to get some packets through the
routerbox.  I really don't want to accept everything blindly on the
INPUT and OUTPUT of the routerbox.  I would actually like to set
INPUT/OUTPUT rules that only allow traffic on a few different ports
for web browsing, ssh access, and network samba; close everything
else.


> I will email you a diagram on the packet flow inside the kernel. Probably
> that would make things easier in understanding where each chain exists
> inside the kernel.
> 

Hey now, thanks for the diagram.  This is pretty cool stuff.  I need a
few months to figure it all out though.  :-)

Please write back on the other issues above if you have a chance.
Hope to hear from you.

Thanks,

Mike


  reply	other threads:[~2004-09-01 15:46 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 [this message]
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
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=8ca4228204090108466549b5f3@mail.gmail.com \
    --to=1100100@gmail.com \
    --cc=dseshadri@broadbandmaritime.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 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.