From: Jeff Garzik <jgarzik@pobox.com>
To: Quantum Scientific <Info@Quantum-Sci.com>
Cc: netdev@oss.sgi.com
Subject: Re: Kernel 2.6 IPV6 Busted
Date: Sun, 27 Feb 2005 13:12:14 -0500 [thread overview]
Message-ID: <42220D7E.3000104@pobox.com> (raw)
In-Reply-To: <200502270928.44402.Info@Quantum-Sci.com>
Quantum Scientific wrote:
> After a week of intensive research and full-time study, it's become clear that
> IPV6 support, as it comes in standard Linux 2.6 kernels, is effectively
> non-functional.
Strange how I use this non-functional support every day.
> I have a properly working firewall, but it appears there is no stateful
> filtering nor connection tracking in the IPV6 stack. I send out an
> So is there something I'm missing? Am I completely fscked-up when I say that
> it doesn't work in practice, because there is no stateful packet filtering
> nor connection tracking?
Yes. IPv6 does not need NAT'ing. Everyone should have a global
address. Connection tracking is not needed.
Jeff
prev parent reply other threads:[~2005-02-27 18:12 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
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 [this message]
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=42220D7E.3000104@pobox.com \
--to=jgarzik@pobox.com \
--cc=Info@Quantum-Sci.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.