All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Frank Matthieß" <frankm@lug-owl.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Trivial IPv6-for-Fedora HOWTO
Date: Mon, 23 Aug 2004 10:50:00 +0200	[thread overview]
Message-ID: <20040823085000.GA12383@dvmwest.dvmwest.de> (raw)
In-Reply-To: <4129236E.9020205@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

Jeff Garzik [2004-08-23 00:51 CEST]:
> 
> So, thanks to David Woodhouse for showing me how to do this.  IPv6 
> appears to be very, very close to a Just Works(tm) state.
> 
> These instructions are for Fedora Core 2 users, and describe how to set 
> up IPv6 automatically tunnelling (6to4) on an IPv4 network.  If you are 
> stuck on an IPv4-only network (like most of us), this enables 
> communication with IPv6 hosts quickly, easily, and transparently.
> 
> (this HOWTO is archived at http://yyz.us/ipv6-fc2-howto.html)
[...]
> 
> If you have an iptables ipv4 firewall, you'll want to
> 
[...]
> 
> F2) duplicate your ipv4 firewall rules for ipv6, using ip6tables.  Some 
> things, like masquerade, are not applicable to ipv6.

Does Fedora Core 2 has patches, which add ipv6 statefull inspection to
netfilter? If not, this is only true for rules without statefull
inspection.

Frank.
-- 
Frank Matthieß

"Was kommt denn als nächstes? Ein Studiengang 6 Semester sendmail mit
 Aufbaustudium `sendmail security'?" -- Frank Guthausen

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-08-23  8:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22 22:51 Trivial IPv6-for-Fedora HOWTO Jeff Garzik
2004-08-22 23:08 ` Paul Fraser
2004-08-22 23:06   ` Alan Cox
2004-08-22 23:22   ` Jeff Garzik
2004-08-22 23:24   ` Tomasz Torcz
2004-08-22 23:42 ` Bernd Eckenfels
2004-08-23  5:25   ` Kalin KOZHUHAROV
2004-08-23  9:07     ` Bernd Eckenfels
2004-08-23  8:50 ` Frank Matthieß [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=20040823085000.GA12383@dvmwest.dvmwest.de \
    --to=frankm@lug-owl.de \
    --cc=linux-kernel@vger.kernel.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 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.