Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

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

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    15 Posts 7 Posters 16.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • jimpJ
      jimp Rebel Alliance Developer Netgate
      last edited by

      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.

      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        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?

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • R
          razzfazz
          last edited by

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

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            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.

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • R
              rt_rex
              last edited by

              Will there be wireless 802.11N support on RC 2.1 ?

              Don´t Try this @home go outside!
              WIFI Link @ 76 km
              Pfsense with 3G USB

              1 Reply Last reply Reply Quote 0
              • jimpJ
                jimp Rebel Alliance Developer Netgate
                last edited by

                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.

                Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                Need help fast? Netgate Global Support!

                Do not Chat/PM for help!

                1 Reply Last reply Reply Quote 0
                • rcfaR
                  rcfa
                  last edited by

                  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…

                  1 Reply Last reply Reply Quote 0
                  • jimpJ
                    jimp Rebel Alliance Developer Netgate
                    last edited by

                    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

                    Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                    Need help fast? Netgate Global Support!

                    Do not Chat/PM for help!

                    1 Reply Last reply Reply Quote 0
                    • rcfaR
                      rcfa
                      last edited by

                      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?

                      1 Reply Last reply Reply Quote 0
                      • jimpJ
                        jimp Rebel Alliance Developer Netgate
                        last edited by

                        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.

                        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                        Need help fast? Netgate Global Support!

                        Do not Chat/PM for help!

                        1 Reply Last reply Reply Quote 0
                        • rcfaR
                          rcfa
                          last edited by

                          @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?

                          1 Reply Last reply Reply Quote 0
                          • jimpJ
                            jimp Rebel Alliance Developer Netgate
                            last edited by

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

                            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                            Need help fast? Netgate Global Support!

                            Do not Chat/PM for help!

                            1 Reply Last reply Reply Quote 0
                            • R
                              Roots0
                              last edited by

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

                              Mobile Computer & Network Support Stockport, UK
                              www.timotten.co.uk

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post
                              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.