Re: Setting a default policy does not work :(

[Michael Gale <mgale@utilitran.com>]

Hello,

	Thanks for the help so far -- it must of been the location I had placed the default policy in the file or maybe some other rule. But everything is working fine now. 

Michael


On Tue, 2 Dec 2003 21:03:47 +0100
Arnt Karlsen <arnt@c2i.net> wrote:

> 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.
> 
> 
> 


-- 
Michael Gale
Network Administrator
Utilitran Corporation