6to4 is protocol 41 as well, perhaps you meant Teredo. Most likely it is something in the modem, and if it cannot be changed out, or but into a proper bypass, there isn't much that can be done on our end.

Yes, Teredo, of course. That's what I get for posting before dinner.

Can I still use HE with those tunnel options?

No, our service is only 6in4 tunnels. If you can figure out the protocol41 issue, though, it sounds like everything else looks good.

If AT&T NOC says that they are blocking protocol41, you'll have to take them at their word. Sorry.

Have a look at 6to4, Sixxs, or Gogo6. They use different methods of providing tunnels/connectivity, so one of those might work for you.

You can subnet a /64 out farther, but its generally recommended to have /64 as your longest prefix. SLAAC won't work for anything longer than /64.

For options such as DNS and NTP, you have three possible options (aside from static assignment), none of which are very mature at the moment. Stateful DHCPv6, handing out all the information from DHCP like DHCPv4 does, stateless DHCP + SLAAC, where DHCPv6 only passes out the DNS, etc information and doesn't keep track of anything else and basic information is gained via SLAAC, or RDNSS, where the RA contains the extra configuration information. Unfortunately, the first option is the most mature at the moment, I believe. RDNSS is the easiest, as it doesn't require DHCP at all, but support for it is very hit or miss at the moment.

I received mine today. ;-)

When you put your modem in bridge mode, it will pass all traffic through untouched, instead of acting as a router and possibly filtering something.

Though, there might be some miscommunication in terms here. If your modem is not acting as a router (ie, handing out DHCP addresses to your internal network and performing NAT), then it is very unlikely to be the culprit. If AT&T has stated that they are blocking protocol41 traffic, then you need to yell at them to stop filtering your internet traffic. It is impossible to set up a 6in4 tunnel with protocol41 being blocked (as protocol41 is the ipv6-in-ipv4 protocol number).

If you don't mind doing some legwork, you can probably get good results from consumer-grade routers and DD-WRT.

Have you taken a look at PowerDNS? You can script its behavior with Lua.

There are currently no additional tests above Sage (Technical and Knowledge) aside from the daily tests.

What does your virtualhost config look like? What does your ip6tables config look like? What happens when you telnet to port 80 using the ipv6 address?

Yes, I know. But for some reason I kind of find it self-evident that somebody who's interested in IPv6 certification also has at least an IPv6 connection at home (whether it is native or tunneled). 

True, but there are also other options for IPv6 at home, such as Sixxs or GoGo. We're just the best of the bunch, that's all.

By the way, the topic starter seems to be Sage certified but doesn't have the ability to create a HE tunnel at his home . Maybe he'd better find an ISP which allows your global IP4 to be pingable.

The HE IPv6 certifications aren't HE-specific at all, so anyone with IPv6 knowledge and connectivity can get certified. You don't even need IPv6 connectivity from home to earn your Sage.

May I ask you if you're a HE official on this forum? Your user icon seems to suggest that.

Yep, I sure am.

Sorry, unfortunately you will not be able to establish a tunnel if the endpoint cannot be reached via ping.

I generally recommend not blocking ICMPv6 at all (as much of it is required for proper IPv6 transit), but do recommend putting limits on it. For example, with iptables:

Code:

ip6tables -A INPUT   -j ACCEPT  -p ipv6-icmp --match limit --limit 50/minute

The PPTP VPN Beta is currently on hold, so those configuration options don't show up for newly created tunnels.