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

    FreeBSD sources for 2.7.0 missing?

    Scheduled Pinned Locked Moved General pfSense Questions
    13 Posts 5 Posters 1.4k 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.
    • R
      razzfazz
      last edited by

      (Cross posting from r/PFSENSE as suggested by u/netgate-rc.)

      I noticed that there does not appear to be a RELENG_2_7_0 branch (nor a tag) for the FreeBSD sources that correspond to the 2.7.0 release in the public pfSense FreeBSD-src repo. I do see new commits on the devel-main branch, as well as various older references to 2.7.0 in commit messages, but the actual hash that 2.7.0 was built from (686c8d3c1f0) does not appear to exist in the repo. Is there a plan to eventually publish a RELENG_2_7_0 branch, or will the FreeBSD sources for pfSense releases no longer be publicly available moving forward?

      rmonsterR N 2 Replies Last reply Reply Quote 2
      • rmonsterR
        rmonster @razzfazz
        last edited by

        I'd like to know as well since I have to rebuild a module but no sources are available

        R fabricioguzzyF 2 Replies Last reply Reply Quote 0
        • R
          razzfazz @rmonster
          last edited by

          The RELENG_2_7_0 branch was recently pushed to the public repo, including the hash that the release version was built from.

          1 Reply Last reply Reply Quote 3
          • fabricioguzzyF
            fabricioguzzy @rmonster
            last edited by

            @rmonster Are you compiling from the sources? There are 2 problems I am facing with the new 2.7.0 code.
            1- The php-pfsense-module - The build.sh script doesn't work anymore while trying to rename the php-pfsense-module. (I use a different brand name)
            2- There is a new package called "pfsense-repoc" that point to an internal Netgate URL, so it's not possible to compile it. This one is critical since one of the functions to update the repository is based on that binary file.

            I have opened a ticket on redmine pointing to the php-module-error - Still missing one related to that psense-repoc package now.

            Regards
            Fabricio.

            rmonsterR 1 Reply Last reply Reply Quote 0
            • rmonsterR
              rmonster @fabricioguzzy
              last edited by rmonster

              @fabricioguzzy Hey i just got done building my module. It's for the Mac mini Fan.

              I didn't have an issue when I copied the Git source to my freebsd vm and ran make.

              I copied the module to my Pfsense and it's loading up fine.

              https://github.com/pfsense/FreeBSD-src/tree/RELENG_2_7_0

              fabricioguzzyF NollipfSenseN 2 Replies Last reply Reply Quote 0
              • fabricioguzzyF
                fabricioguzzy @rmonster
                last edited by

                @rmonster OK, so you are compiling using the pfsense name. You didn't change the brand to something else, Am I right?
                The problem happens when you compile the code using a different name, not pfsense.

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

                  This thread is about the FreeBSD sources for 2.7.0; branding etc. isn’t relevant to those.

                  R fabricioguzzyF 2 Replies Last reply Reply Quote 0
                  • R
                    razzfazz @razzfazz
                    last edited by razzfazz

                    We are just building kernel modules (and, in my case, a modified miniupnpd binary).

                    My understanding is that rebranding is intentionally made difficult not being facilitated, because it’s not in Netgate’s interest; this isn’t new for 2.7.0, either.

                    1 Reply Last reply Reply Quote 0
                    • fabricioguzzyF
                      fabricioguzzy @razzfazz
                      last edited by

                      @razzfazz Sure, and it wasn't my intention to hijack your topic. Sorry about that.
                      yeah, I am aware of netgate making it difficult to rebrand, but one thing is being difficult, the other is being impossible (cause the code is not available). This is supposed to be a COMMUNITY edition, not a close-source.

                      R 1 Reply Last reply Reply Quote 0
                      • NollipfSenseN
                        NollipfSense @rmonster
                        last edited by

                        @rmonster said in FreeBSD sources for 2.7.0 missing?:

                        It's for the Mac mini Fan.

                        That's exactly why I jump ship on the Mac Mini to avoid the fan issue.

                        pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
                        pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

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

                          @fabricioguzzy No worries, I just meant to point out why we didn’t run I to the issue you mentioned.

                          AFAIK the issues with the build system referencing private repos have existed since before CE was even a thing.

                          1 Reply Last reply Reply Quote 0
                          • N
                            NicS @razzfazz
                            last edited by

                            @razzfazz Do the following:

                            git fetch origin RELENG_2_7_0
                            git checkout RELENG_2_7_0
                            
                            git rev-parse 686c8d3c1f0
                            686c8d3c1f043c03afbae4aac6068cf1778b0abf
                            
                            git checkout 686c8d3c1f043c03afbae4aac6068cf1778b0abf
                            
                            R 1 Reply Last reply Reply Quote 0
                            • R
                              razzfazz @NicS
                              last edited by

                              @NicS ?! I mentioned above that I saw the branch had been pushed?!

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