public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] IPv6 not ready here; Hmmm
Date: Wed, 08 Jun 2011 21:15:07 -0500	[thread overview]
Message-ID: <4DF02CAB.2080505@gmail.com> (raw)
In-Reply-To: <BANLkTi=5iPQWQtziBy0J34v_-KYXf8toQg@mail.gmail.com>

Paul Hartman wrote:
>
> 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 :)
>
>    

Now what was I thinking.  Oh, wait.  I wasn't thinking.  There was the 
problem right there.  I hadn't enabled any of the IPv6 stuff in the 
kernel.  Jeeez, what a idiot.  I haven't even thought of the kernel 
settings. < sighs >

Anyway, I enabled a lot of stuff in the kernel and will reboot at some 
point and test again.  I'm not sure when I will be rebooting tho.

Dale

:-)  :-)



  reply	other threads:[~2011-06-09  2:16 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
2011-06-09  2:15   ` Dale [this message]
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=4DF02CAB.2080505@gmail.com \
    --to=rdalek1967@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