Manual install using gitsync
-
I did a full install of pfsense 2.0-RC1 and then followed the manual to do a gitsync install of ipv6
when I look at the version of my firewall it says
2.0-RC2-IPv6
Built On: Sat Feb 26 16:33:51 EST 2011any reason RC1 went to RC2?
-
The main pfSense code is at RC2 now which was merge into the IPv6 Code
-
ohh cool
do you recommend me running the latest upgrade snapshot
from build: Sat Feb 26 16:33:51 EST 2011
to Sun May 15 21:22:15 EDT 2011
and then gitsync?
-
I would upgrade your snapshot then gitsync. I usually update my snapshot every 2-3 weeks and haven't had an issue. A lot of changes have happen to the binaries which you can only get by doing a snapshot update.
Remember, a snapshot can break a system so make sure you have a backup of your config. Its highly unlikely but could happen.
-
ok thanks for your help
one last question…will pfsense officially support this ipv6 hacked version (meaning will i be able to easily upgrade to a supported version in the future when it is official?) in the future (merge it into their code)? From what you said above, has the merge already happened?
-
ok thanks for your help
one last question…will pfsense officially support this ipv6 hacked version (meaning will i be able to easily upgrade to a supported version in the future when it is official?) in the future (merge it into their code)? From what you said above, has the merge already happened?
Your welcome. IPv6 isn't officially supported by the core dev team yet. databeestje is the dev that is actively working on the IPv6 branch and does provide support. The other dev seem to be helping out also. Once pfSense 2.0 become an official release and not a RC, i foresee them merging the IPv6 code to make a pfsense 2.1 beta.
What I meant by merge, every week or 2 the main code of pfsense is merge into the IPv6 branch. If this wasn't done, we would have a IPv6 code but the main pfsense code would be months behind. This allows us to have IPv6 functionally and keep up-to-date with the main code.
-
Cino has it just about right. Once 2.0 ships the current ipv6 code from databeestje will likely be pulled in and used as the basis for 2.1 from that point. Obviously many other things will go in to make 2.1 proper, but that will be a good starting point to jump ahead on ipv6. The current ipv6 code is periodically synced up with 2.0 proper to make sure there isn't too much divergence between them.
Many of us devs are running the ipv6 code on routers in various places trying to help track down issues. I run it at home on my router and use a he.net tunnel, it works great for me (aside from some dhcpd issues which have probably been fixed since my last sync.)