I think he is actually talking about this article in the documentation : http://doc.pfsense.org/index.php/Using_IPv6_on_2.0 I've got the same issue, but installing using snapshots from 2.1-dev is working :)

@joe_cowboy: Have you tried it or anybody else on your team with multiple broadband connections with each one assigned it's own IPv6 He.net broker tunnel?  Thanks again for your help Jim… As I mentioned above I have one on each of my WANs (DSL and Cable) and they both show online and I can ping out from each. It's not a general problem, at least not one I can reproduce here. I even have both setup with he.net dyndns updater entries to keep the tunnels up when my IPs change, they both track fine.

Thx Steve!

Im not sure if this is under 2.1…Im using 2.0.1..Sorry for the post if i posted it wrong again...

@sokolum: Thank you for your exploitation, but for an better understanding, does "would replace all of the binary" also mean it will downgrade my FreeBSD? yes

Locking this since http://forum.pfsense.org/index.php/topic,45487.0.html seems to have more active discussion.

jimp: dhatz was talking about a way to tell it to restore a snapshot of the configuration after a set period of time if the timeout isn't canceled within that period of time.  This is something to do when managing remotely if you are doing something that has a chance of accidentally locking yourself out if you make a mistake.

If you try it again, start a new thread with the errors. I would still expect packages to be problematic because there are likely lots of them out there that need updates for depreciated code (though that isn't fatal in most cases). Time to close out this thread since it's strayed way too far from the original topic.

Oops! Darn my self, forgot I was running from the live CD, so I installed 2.1 on the HD then upgraded,so no problem. Sorry for crying wolf too early!

@bmah: @jimp: We have a note about requiring ICMP here: http://doc.pfsense.org/index.php/Using_IPv6_on_2.0#Enable_ICMP but which other page were you thinking could use a note for that? The DynDNS config? Yes that's what I had in mind when I wrote that, but upon thinking about it, that won't help the people who just nail up their tunnelbroker configuration.  And this requirement for ICMP might not apply to all tunnelbrokers (sonic.net, my old ISP, supports IPv6 tunnels but they didn't have that requirement).  Finally I should have RTFM-ed.  So nevermind.  :-) Yeah, hard to find a good place for that outside of the doc wiki really. At the moment HE.net is the only tunnelbroker type in DynDNS so it might be worth mentioning there. Makes me wonder if somewhere there exists a list of which providers require ICMP… Might be time to make a spreadsheet like I had to make for FreeBSD wireless support. :-)

Unfortunately the patch fails to apply/build cleanly to PHP 5.3 so some work will be needed to get that going. http://redmine.pfsense.org/issues/2250

Before I aw this suggestion @Efonne: If you boot from the LiveCD it should be possible to fix it by mounting your root filesystem and running this command that comes from /tmp/post_upgrade_command, adding to the paths as appropriate for where you mounted it: tar xzpf /kernels/kernel_SMP.gz –exclude loader.conf -C /boot/ I had reinstalled 2.0.1. I decided to try changing /boot/kernel/pfsense_kernel.txt to SMP and then upgrade to 2.1. If the upgrade didn't work I could try booting the LiveCD and issuing the tar command. The firmware upgrade completed successfully and the subsequent reboot successfully booted FreeBSD 8.3-PRERELEASE.

@jimp: we just fixed it for good (we hope) in the builds tonight. Since the official snap servers aren't going, here's the first build any of us have made with the fix. (Fair warning: nobody has actually tried to use these images, they are fresh off the builder): http://files.chi.pfsense.org/jimp/2.1-8.3/ Thanks, you saved my morning. ;-) Consensus, do not git sync in the morning without checking the forum first. Regards // Jallee

Do you have DNS servers defined under System>General Setup? The DNS forwarder requires them, and you must statically configure them with a static WAN.

Thanks databeestje and jimp! The RLRENG8.3-branch is working fine, even IPv6 is up and running without any problems (had some configuration issues though). Thanks again.

Thanks again Jimp, I'll do my tests  :)