Re: eth1 - iptables do not work

To: debian-firewall@lists.debian.org
Subject: Re: eth1 - iptables do not work
From: Ansgar Wiechers <lists@planetcobalt.net>
Date: Thu, 9 Oct 2008 17:16:22 +0200
Message-id: <[🔎] 20081009151622.GB20168@mail.planetcobalt.net>
In-reply-to: <[🔎] 48EE1B9C.7070703@med.unc.edu>
References: <[🔎] 48ED435E.1080901@med.unc.edu> <[🔎] 20081009065602.GU26719@localhost> <[🔎] 48EDF6D5.3080201@med.unc.edu> <[🔎] 20081009135951.GA20168@mail.planetcobalt.net> <[🔎] 48EE1B9C.7070703@med.unc.edu>

On 2008-10-09 Tamas Hegedus wrote:
> Thanks for the detailed notes, I learned a lot from them.

You're welcome.

> Somewhere I have red that I "DROP" should not be the default policy
> for the INPUT and for the OUTPUT chain. ???

For the INPUT chain I can't think of a reason why that would be. As for
the OUTPUT chain: see my previous mail.

Regards
Ansgar Wiechers
-- 
"The Mac OS X kernel should never panic because, when it does, it
seriously inconveniences the user."
--http://developer.apple.com/technotes/tn2004/tn2118.html

Reply to:

References:
- eth1 - iptables do not work
  - From: Tamas Hegedus <hegedus@med.unc.edu>
- Re: eth1 - iptables do not work
  - From: Paolo <oopla@users.sf.net>
- Re: eth1 - iptables do not work
  - From: Tamas Hegedus <hegedus@med.unc.edu>
- Re: eth1 - iptables do not work
  - From: Ansgar Wiechers <lists@planetcobalt.net>
- Re: eth1 - iptables do not work
  - From: Tamas Hegedus <hegedus@med.unc.edu>

Prev by Date: Re: eth1 - iptables do not work
Next by Date: iptables dport range
Previous by thread: Re: eth1 - iptables do not work
Next by thread: iptables dport range
Index(es):
- Date
- Thread