From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] IPv6 not ready here; Hmmm
Date: Thu, 9 Jun 2011 06:46:44 +0100 [thread overview]
Message-ID: <201106090646.54905.michaelkintzios@gmail.com> (raw)
In-Reply-To: <BANLkTik8kAYaCpw22YJiUV6ra93Jyh-Tng@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 3624 bytes --]
On Thursday 09 Jun 2011 02:25:43 Paul Hartman wrote:
> My wireless router is running DD-WRT (which is a Linux distro). It is
> running kernel 2.6.34 and has all the ipv6 modules enabled in the
> kernel. Basically, it is setup by loading the "sit" module
> (CONFIG_IPV6_SIT_6RD in kernel config). Then using the "ip" command to
> create a sit tunnel and set up the routes for IPv6 traffic, and then
> starts radvd (the IPv6 router advertisement daemon, think of it as a
> kind of DHCP server for IPv6 addresses). The process should be exactly
> the same on OpenWRT.
Oh I see, that explains it!
> > What does your /etc/resolv.conf show?
>
> $ cat /etc/resolv.conf
> nameserver 127.0.0.1
>
> (because I run net-dns/unbound on my local machine). For the other
> computers/devices they use the DNS server which runs on the router,
> 192.168.0.1
>
> My ISP does offer DNS servers at actual IPv6 addresses, though I'm not
> using them.
So when a ipv6 query arrives at your local resolver (router) from one of your
LAN machines on the 192.168.0.1 address, the router knows to send it down the
tunnel to be resolved at the ISP's resolvers?
> For Microsoft Windows (at least Windows 7), when it detects IPv6
> advertisement server on the local network, it will use it
> automatically. When no IPv6 is detected, it uses Teredo instead. Maybe
> your DNS servers don't return IPv6 addresses?
Well, yes my router is ipv4 only and therefore it would not resolve ipv6
addresses.
> On my wife's Windows 7 laptop, it just worked perfectly after I
> enabled it on my router and her wifi reconnected. All tests on
> test-ipv6.com pass except for the last DNS test. She can go to sites
> like http://www.v6.facebook.com no problems.
That's because Windows7 use toredo servers/relays to resolve and connect to
ipv6 addresses.
> BTW, Windows Vista and 7 generate randomized host IDs for public IPv6
> addresses, it's generally advised to disable that. You can do that by
> running this at administrator cmd prompt:
> netsh interface ipv6 set global randomizeidentifiers=disabled
I was looking at the same in the Linux kernel scratching my head if I should
enable this or not ...
What does it do - not sure I understand what such temporary addresses are used
for:
============================================
IPv6: Privacy Extensions (RFC 3041) support
CONFIG_IPV6_PRIVACY:
Privacy Extensions for Stateless Address Autoconfiguration in IPv6 support.
With this option, additional periodically-altered pseudo-random global-scope
unicast address(es) will be assigned to your interface(s).
We use our standard pseudo-random algorithm to generate the randomized
interface identifier, instead of one described in RFC 3041.
By default the kernel does not generate temporary addresses. To use temporary
addresses, do
echo 2 >/proc/sys/net/ipv6/conf/all/use_tempaddr
See <file:Documentation/networking/ip-sysctl.txt> for details.
Symbol: IPV6_PRIVACY [=n]
Type : boolean
Prompt: IPv6: Privacy Extensions (RFC 3041) support
Defined at net/ipv6/Kconfig:24
Depends on: NET [=y] && INET [=y] && IPV6 [=y]
Location:
-> Networking support (NET [=y])
-> Networking options
-> TCP/IP networking (INET [=y])
-> The IPv6 protocol (IPV6 [=y])
============================================
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-06-09 5:47 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 [this message]
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
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=201106090646.54905.michaelkintzios@gmail.com \
--to=michaelkintzios@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