netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Torcz <zdzichu@irc.pl>
To: netdev@oss.sgi.com
Subject: Re: Kernel 2.6 IPV6 Busted
Date: Tue, 1 Mar 2005 21:46:15 +0100	[thread overview]
Message-ID: <20050301204615.GC15329@irc.pl> (raw)
In-Reply-To: <422497BA.9090606@pobox.com>

On Tue, Mar 01, 2005 at 11:26:34AM -0500, Jeff Garzik wrote:
> Just write sane firewall rules that don't allow incoming.

 Isn't this thread about non-working stateful firewalling? Specifically
situation where -m state --state RELATED or ESTABLISHED isn't allowin
any packets because there is no connection tracking? Without allowing
incoming packets there could be no 2-way communication (for UDP at
least).

-- 
Tomasz Torcz               "Never underestimate the bandwidth of a station
zdzichu@irc.-nie.spam-.pl    wagon filled with backup tapes." -- Jim Gray

  reply	other threads:[~2005-03-01 20:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27 15:28 Kernel 2.6 IPV6 Busted Quantum Scientific
2005-02-27 16:10 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-27 16:29   ` Quantum Scientific
2005-02-27 17:28     ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-27 18:08       ` Quantum Scientific
2005-03-15  5:00     ` Horms
2005-02-27 17:40 ` Andre Tomt
2005-02-27 18:20   ` Quantum Scientific
2005-02-27 18:59     ` Jeff Garzik
2005-02-27 19:10       ` Quantum Scientific
2005-02-27 19:58         ` Jeff Garzik
2005-02-27 20:10           ` Quantum Scientific
2005-02-27 21:35             ` David S. Miller
2005-03-01 10:07               ` Denis Vlasenko
2005-03-01 13:50                 ` Quantum Scientific
2005-03-01 16:26                 ` Jeff Garzik
2005-03-01 20:46                   ` Tomasz Torcz [this message]
2005-03-01 23:55                     ` Quantum Scientific
2005-03-02 14:02                   ` Denis Vlasenko
2005-03-02 19:12                     ` Jeff Garzik
2005-03-01 21:50     ` Andre Tomt
2005-03-01 23:59       ` Quantum Scientific
2005-02-27 18:12 ` Jeff Garzik

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=20050301204615.GC15329@irc.pl \
    --to=zdzichu@irc.pl \
    --cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).