HEADS UP: 2.1-RC0 Branched, you MUST fix your update URL.

dhatz

To see the RC0 snapshot as an upgrade, you'll need to visit System > Firmware on the Updater Settings tab, and either pick the 2.1-RC entry form the drop-down, or change HEAD to RELENG_2_1 in your update URL. Once that change has been saved, Auto Update will pick up RC0.

So the System > Firmware > Settings > Firmware Auto Update URL needs to be either:
http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/i386/pfSense_RELENG_2_1/.updaters
http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_RELENG_2_1/.updaters
(i386/amd64 depending on your architecture)

jimp

Yes, that's right, either one of those.

I updated my first post in the thread with some other info. Notably the warning for gitsync after update being harmful.

phil.davis

On my systems, the Default Auto Update URLs dropdown does not show 2.1-RC. It only shows the usual "stable updates" and "2.1 Development" options. I thought that the dropdown list is built at run-time from an online source, so should do its thing automatically. Am I missing something or?

razzfazz

Seeing the same thing on my embedded install; works fine on a full install, though.

jimp

There were a couple instances of the manifest file on servers that I didn't get to update earlier, they should be OK now.

The drop-down menus should be showing an RC choice for everyone now, no matter which mirror gets hit.

rt_rex

Will there be wireless 802.11N support on RC 2.1 ?

jimp

That wouldn't have changed from the betas. There are a few cards that support 802.11n mode, but none that do full 802.11n rates.

That should come in 2.2. Either way it's off-topic for this thread.

rcfa

In the dashboard the latest build still shows up as "2.1-BETA1 (amd64)" and not as I would have expected as something like "2.1-RC0 (amd64)"
So given that it was already called BETA1 before I changed the updater URL, I wonder if it actually got the proper build…

jimp

It does not. Either your system is not really updating, or you have some other problem (such as gitsync-after-update with an old/invalid git repo URL)

Current snapshots show:

2.1-RC0 (amd64)
built on Wed May 29 04:53:18 EDT 2013
FreeBSD pfsense-amd64.localdomain 8.3-RELEASE-p8 FreeBSD 8.3-RELEASE-p8 #1: Wed May 29 05:26:02 EDT 2013 root@snapshots-8_3-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64

rcfa

Well, I have these:

http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_RELENG_2_1/.updaters

and for gitsync:
git://github.com/bsdperimeter/pfsense.git
with branch:
RELENG_2_1

and the dashboard reports this:

2.1-BETA1 (amd64)
built on Wed May 29 04:53:18 EDT 2013
FreeBSD 8.3-RELEASE-p8

You are on the latest version.

Anything wrong with what I got there?

jimp

That is the wrong URL. It should be /pfsense/ not /bsdperimeter/, it moved a couple months back. You should not be using gitsync-after-update anymore anyhow.

rcfa

@jimp:

That is the wrong URL. It should be /pfsense/ not /bsdperimeter/, it moved a couple months back. You should not be using gitsync-after-update anymore anyhow.

Ah, OK, that would help….
...must have missed that change. Maybe something that would be useful in the sticky section.

Do I have to also follow the steps in the section: "Git URL Moved" described here: http://doc.pfsense.org/index.php/Updating_pfSense_code_between_snapshots
or does that only apply when the actual site changes, i.e. pre-github to github change?

jimp

Yes, you need to follow the steps on the page.

Roots0

Thanks, I was wondering why I was't seeing new builds.