From: Arnt Karlsen <arnt@c2i.net>
To: netfilter@lists.netfilter.org
Subject: Re: Setting a default policy does not work :(
Date: Tue, 2 Dec 2003 21:03:47 +0100 [thread overview]
Message-ID: <20031202210347.3e151a19.arnt@c2i.net> (raw)
In-Reply-To: <200312021107.39011.JALaramie@Loudoun-Fairfax.com>
On Tue, 2 Dec 2003 11:07:39 -0500,
Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com> wrote in message
<200312021107.39011.JALaramie@Loudoun-Fairfax.com>:
> On Tuesday 02 December 2003 10:53, Chris Brenton wrote:
> > On Tue, 2003-12-02 at 10:33, Michael Gale wrote:
> > > Inserting the following to the bottom of my firewall script:
> > >
> > > ### Causes all traffic to or from the box on either interface to
> > > #be
> > > dropped regardless of all other rules.
> > >
> > > iptables --policy INPUT DROP
> > > iptables --policy OUTPUT DROP
> > > iptables --policy FORWARD DROP
> >
> > Try:
> > iptables -P INPUT DROP
> > iptables -P OUTPUT DROP
> > iptables -P FORWARD DROP
> >
> > Works for me on multiple firewalls using multiple interfaces.
> >
>
> OK, now *I'm* confused. Aren't they the same command?
..supposely, according to the man page, but if OP is using a
development version off his own cvs tree or somesuch, all
bets are off. ;-)
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
next prev parent reply other threads:[~2003-12-02 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 15:33 Setting a default policy does not work :( Michael Gale
2003-12-02 15:53 ` Ray Leach
2003-12-02 15:53 ` Chris Brenton
2003-12-02 16:07 ` Jeffrey Laramie
2003-12-02 20:03 ` Arnt Karlsen [this message]
2003-12-03 0:49 ` Michael Gale
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=20031202210347.3e151a19.arnt@c2i.net \
--to=arnt@c2i.net \
--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