@jimp:

Netflix turned on IPv6 for streaming, so I bet he.net and friends are really feeling a bit of a bandwidth spike. :-)

I've been expecting the day that happens is the day they stop offering free IPv6 tunnels (as tons of people outside the US will start using it to have US IPs), so we'll see. They do appear to put a 1 Mb limit on the tunnels at least at times, sometimes I can get 10+ Mbps, sometimes it flatlines right at 1 Mb, so that's not all that useful for Netflix given the highest quality SD stream seems to be around 3-4 Mbps continuous.

I did a whitelist for pfBlocker, will test when it changes IP (is working fine atm).

Also, Snort isn't showing any IPv6 attack, only IPv4.  So it needs to gets updated.

Got my fiber installed today, finally. 6RD worked like a charm, so obviously my problems were related to PPP for some reason. I'm happy, but if you'd like to continue to pursue this and need any more data from me, just let me know.

Thanks.

@cmb:

NAT is the most common solution there. Or if you have a requirement for public IPs directly on servers, a separate private subnet on a VLAN. Best to isolate hosts that are publicly reachable and those that aren't anyway.

Thanks fort he advice - added in a separate NIC onto PFsense and made a separate network for servers requiring public IPs. Works fine. Only thing is I needed to set a manual oubound NAT rule for the private IPv4 interface range

Yes there are now official snapshots, we have not blessed a particular one for general consumption though, although we do have fixed a largish list of bugs.

You can find them at http://snapshots.pfsense.org

Yup should work fine  :D

To update this:

I think it ended up being the IPv6 Ping website I was using located in Denmark. I've since tried other ones and the ping seems to be working correctly.

Thank you for your responses.

Known issue

http://redmine.pfsense.org/issues/2129

ls -l /usr/local/pkg see if there is a file there that you don't recognize.

now I have setup Multi-ipv6 tunnels in adsl.  using config the Static Routes and NTP show all ipv6 tunnels online.

but only out visit work, the second ipv6 can't visit from internet. I want to setup multi-ipv6 network, when one ipv6 slow then change use the second ipv6 for my web server etc.

I think should allow setup multi ipv6 network address for the same LAN?

I can offer login my router account. if your need it.

:-[
I think i must wake myself up… [slaps myself in the face]

Thanks for the quick replay…

After making changes on the state and reboot it for 2x, the box freezed :( I saw no errors. I cant even connect to ssh pf menu.. Ill reformat it now and use the latest snapshot http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/i386/pfSense_HEAD/livecd_installer/pfSense-LiveCD-2.1-DEVELOPMENT-i386-20120409-1444.iso.gz

Ok, thanks again.

Regarding gif interfaces. I now figured out how to do 6to4 using gif instead of stf0/stf1.
I am unsure wheter the /48 prefix instead of /16 will increase the latency. I still have to figure out how to circumvent this.

I followed http://ipv6int.net/systems/freebsd-ipv6.html and configured pfsense using the webinterface accordingly.

interfaces/assign/gif/"+".
wan/gif remote address: 192.88.99.1
gif tunnel local address: 2002:[myipv4address]::
gif tunnel remote address: 2002:c058:6301::/128
save.
Then I created an opt interface, assigned gif 192.88.99.1 and configured ipv6 only with an address of gif tunnel local address: 2002:[myipv4address]::1/48

Following the same method for the other interface, while the first is using a default gateway of ::192.88.99.1 and the other just a gateway of ::192.88.99.1 did the trick.

I am still investigating…

I have test for PPPoE in ipv6 tunnel MTU is 1420.

@Matthias:

I'm not sure this can be marked solved as there really isn't an answer as to why this was happening. I seem to be having the same issue right now ever since upgrading to the latest snapshots. I'll randomly lose my IPv6 connectivity, the gateway is still up and I can ping ipv6 addresses from the firewall but not from any of my LAN workstations. My last known working config was the pfSense-Full-Update-2.1-DEVELOPMENT-i386-20111125-1741.tgz

post info in a new thread, there are countless reasons this can happen and it's not likely yours is the same as the OP's. HE.net has been flaky for me of late, you may be seeing the same, or there may be some kind of issue. Post a new thread with traceroute6 output from a LAN host when it's not working.

Split this off the old thread because it's really different (the old thread was many months old).

What mask were you using when setting up the interface? I haven't seen it change a ::2 into a ::1 myself.