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

    Building pfSense 2.2 / FreeBSD 10.1 - WORKING STEPS

    Development
    14
    50
    20.9k
    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.
    • S
      S. Kirschner
      last edited by

      Ok thats are some points why the pkg method gets a +  :)

      But I try it with a pbi , for following reason:
      1.keep the usability of the webinterface for that software
      2.keep the possability to update the software later via the webinterface without "tons" of old useless files
      3.publish my expierence in the forum, that other got an better idea how it works and maybe faster an update for that software could be published to all via the offical repo.

      The software i try to build is the latest version of squid 3 (which is actual the version 3.5.8 and the latest (not fully offical) available version for pfsense is 3.5.3 at the moment).
      And i hope if its get working that the offical version of squid 3 got updated for pfsense that all other could use the new features.

      At the moment I stuck a bit with the default prefix path.

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        That's just completely wrong reason. The usability with the web GUI will be much better if you avoid PBI completely. With huge things like this, probably some 1/3 of the code could be dropped altogether if there was no PBI in the first place. Huge part of the rest could be simplified and made much less buggy.

        Squid 3.5.x is already compiled as PBI (https://files.pfsense.org/packages/10/All/). Upgrade never happened mostly likely because

        • it'd require another round of insane hacking around the PBI screwed paths in the XML/PHP package (the webGUI)
        • the whole binary thing doesn't work properly anyway

        If you want to work on Squid 3.5.x GUI integration

        • install Squid via pkg
        • take the current package code - https://github.com/pfsense/pfsense-packages/tree/master/config/squid3/34
        • fix the package code so that it points to the sane paths under the /usr/local prefix, ditching all the PBI and pfSense-version specific shit/generally useless garbage (if,else,blah…)
        1 Reply Last reply Reply Quote 0
        • S
          S. Kirschner
          last edited by

          @doktornotor:

          Squid 3.5.x is already compiled as PBI (https://files.pfsense.org/packages/10/All/). Upgrade never happened mostly likely because

          • it'd require another round of insane hacking around the PBI screwed paths in the XML/PHP package (the webGUI)
          • the whole binary thing doesn't work properly anyway

          What I dont get is , I think between 3.5.3 and 3.5.9 didnt changed so much in the file structure,
          why the person who build 3.5.3 couldnt fetch the new files and build 3.5.9 ?

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned
            last edited by

            Hmm? Why'd you waste hours of time building something that ain't gonna be used anywhere?

            1 Reply Last reply Reply Quote 0
            • S
              sreekupmgmail.com
              last edited by

              @PiBa:

              Hi sreekupm,

              Step 1: READ the posts above yours !
              Step 2: read some more forum posts, try to do the steps, then read some more.
              Step 3: fail while trying those steps, then try to understand the error's show, gather logfiles, look in those logs for clues what might have gone wrong.
              Step 4: search the forum and use google to find possible solutions to your problems..
              Step 5: try those possible solutions.
              Step 6: repeat above steps 3 times (or more..)

              Step 7: then, and only then, clearly explain what you have done, tried and failed at, what errors you have seen, what step you could not follow..

              Now please follow these instructions and you might get a more useful reply next time..

              Some computer knowledge and is expected from a developer so we are not going to tell every mouse click you need to do..
              What would you say when i report you the problem that the program/website you created is not working properly? Wouldn't you like to know what button&page i was talking about and what behavior i expected but didn't get?

              I'm sorry if i sound a bit harsh, but please do understand that your question is useless like it is currently written..

              Regards,
              PiBa-NL

              I had done above steps but stuck up here what I can do?

              [2.2.4-RELEASE][admin@pfSense.localdomain]/home/pfsense: git clone -b RELENG_2_2 git@github.com:pfsense/pfsense-tools.git tools
              Cloning into 'tools'…
              Permission denied (publickey).
              fatal: Could not read from remote repository.

              Please make sure you have the correct access rights
              and the repository exists.

              1 Reply Last reply Reply Quote 0
              • P
                PiBa
                last edited by

                Surely you did not do "step7: clearly explain what you have done, tried and failed at".
                Anyway..

                So, did you sign the ICLA or CCLA and the LA for the pfSense portal ? Did you recieve a email that you added to the pfsense-tools team? Did you configure your public ssh key to github?

                1 Reply Last reply Reply Quote 0
                • S
                  sreekupmgmail.com
                  last edited by

                  Hi PiBa

                  I already sign Individual CLA - Lifetime

                  I am stuck up
                  root@develop:/usr/ports/devel/git # cd /home/pfsense && git clone git@git.pfsense.org:pfsense-tools tools
                  Cloning into 'tools'…
                  The authenticity of host 'git.pfsense.org (208.123.73.74)' can't be established.
                  ECDSA key fingerprint is 52:7b:22:f9:3b:7e:dd:85:85:1a:a5:98:b8:8f:7f:62.
                  No matching host key fingerprint found in DNS.
                  Are you sure you want to continue connecting (yes/no)? yes
                  Warning: Permanently added 'git.pfsense.org' (ECDSA) to the list of known hosts.
                  Password:  Which Password??
                  Password for git@git.pfsense.org: Which Password??
                  Password:
                  Password for git@git.pfsense.org:
                  Password:
                  Password for git@git.pfsense.org:
                  Permission denied (publickey,keyboard-interactive).
                  fatal: Could not read from remote repository.

                  Please make sure you have the correct access rights
                  and the repository exists.

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

                    pfsense-tools moved onto GitHub as a private repo a while ago. After completed the CLA you should have it as a repo in GitHub. That GitHub repo has the RELENG_2_2 branch from which you should be able to clone and build 2.2.* …

                    I guess the CLA signup code is no longer automagically adding access to the git.pfsense.org:pfsense-tools repo?

                    @cmb @jimp ?

                    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
                    • P
                      PiBa
                      last edited by

                      @sreekupm@gmail.com:

                      I had done above steps but stuck up here what I can do?
                      [2.2.4-RELEASE][admin@pfSense.localdomain]/home/pfsense: git clone -b RELENG_2_2 git@github.com:pfsense/pfsense-tools.git tools
                      Cloning into 'tools'…
                      Permission denied (publickey).
                      fatal: Could not read from remote repository.

                      Some questions where asked after you asked that.
                      @PiBa:

                      • So, did you sign the ICLA or CCLA and the LA for the pfSense portal ?
                      • Did you recieve a email that you added to the pfsense-tools team?
                      • Did you configure your public ssh key to github?

                      Which you did not answer..

                      @sreekupm@gmail.com:

                      I am stuck up
                      root@develop:/usr/ports/devel/git # cd /home/pfsense && git clone git@git.pfsense.org:pfsense-tools tools
                      Cloning into 'tools'…

                      Indeed you are.. And probably will be for a while longer.. Why now try and clone a different repository? Others have confirmed the github repository to be working fine? (when ICLA/CCLA LA are signed, and ssh key has been configured)

                      If i may repeat myself.. Please read the other posts in this thread, and don't blindly run commands until something breaks, instead try to understand what your doing, pretty much all information required is there already.

                      Could you please answer the 3 questions above before continuing with other attempts?

                      1 Reply Last reply Reply Quote 0
                      • S
                        sreekupmgmail.com
                        last edited by

                        Hi Piba

                        I had sign ICLA
                        recived a mail [pfsense-github added you to the pfsense team pfsense-tools read access]

                        configured Publish key in github
                        :(

                        1 Reply Last reply Reply Quote 0
                        • P
                          PiBa
                          last edited by

                          Ok, so does this work now?

                          git clone -b RELENG_2_2 git@github.com:pfsense/pfsense-tools.git tools

                          Edit,
                          After loading the private ssh key, with commands shown before.

                          1 Reply Last reply Reply Quote 0
                          • S
                            sreekupmgmail.com
                            last edited by

                            Hi PiBa

                            Thanks Its working fine!
                            I have build my own ISO File,  Please help me on the below doubts

                            1. How can I change Gui??
                            2. How can I add another Packages?
                            3. How can I build for Nano BSD?

                            1 Reply Last reply Reply Quote 0
                            • P
                              PiBa
                              last edited by

                              Ok good that worked out.

                              1- investigate how for example "the wall" theme changes the gui, then create your own theme?
                              2- create your own package repository, and install packages from there?
                              3- so you dont want a iso? If your lucky the "./build.sh iso" command has other options to? Did you check?

                              1 Reply Last reply Reply Quote 0
                              • S
                                sreekupmgmail.com
                                last edited by

                                Hi Pi Ba,

                                I have change the theme, after building restore old theme what I can do?
                                any option before building?

                                1 Reply Last reply Reply Quote 0
                                • P
                                  PiBa
                                  last edited by

                                  So where do you think the build scripts get the normal pfSense gui from? Do you think that could be the https://github.com/pfsense/pfsense.git which was set in step3 of the building steps ? So its probably possible replace that to a cloned&modified git repository of your own to create a fully customized gui if thats what you want.

                                  There might be other ways to accomplish changing the normal pfSense webgui build to, which i currently dont know, and im not going to investigate as you should do that yourself.

                                  Anyway this topic is not about how to customize every single thing there is in pfSense, you succeeded in building the iso and thats as far as this topic is supposed to help you, so if you dont mind please ask further not directly related questions in another topic, perhaps one you create. Thanks.

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    sreekupmgmail.com
                                    last edited by

                                    PiBa

                                    Thanks a lot

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