behind NAT

[realdreams]

When behind a firewall appliance that passes protocol 41, use the IPv4 address you get from your appliance's DHCP service instead of the IPv4 endpoint you provided to our broker.

I am behind a firewall(DD-WRT) that doesn't passes ipv6. IPv6 support is not included in the ddwrt build.
Can I set up the tunnel without DMZ(conditional forwarding is OK but not DMZ)?
Thanks

[cholzhauer]

The way to find out would be to set it up and see if it works :)  most people on here just host the tunnel on the ddwrt router

[realdreams]

I just replaced my public ip with private ip in netsh command and it worked... I guess.
I can get ping reply from ipv6.google.com but I can't open it in browser.

I added he dns and google public dns ipv6 to ipv6 dns for IPv6Tunnel

> ipv6.google.com
Server:  ordns.he.net
Address:  2001:470:20::2

Non-authoritative answer:
Name:    ipv6.l.google.com
Address:  2001:4860:800f::93
Aliases:  ipv6.google.com

Pinging ipv6.l.google.com [2001:4860:8007::6a] with 32 bytes of data:
Reply from 2001:4860:8007::6a: time=63ms
Reply from 2001:4860:8007::6a: time=58ms

I can open ipv6.google.com in IE9 but not Chromium 18


edit:
ipv6dns disabled in Chromium by default.

How can I force using ipv6 if available?

Server:  ordns.he.net
Address:  2001:470:20::2

Non-authoritative answer:
Name:    youtube-ui.l.google.com
Addresses:  2001:4860:800f::5d
          72.14.204.93
          72.14.204.136
          72.14.204.190
          72.14.204.91
Aliases:  www.youtube.com

Pinging youtube-ui.l.google.com [74.125.159.93] with 32 bytes of data:
Reply from 74.125.159.93: bytes=32 time=17ms TTL=49
Reply from 74.125.159.93: bytes=32 time=28ms TTL=49
Reply from 74.125.159.93: bytes=32 time=25ms TTL=49

[kasperd]

ipv6dns disabled in Chromium by default.

What version are you using? I am using Chromium on Ubuntu 10.04, and it will use IPv6 when it gets the choice between native IPv6 and IPv4. Are you sure you are actually using your HE tunnel and not an auto configured tunnel such as 6to4 or Teredo? Google dislikes auto configured tunnel, so it is quite likely that some versions of Chromium will not use IPv6 if you only have an auto configured tunnel.

But the Chromium version I have installed will not avoid IPv6 in those cases, instead it will open a second TCP connection using a different server address if the first connection has not been established within 0.2 second. I believe all recent Chromium versions will behave similar.

You'll probably need to use tcpdump or wireshark to figure out what is happening. Can you look at the traffic inside or outside the tunnel endpoint? You can also try to go to one of those sites that can tell you which IP address you use and compare that to those that are actually configured on your computer.