HEADS UP: 2.1-RELEASE coming - don't forget to fix your update URL!


  • Rebel Alliance Developer Netgate

    For those of you that were tracking 2.1 snapshots: Now that 2.1-RELEASE is almost ready to drop the snapshots updates are down and the -RELEASE version will not be on the snapshots server but the main/official update server.

    You must go to the firmware settings and choose the "stable updates" URL for your architecture to receive the -RELEASE update via auto update.

    So in summary:

    • System > Firmware, Updater Settings tab

    • From the drop-down, pick "pfSense <i386 amd64="">stable updates (Current Architecture)" whichever shows "Current Architecture" for you. Verify against the architecture shown on the dashboard if you like.</i386>

    • Uncheck "Unsigned images" (the -RELEASE images will be signed)

    – At this point, you may perform the upgrade as desired.

    After the upgrade has been performed and you are on 2.1-RELEASE, the default URL there will be the stable updates, so you can then uncheck "Use a URL server for firmware upgrades other than www.pfsense.org" at that point in time.



  • Not working for me are we still waiting for the upgrade or should this method be working right now


  • Rebel Alliance Developer Netgate

    It is not up yet. Note that it says "coming" and "almost ready"

    There will be an announcement when it is actually ready.

    Neither the snapshots nor the stable updates will get you any 2.1 image right now.



  • Ok thanks



  • I use the following URL from the updater configuration:

    http://updates.pfsense.org/_updaters/amd64

    It tells me, I am on the lastest version. The last update was done on 30th August, 2013. Is that really the latest version?

    The snapshot server messages report a version 10th September, but this a corrupt file (only containing the date). Couldn't the updater report something more meaningful. E.g.: stable updates are out, change url?

    Regards, so long and thanks for all the pf-fish;)



  • Steady there guy…  Steady...  Wait for it.


  • Rebel Alliance Developer Netgate

    @epek:

    I use the following URL from the updater configuration:

    http://updates.pfsense.org/_updaters/amd64

    It tells me, I am on the lastest version. The last update was done on 30th August, 2013. Is that really the latest version?

    The snapshot server messages report a version 10th September, but this a corrupt file (only containing the date). Couldn't the updater report something more meaningful. E.g.: stable updates are out, change url?

    Regards, so long and thanks for all the pf-fish;)

    Please read the entire thread carefully. This has already been explained.



  • Hi jimp

    All update went well, and all the steps you mentioned above are taken.

    Firmware Settings page:-

    But on the Dashboard shows Unable to check for updates:-

    Wondering if I am missing anything here.

    Thank you


  • LAYER 8 Global Moderator

    I believe cmb is working on the updater- from this he stated he has blocked public access to it.

    http://forum.pfsense.org/index.php/topic,66566.msg363251.html#msg363251



  • @johnpoz:

    I believe cmb is working on the updater- from this he stated he has blocked public access to it.

    http://forum.pfsense.org/index.php/topic,66566.msg363251.html#msg363251

    Noted, thank you.



  • Sorry, but my version does not have any pull down under "Updater Settings"?

    I have a FIRMWARE BRANCH with a field to enter a URL for a update server other than www.pfsense.org and then a UPDATES section with unsigned images and Dashboard check.

    So what I am suppose to change? I understand that the update server might be down, but want to make sure I have the right settings once its up. I am currently on 2.1-RC0 (amd64) built on Fri May 31 09:12:16 EDT 2013

    Note, it takes about 2 minutes to bring up the "updater Sesstings" tab for some reason? so not sure if thats why I dont have any pull down?

    @jimp:

    So in summary:

    • System > Firmware, Updater Settings tab

    • From the drop-down, pick "pfSense <i386 amd64="">stable updates (Current Architecture)" whichever shows "Current Architecture" for you. Verify against the architecture shown on the dashboard if you like.</i386>

    • Uncheck "Unsigned images" (the -RELEASE images will be signed)

    After the upgrade happens and you are on 2.1-RELEASE, the default URL there will be the stable updates, so you can then uncheck "Use a URL server for firmware upgrades other than www.pfsense.org" at that point in time.



  • @iculookn:

    Sorry, but my version does not have any pull down under "Updater Settings"?

    I have a FIRMWARE BRANCH with a field to enter a URL for a update server other than www.pfsense.org and then a UPDATES section with unsigned images and Dashboard check.

    So what I am suppose to change? I understand that the update server might be down, but want to make sure I have the right settings once its up. I am currently on 2.1-RC0 (amd64) built on Fri May 31 09:12:16 EDT 2013

    Note, it takes about 2 minutes to bring up the "updater Sesstings" tab for some reason? so not sure if thats why I dont have any pull down?

    @jimp:

    So in summary:

    • System > Firmware, Updater Settings tab

    • From the drop-down, pick "pfSense <i386 amd64="">stable updates (Current Architecture)" whichever shows "Current Architecture" for you. Verify against the architecture shown on the dashboard if you like.</i386>

    • Uncheck "Unsigned images" (the -RELEASE images will be signed)

    After the upgrade happens and you are on 2.1-RELEASE, the default URL there will be the stable updates, so you can then uncheck "Use a URL server for firmware upgrades other than www.pfsense.org" at that point in time.

    Because the updater server is offline right now, it doesn't even serve out the list of update options (versions by architecture). The webGUI takes quite a while to timeout, waiting for that data to arrive, like you say. I suspect there is not really much that can be done until the update server is back online.
    If you want to upgrade, you can download an upgrade file from one of the mirrors, save it on a local disk, and use manual upgrade to apply it.



  • @jimp:

    For those of you that were tracking 2.1 snapshots: Now that 2.1-RELEASE is almost ready to drop the snapshots updates are down and the -RELEASE version will not be on the snapshots server but the main/official update server.

    You must go to the firmware settings and choose the "stable updates" URL for your architecture to receive the -RELEASE update via auto update.

    So in summary:

    • System > Firmware, Updater Settings tab

    • From the drop-down, pick "pfSense <i386 amd64="">stable updates (Current Architecture)" whichever shows "Current Architecture" for you. Verify against the architecture shown on the dashboard if you like.</i386>

    • Uncheck "Unsigned images" (the -RELEASE images will be signed)

    After the upgrade happens and you are on 2.1-RELEASE, the default URL there will be the stable updates, so you can then uncheck "Use a URL server for firmware upgrades other than www.pfsense.org" at that point in time.

    I did not understand
    I currently have Version

    2.0.3-RELEASE (i386)
    built on Fri Apr 12 10:22:57 EDT 2013
    FreeBSD home.plex 8.1-RELEASE-p13 FreeBSD 8.1-RELEASE-p13 #1: Fri Apr 12 10:50:43 EDT 2013 root@snapshots-8_1-i386.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 i386

    Is the details on the screen ok or need to change something ?




  • Looks good…


  • Rebel Alliance Developer Netgate

    @firefox:

    I did not understand
    I currently have Version

    2.0.3-RELEASE (i386)
    built on Fri Apr 12 10:22:57 EDT 2013
    FreeBSD home.plex 8.1-RELEASE-p13 FreeBSD 8.1-RELEASE-p13 #1: Fri Apr 12 10:50:43 EDT 2013 root@snapshots-8_1-i386.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 i386

    Is the details on the screen ok or need to change something ?

    If you are on 2.0.3, then you were not tracking 2.1 snapshots as stated in the message I posted, so there isn't anything that needs changing. You can make the change if you like, it would still work, it's just not required.


  • Banned

    Since noone asked yet… gitsync stays at RELENG_2_1 ? :)


  • Rebel Alliance Developer Netgate

    @doktornotor:

    Since noone asked yet… gitsync stays at RELENG_2_1 ? :)

    For 2.1.x, yes. There isn't any real compelling reason to do gitsync anytime soon though.


Log in to reply