Nothing seems to be working. I turned on logging on my router to see if it's blocking or allowing the packets, but it doesn't show it either way. I just get a bunch of dropped packets from my upstream router (my ISP's) with a protocol of "boot-pc". Kinda weird, but, still not helping.

IDK, I guess I'll just give up and try later.

Could my router (DD-WRT) be firewalling it? It's not terminating at the router, I'm passing protocol 41 through to a computer on my network and terminating it there. iptables and ip6tables on that computer both show no rules with a default policy of ACCEPT.

EDIT: I fired up wireshark and I found that when I run the test, no packets show up on that computer. So, my router must be blocking the incoming traffic. What would be a iptables (not ip6tables) rule that will allow all IPv6 traffic to go to it's destination?

Does it atleast resolve to the right address for you? It should resolve to:

2001:470:1F06:6C5::2

I'm having this same problem.

http://ipv6.home.core.arcticfire.net

It gives me the same error. I know that apache is accepting the IPv6 connection, because I can get to it from that computer. (using the domain or the IPv6 address) I don't think that DD-WRT is somehow firewalling the IPv6 traffic, but idk.

EDIT: I'm not sure if this will shed any light on the subject, but the tunnel is terminated on the computer, not at the router.

I would just like to thank NYT for all his help.

Well, it's not just HE's that the problem exists with, but it's the one that I really want to connect to. I posted this here for two reason: (1) I already have an account here, (2) It is HE's server after all.

I'm using KVirc to try to connect to irc.ipv6.he.net on efnet.org. However, it all ways gives me a socket error: connection timed out. Here's my traceroute to the server.

  1       <1 ms    <1 ms    <1 ms  home.core.arcticfire.net [2001:470:1f07:6c5::]
  2       34 ms    38 ms    50 ms  2001:470:1f06:6c5::1
  3       41 ms    42 ms    72 ms  gige-g3-8.core1.nyc4.he.net [2001:470:0:5d::1]
  4      122 ms   111 ms   123 ms  10gigabitethernet3-1.core1.sjc2.he.net [2001:470:0:33::1]
  5      115 ms   124 ms   114 ms  gige-g1-1.core1.fmt1.he.net [2001:470:0:2f::1]
  6      112 ms   112 ms   114 ms  irc.ipv6.he.net [2001:470:0:6667::2]

If someone could maybe help me out here, that would be great. Also, I have this in my router's iptables, I'm assuming this means it's not firewalling IPv6 traffic.

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     ipv6 --  anywhere             anywhere

Ok, but I'm talking about a different IP address for IRC, one that is completely unique. (I want to give it a special RDNS entry) Basically:

1) Address for general browsing. (this will be the 'autoconfig' address that you mentioned)
2) An address for http.
3) An address for IRC usage.

That was it. I was using my public IP instead of my local IP. But anyway, I got it working with DD-WRT, so no worries here.

Ok, cool. Everything is working. Now, my next question. How can I assign a specific address to a specific computer on my lan. Let's say I have apache and I want it to listen on a specific address. Or when I connect to IRC, I want to always use the same address that I did last time to connect.

Ok, I didn't replace the tunnelbroker's server IP, maybe that's what was wrong. I just used the one he had there. (I don't know why it didn't occur to me to change that too) Anyway, when I get home (or just get time to RDP home), I'll try that.

Ok........that explanation of the two addresses confused me.

Let's start out with something simple, like getting it working. I just installed DD-WRT v23 std. I followed this guide exactly, only changing stuff to put my addresses in. But yet it still doesn't work. I really thought I was good at networking, but this knocked me down a peg or twenty.

http://solosoft.org:81/projects/ipv6/ipv6.html

We are looking to compile a list of firewall/CPE devices that by default (With no major changes except maybe a firmware update) support IPv6 over IPv4 tunnels. (Protocol 41 tunneling).

If you are passing your tunnel over a commercial firewall to terminate on a machine behind it, then please let us know what version hardware and firmware you are having success with.

So far we have tested in house:

# Linksys WRT54G firmware 4.21.2
# Linksys WRT54GL firmware 4.30.7 & 4.30.11
# D-Link DGL-4100 firmware 1.6 & 1.7

All of which work.
 

I might have set something up wrong. My WRT54g has firmware version 4.21.1 (not that much of a difference) and my tunnel doesn't work. Here are the commands I used on my windows machine as instructed by the tunnel info page.

Code:

ipv6 install
ipv6 rtu ::/0 2/::209.51.161.14 pub
ipv6 adu 2/2001:470:1f06:6c5::2

Now please keep in mind, I just can't wrap my mind around the address structure of IPv6. I'm the kinda person that says IPv4 + NAT = fine for me. But I'm trying to keep an open mind, learn new things and try new things.

I'm trying to set up RDNS for my tunnel. To make it easier to provide an example for me, here's the information.

Routed /48:       2001:470:89a6::/48
Routed /64:     2001:470:1f07:6c5::/64

Now I'm just working on the /64 for now. (I didn't even mean to allocate the /48 ) I'm using xname.org for my DNS hosting. I already have the name servers set up in the Control Panel here.

Also please note that this is for delegation of reverse DNS for the netblocks listed below, your routed /64 and /48. The Point to Point /64 reverse DNS is never delegated.

What does this mean? I thought this meant that you can't create a PTR record for a specific IP but rather you had to do it for the subnet....I didn't know you could do this. I thought the PTR record had to contain a specific IP. Maybe I'm just a little confused about that too.

I could sure use some help. I don't even have the tunnel working yet, but I expect that to all be fixed as soon as I upgrade my router to DD-WRT so that it will allow the proto41 to pass.

EDIT:
Just out of curiosity (it's the main reason I'm doing this, to learn) why are these different?

Client IPv6 address:     2001:470:1f06:6c5::2/64
Routed /64:     2001:470:1f07:6c5::/64

Which will actually be used?

for dd-wrt, use v23 if you want working ipv6 tunnel termination on the appliance.

Thanks for that. I was going to install v23 then upgrade to v24, but now that you mentioned that, I'll stick with v23 standard. (I'm on v4 Official, so I have to use v23 mini, then go from there)