Netgate SG-1000 microFirewall

Author Topic: IPv6 code merged to mainline!  (Read 29419 times)

0 Members and 1 Guest are viewing this topic.

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21486
  • Karma: +1456/-26
    • View Profile
IPv6 code merged to mainline!
« on: July 13, 2011, 08:02:46 am »
Because the 2.0 code was branched into RELENG_2_0 and mainline was opened back up for major changes, it was time to merge the IPv6 code into mainline to start paving the road for 2.1. (And there was much rejoicing, yay!)

As of this morning, the merge is complete, and the IPv6 code is in the pfsense code repository on the master branch (mainline).

2.0 snapshots are not built from mainline, but from RELENG_2_0 so a gitsync is still needed to get IPv6 onto current snapshots. You can use the standard pfsense repo with the "master" branch for gitsync at this stage to have the same net effect as following the previous IPv6 repository.

Once 2.0 is released the snapshots will start building from mainline again and IPv6 will not require any special settings of syncing at that point.
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline iFloris

  • Full Member
  • ***
  • Posts: 172
  • Karma: +1/-0
  • one layer of information removed
    • View Profile
    • Small personal site
Re: IPv6 code merged to mainline!
« Reply #1 on: July 13, 2011, 08:07:52 am »
This is great news!
one layer of information
removed

Offline tebeve

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
    • View Profile
Re: IPv6 code merged to mainline!
« Reply #2 on: July 13, 2011, 10:13:58 am »
Sorry, not ultra familiar with the whole git process...

So would I just change my auto gitsync repo on system -> firmware -> updater settings

from:
git://github.com/smos/pfsense-ipv6.git
to:
git://github.com/bsdperimeter/pfsense.git


Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21486
  • Karma: +1456/-26
    • View Profile
Re: IPv6 code merged to mainline!
« Reply #3 on: July 13, 2011, 10:30:39 am »
Yep, that's it. Branch is master in either case there, just the URL changes.
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline tebeve

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
    • View Profile
Re: IPv6 code merged to mainline!
« Reply #4 on: July 13, 2011, 10:31:33 am »
roger that, thanks Jim!

Offline lostcontrol

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
    • View Profile
Re: IPv6 code merged to mainline!
« Reply #5 on: July 15, 2011, 03:54:53 am »
Once 2.0 is released the snapshots will start building from mainline again and IPv6 will not require any special settings of syncing at that point.

No chance to setup an additional snapshot build for mainline? I guess there will still be daily snapshot for the RELENG_2_0 branch once 2.0.0 is released so having daily mainline snapshots too would be good. Thanks.

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21486
  • Karma: +1456/-26
    • View Profile
Re: IPv6 code merged to mainline!
« Reply #6 on: July 15, 2011, 07:22:30 am »
No interest in that right now from the devs that I know of, the amount of CPU and hdd space consumed by the process makes it a bit cumbersome. We'd rather be concentrating on getting 2.0 out at this point, and this will be a moot point. We may occasionally crank out a single set, but nothing regular.
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline Jason Litka

  • Hero Member
  • *****
  • Posts: 1294
  • Karma: +53/-1
    • View Profile
    • Utter Ramblings
Re: IPv6 code merged to mainline!
« Reply #7 on: July 28, 2011, 10:26:44 am »
Is there a roadmap for what you plan to get into 2.1 (other than IPv6, I mean)?
I can break anything.

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21486
  • Karma: +1456/-26
    • View Profile
Re: IPv6 code merged to mainline!
« Reply #8 on: July 28, 2011, 10:29:45 am »
It's not set in stone, but here is a good idea:

http://redmine.pfsense.org/projects/pfsense/roadmap
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline tebeve

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
    • View Profile
Re: IPv6 code merged to mainline!
« Reply #9 on: September 19, 2011, 11:10:51 am »
Once 2.0 is released the snapshots will start building from mainline again and IPv6 will not require any special settings of syncing at that point.

Just so I'm clear, should we still be using http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_RELENG_2_0/.updaters/ for our update URL and just untick the auto gitsync section now that 2.0 release is out?

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21486
  • Karma: +1456/-26
    • View Profile
Re: IPv6 code merged to mainline!
« Reply #10 on: September 19, 2011, 11:25:29 am »
There will be changes coming in that regard. The 2.1 builds will switch to FreeBSD 9 shortly so there may be some instability there and once we pass that point it will become more and more difficult to overlay the code as we currently do. It may be impossible (and damaging) to keep syncing once we cross that line. The pf rule syntax will change from 8 to 9 so once that commit drops you would not want to gitsync the 2.1 code on top of a 2.0 binary set.

At the moment I would stick with 2.0-RELEASE and gitsync the code manually if you really need an update. I'm sure we'll announce more when the time comes for more changes.
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline tebeve

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
    • View Profile
Re: IPv6 code merged to mainline!
« Reply #11 on: September 19, 2011, 12:46:40 pm »
Thanks Jim, I'll do as you suggest... I was just looking for the best way to keep my IPv6 code as fresh as possible.

Sorry to be so dense, but will just upgrading to 2.0-RELEASE keep my IPv6 settings?

Currently I'm on:
2.1-DEVELOPMENT (i386)
built on Mon Sep 5 04:07:51 EDT 2011

Which now tells me I'm "on the latest version" from auto updater.

Or will I need to gitsync once to get IPv6 support back after an upgrade to 2.0-RELEASE?

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21486
  • Karma: +1456/-26
    • View Profile
Re: IPv6 code merged to mainline!
« Reply #12 on: September 19, 2011, 01:25:15 pm »
You'll likely want to keep your gitsync settings in place for the moment, and run a normal firmware update. Thinking about how the checks are done the official update for automatic upgrades checks the version number not the date so since you are on "2.1-DEVELOPMENT" it considers that newer than 2.0-RELEASE.

It will definitely need to gitsync after applying the 2.0 update.

I'll likely be making a set of update files soon that will make it a little easier. I haven't made a new set of images since 2.0-RELEASE happened.
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline tebeve

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
    • View Profile
Re: IPv6 code merged to mainline!
« Reply #13 on: September 19, 2011, 03:20:38 pm »
OK, well maybe I'll just sit tight on the snap I'm on and do manual getsyncs for the time being if need be.

No rush at all, but could you give a heads up when you have the new update files ready and I'll just go that route? Or do you think it would behoove me to move off of the 2.1-DEVELOPMENT Snaps if all I'm looking for is the IPv6 portion of the code?

I'm happy to help test, but I'm not sure I want to take the early stages ride of 2.1 on this particular machine.

Thanks for all your time, Jim.

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21486
  • Karma: +1456/-26
    • View Profile
Re: IPv6 code merged to mainline!
« Reply #14 on: September 19, 2011, 03:50:07 pm »
I'll probably forget to post about it, but you can always just keep an eye on http://files.pfsense.org/jimp/ipv6/
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!