From: "Rob Sterenborg" <rob@sterenborg.info>
To: "'Robert P. J. Day'" <rpjday@mindspring.com>
Cc: 'iptables mailing list' <netfilter@lists.netfilter.org>
Subject: RE: thoughts on a newbie tutorial i'll be giving shortly
Date: Thu, 30 Oct 2003 16:56:11 +0100 [thread overview]
Message-ID: <20031030184542.698CB1B9B8@smtp.ttp.nl> (raw)
In-Reply-To: <Pine.LNX.4.44.0310300823360.18175-100000@localhost.localdomain>
> there are definitely two schools of thought: 1) those who set
I know ;o)
> if you want to be really restrictive on your OUTPUT chain,
> that's fine. but for testing purposes, you might want to
> open it up, make sure everything works, *then* lock it down
> and see what breaks. at least you'll be closer to isolating
> the problem.
I was referring to the last statement, not your question (which makes
this OT btw, but I wanted to answer Steve) :
> > Just my 0.02, if it's worth that much considering I cant even get
> > DNS lookups from my fw working.....
In your case I'd not set policy to DROP for OUPUT.
IMHO it would be overkill for an introduction of approx. 30 minutes.
Gr,
Rob
next prev parent reply other threads:[~2003-10-30 15:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 12:45 thoughts on a newbie tutorial i'll be giving shortly Knight, Steve
2003-10-30 13:11 ` Robert P. J. Day
2003-10-30 13:14 ` Rob Sterenborg
2003-10-30 13:25 ` Robert P. J. Day
2003-10-30 15:56 ` Rob Sterenborg [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-31 0:57 Daniel Chemko
2003-10-31 0:36 George Vieira
2003-10-31 1:51 ` Arnt Karlsen
2003-10-31 2:45 ` Tarek W.
2003-10-30 16:54 Knight, Steve
2003-10-30 14:31 Knight, Steve
2003-10-30 15:24 ` Robert P. J. Day
2003-10-30 12:30 Robert P. J. Day
2003-10-31 0:07 ` Tarek W.
2003-10-31 1:45 ` Arnt Karlsen
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=20031030184542.698CB1B9B8@smtp.ttp.nl \
--to=rob@sterenborg.info \
--cc=netfilter@lists.netfilter.org \
--cc=rpjday@mindspring.com \
/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