Could you please check on tserv4.nyc4.ipv6.he.net aswell? Can't connect.

You will get a faster response if you email ipv6@he.net. These boards are not constantly monitored.

Have you tried bypassing your router and plugging directly into your modem? Have you tried temporarily disabling your firewall? Its always possible that your ISP has blocked ICMP for some reason if everything else fails.

I made Sage in July ( I think  ), no shirt yet.

Do I need to get to 1500 first?

No, you only need to attain sage. You don't need to get all 1500 points for the t-shirt. We send the tshirts out in batches every couple of months. We haven't sent out a batch since July. I'm not sure when another batch is being sent out.

Your account does not have any domains configured, and you obfuscated the actual domain name. Without either of those bits of information, I can't actually make sure your configuration is correct. (Though I do not see anything amiss from what you have posted.)

T-shirts are sent out in batches every couple of months to everyone who attained sage since the last batch. We send t-shirts all over the world, so that's not a problem. Just make sure you validate your postal address, and you'll get lumped into the next batch.

Its just a stale DNS entry. I'll get it cleaned up.

No new news on either of those services at this time.

Are you connecting over http or https? Is your password properly md5-hashed? Have you tried the https://USERNAME:PASSWORD@ version?

Ping is a basic Internet program that allows a user to verify that a particular IP address exists and can accept requests.



How about dig? I still dont understand... thanks guys!

dig is used to perform DNS queries against DNS servers. (A, AAAA, MX, SOA, etc)

PPTP looks to be running fine on that tserv. Has anything changed on your end lately?

Okay. Then how can I get an IPv6 firewall in a version of pfSense that does not even support IPv6?

The version that supports IPv6, 2.1, is still beta. 2.0 is not even finished yet so it will be a while before 2.1 gets released.

I'd highly recommend upgrading to the 2.0RC3 release. Its quite stable, and should be the last RC before 2.0 stable anyway. There are patches for 2.0 that you can apply for IPv6. Look around on the IPv6 pfsense board: http://forum.pfsense.org/index.php/board,52.0.html

1) Your tunnel endpoint address will not change, as it is not in either the routed /64 or the routed /48. You have a separate /64 for the tunnel.

3) To set up a BGP tunnel, you will need your own RIR-assigned ASN and PI space.

It is always a good idea to have a firewall somewhere along the line. The best way to think about it is.....take your IPv4 best-practices and apply them to IPv6.

I'd recommend setting up the firewall properly on your router. Then tunnel itself will go through your IPv4 firewall, which is the correct behavior. You should be applying firewall rules to your tunnel interface, though, so that traffic is properly firewalled.

Replace DEV with your device name and ADDR with the address you wish to depreciate, like so:

sudo ifconfig en0 inet6 2001:470::a9:1889:a6e7:ee07:1687 deprecated

Is there any particular reason you are using NAT instead of the /64 you get for free from the tunnel? And are you doing NAT-PT?