IPv6 code merged to mainline!

[iFloris]

This is great news!

[tebeve]

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

[jimp]

Yep, that's it. Branch is master in either case there, just the URL changes.

[tebeve]

roger that, thanks Jim!

[lostcontrol]

@jimp:

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.

[jimp]

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.

[jasonlitka]

Is there a roadmap for what you plan to get into 2.1 (other than IPv6, I mean)?

[jimp]

It's not set in stone, but here is a good idea:

http://redmine.pfsense.org/projects/pfsense/roadmap

[tebeve]

@jimp:

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?

[jimp]

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.

[tebeve]

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?

[jimp]

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.

[tebeve]

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.

[jimp]

I'll probably forget to post about it, but you can always just keep an eye on http://files.pfsense.org/jimp/ipv6/

[jonnytabpni]

@jimp:

I'll probably forget to post about it, but you can always just keep an eye on http://files.pfsense.org/jimp/ipv6/

Hi Jimp,

What's the difference between the -DEVELOPMENT and Full-Update-2.1-DEVELOPMENT files?

Thanks

[jimp]

The same as with any other snapshots or files… the iso is the livecd, nanobsd are for embedded, full updates are update files for full installs, etc.

[MrKoen]

When I do a manual gitsync using the console developer shell from git://github.com/pfsense/pfsense.git and do a reboot, after the reboot my IPv6 connectivity is no longer working. When I go back into the console developer shell and gitsync from git://github.com/smos/pfsense-ipv6.git again followed by a reboot, IPv6 works again.

In both situations I'm left with the following crash notice on the pfSense dashboard:

pfSense has detected a crash report or programming bug. Click here for more information.

Crash report begins.  Anonymous machine information:

amd64
8.1-RELEASE-p4
FreeBSD 8.1-RELEASE-p4 #1: Mon Jul  4 16:48:26 EDT 2011     root@FreeBSD_8.0_pfSense_2.0-AMD64.snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8

Crash report details:

When I try to upload the crash report, I get the following notice:

Diagnostics: Crash reporter

Processing…

Uploading...

minfree only report received. Skipping. This was fixed in a recent snapshot.

Any clues?

[johnpoz]

Just did a sync and not having any issue
Current repository is git://github.com/pfsense/pfsense.git

===> Fetching updates…
remote: Counting objects: 153, done.
remote: Compressing objects: 100% (87/87), done.
remote: Total 118 (delta 91), reused 57 (delta 30)
Receiving objects: 100% (118/118), 13.95 KiB, done.
Resolving deltas: 100% (91/91), completed with 28 local objects.
From git://github.com/pfsense/pfsense
  783321d..6daf497  RELENG_2_0 -> origin/RELENG_2_0
  abf421c..22aaee7  master     -> origin/master
===> Installing new files...
===> Removing FAST-CGI temporary files...
===> Upgrading configuration (if needed)...
===> Configuring filter...
===> Running /etc/rc.php_ini_setup...
===> Locking down the console if needed...
===> Signaling PHP and Lighty restart...
===> Checkout complete.

Your system is now sync'd and PHP and Lighty will be restarted in 5 seconds.

Currently running
2.1-DEVELOPMENT (i386)
built on Fri Oct 21 12:51:56 EDT 2011
FreeBSD 8.1-RELEASE-p6

Ipv6 works just fine after sync from client machines on my network, and the pfsense box - tunnel shows up, etc. etc.
C:\Windows\System32>ping ipv6.google.com

Pinging ipv6.l.google.com [2607:f8b0:4001:c01::93] with 32 bytes of data:
Reply from 2607:f8b0:4001:c01::93: time=47ms
Reply from 2607:f8b0:4001:c01::93: time=44ms
Reply from 2607:f8b0:4001:c01::93: time=50ms
Reply from 2607:f8b0:4001:c01::93: time=45ms

Ping statistics for 2607:f8b0:4001:c01::93:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 44ms, Maximum = 50ms, Average = 46ms

[MrKoen]

johnpoz, did you also do a reboot after the gitsync? That's where things go wrong here. Everything seems to be working: tunnel is up and active, but each ping results in no route to destination found. When I just do a gitsync and not reboot, it remains working.

[johnpoz]

Normally I do not reboot after a gitsync, but to make you happy I just did after reading your response

And working just fine
[2.1-DEVELOPMENT][root@pfsense.local.lan]/root(9): uptime
7:06AM  up 2 mins, 2 users, load averages: 0.58, 0.45, 0.19

[2.1-DEVELOPMENT][root@pfsense.local.lan]/root(11): ping6 ipv6.google.com
PING6(56=40+8+8 bytes) 2001:470:1f10:b85::2 –> 2607:f8b0:4001:c01::69
16 bytes from 2607:f8b0:4001:c01::69, icmp_seq=0 hlim=56 time=45.867 ms
16 bytes from 2607:f8b0:4001:c01::69, icmp_seq=1 hlim=56 time=46.064 ms
^C
--- ipv6.l.google.com ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 45.867/45.965/46.064/0.098 ms

ipv6 gateway shows up, booted without errors, etc. etc..

Now I have seen those weird crash errors now and then after a gitsync, and can not make the thing go away on the web gui -- everything seems to be working.  After a reboot those errors are gone, but this just happens every now and then.  For example this last gitsync it did not happen.