Actually it's kinda odd that arc.he.net had extra ipv6 addresses configured on it out of the "aa" range. We've fixed this, and should only have 2001:470:0:aa::2 from that range now.

try: netsh interface ipv6 delete interface "IP6Tunnel"

I have a 210, and according to the release notes for firmware v4.40:

"4.40:F01 Support for IPv6."

http://www.axis.com/ftp/pub_soft/cam_srv/cam_210/latest/relnote.txt

I'll flash it tomorrow and put it up somewhere

*update* Looks like it took the firmware without issue, however the IPv6 support seems to be for auto-configuration, and doesn't let you statically assign an address.

Available for a short time: http://ipv6cam.deus-exmachina.net/view/index.shtml

Whoops, thanks for pointing that out. rDNS should be pushed out shortly.

The login uses the same database. Should be working. Works for all of our tunnel testing accounts so far.

This forum provides a mechanism by which you can submit suggestions for the IPv6 Certification Program that can be reviewed by the tunnelbroker.net staff and your peers. This is not a job board or an advertising forum. Actually none of our forum threads are for advertising, let alone advertising without any mention of IPv6.

If you are reporting an issue with the program, please do so via email at ipv6@he.net as this address is monitored by the Hurricane Electric ticketing system and will result in a much faster response time.

As always we reserve the right to remove, or move any topics that don't match the intended purpose of the forum.

This forum provides a mechanism by which common questions and answers about the IPv6 Certification Program can be handled by the tunnelbroker.net staff. This is not a job board or an advertising forum. Actually none of our forum threads are for advertising, let alone advertising without any mention of IPv6.

If you have a question about this program, or IPv6 in general please drop it in here and we will do the best we can to help.

If you are reporting an issue with the program, please do so via email at ipv6@he.net as this address is monitored by the Hurricane Electric ticketing system and will result in a much faster response time.

As always we reserve the right to remove, or move any topics that don't match the intended purpose of the forum.

Hello!

Hurricane Electric is happy to announce that we've released an IPv6 Certification Program. This will provide you with something entertaining to do after you have established IPv6 connectivity, as well as a way to test your IPv6 readiness and your ability to host services available on IPv6.

http://ipv6.he.net/certification

Tunnelbroker.net users are already enrolled in the program, and should use their username/password for Tunnelbroker.net to log in. (enable javascript)

For any questions about the program, or issues you might have, please email ipv6@he.net

Use netsh to delete the interface

http://technet.microsoft.com/en-us/library/cc740203.aspx

<3 Google

If your host is behind a firewall/router appliance, make sure that when creating the tunnel under Vista, that you change out "85.223.50.138" for the IP assigned to you by DHCP.

If your Vista machine is directly connected to the internet on that IP, it should have worked.

in page "Update IPv4 Endpoint"

change your ip to a false ip

after add your true ip again

http://www.tunnelbroker.net/forums/index.php?topic=147.msg633#msg633

This is only useful if he changed his ipv4 endpoint. if not, this has no bearing as the tunnel-server has his tunnel configured.

Tunnel is configured on our side. I cannot ping6 your side of the tunnel, but I can ping your IPv4 endpoint.

tserv11.ams1.ipv6.he.net is up. Your tunnel is configured, and I cannot ping6 your side of the tunnel. I pushed out the tunnel-servers configuration again just to be certain.

Did you change IPv4 endpoints recently? I cannot ping the IPv4 endpoint you currently have set.

The tunnel servers are getting a platform update today, so its rolling restarts one at a time as we make sure everything is happy. That is why you saw NYC down for a moment today.

If you really want, we can quote you paid services, if you email ipv6@he.net

BGP tunnels are done by hand, as such it wasn't up yet. It is configured now, and we cannot ping6 your side of the tunnel. As for the example config versus what the forums say, we've posted what our Juniper users have used that worked.