public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] IPv6 not ready here; Hmmm
Date: Wed, 8 Jun 2011 15:01:01 -0500	[thread overview]
Message-ID: <BANLkTi=5iPQWQtziBy0J34v_-KYXf8toQg@mail.gmail.com> (raw)
In-Reply-To: <4DEED011.90907@gmail.com>

On Tue, Jun 7, 2011 at 8:27 PM, Dale <rdalek1967@gmail.com> wrote:
> Should I have the USE flag ipv6 enabled or should I leave it off for now?
>  If so, anyone had any trouble with it or is this a trivial change?

Enable the IPv6 stuff in kernel, enable ipv6 USE flag in your
make.conf, rebuild any packages that were -ipv6 before, and you should
be good to go from a basics standpoint.

After that, you need actual IPv6 service from your ISP (and modem and
router), or tunnel over IPv4 through a provider.

My cable ISP has a 6RD Border Relay. My DD-WRT router supports IPv6
and I set it up to make the connection to the 6RD, so on my client
machines there's no special setup needed, it just magically works
without any problems.

If your router doesn't support it, you can still establish IPv6 tunnel
from your Gentoo box directly, there are several ways to do it.
Something like net-misc/miredo is extremely simple to set up if you
just want to try it, and to see the dancing turtle on www.kame.net :)



  parent reply	other threads:[~2011-06-08 20:03 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08  1:27 [gentoo-user] IPv6 not ready here; Hmmm Dale
2011-06-08  1:53 ` Dale
2011-06-08  2:18   ` Adam Carter
2011-06-08  5:31     ` Mick
2011-06-08  5:29 ` [gentoo-user] " Hans de Graaff
2011-06-08 17:01 ` [gentoo-user] " Volker Armin Hemmann
2011-06-08 18:59   ` Dale
2011-06-09  3:25     ` Volker Armin Hemmann
2011-06-09  4:56       ` Dale
2011-06-09  6:59         ` Volker Armin Hemmann
2011-06-08 19:51   ` Paul Hartman
2011-06-08 22:04     ` Mick
2011-06-09  1:25       ` Paul Hartman
2011-06-09  5:46         ` Mick
2011-06-09 15:06           ` Paul Hartman
2011-06-09 15:51           ` Paul Hartman
2011-06-09 20:27             ` Mick
2011-06-09 20:52               ` Paul Hartman
2011-06-09 11:16         ` Tanstaafl
2011-06-09 14:23           ` Mick
2011-06-09 16:21           ` Paul Hartman
2011-06-08 19:45 ` Paul Hartman
2011-06-08 20:08   ` Alan McKinnon
2011-06-08 20:01 ` Paul Hartman [this message]
2011-06-09  2:15   ` Dale
2011-06-09  3:23     ` Pandu Poluan
2011-06-09  4:50       ` Dale
2011-06-09  5:14         ` Paul Hartman
2011-06-09  6:52           ` Dale
2011-06-09  7:46             ` Alan McKinnon
2011-06-09  8:48               ` Dale
2011-06-10 15:46                 ` Dale
2011-06-10 16:03                   ` Paul Hartman
2011-06-10 17:39                     ` Dale
  -- strict thread matches above, loose matches on Subject: below --
2011-06-09  1:52 Pandu Poluan
2011-06-10  1:52 Pandu Poluan
2011-06-10  7:22 ` Joost Roeleveld
2011-06-10 10:08   ` Pandu Poluan
2011-06-10 13:17     ` Joost Roeleveld
2011-06-10 14:30       ` Alan McKinnon
2011-06-10 15:59         ` Joost Roeleveld
2011-06-10 16:04         ` Paul Hartman

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='BANLkTi=5iPQWQtziBy0J34v_-KYXf8toQg@mail.gmail.com' \
    --to=paul.hartman+gentoo@gmail.com \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox