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

    Can I use the same config on different machines? From x86 to ARM and vice versa?

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 4 Posters 864 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.
    • S Offline
      swapjim
      last edited by

      Assuming that they have the same packages installed, and the config doesn't expect hardware it's not there (like extra Ethernet ports), can I use the same config on different machines?

      What if one of the machines is x86 and the other is ARM? (either going from a x86 machine to an ARM one, or from an ARM machine to a x86 one)

      1 Reply Last reply Reply Quote 0
      • H Offline
        heper
        last edited by

        the configs are pretty generic & most of the time, only the interfaces need to be reassigned (either manually editing or by console prompt).

        i've never used an arm device for pfsense, so i can't be certain that there are no special things in the config for arm

        1 Reply Last reply Reply Quote 0
        • S Offline
          swapjim
          last edited by

          That's nice. Thank you!

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

            As long as the same packages are available on both architectures, the config would carry over. The only requirement would be to reassign the interfaces.

            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
            • K Offline
              Knight
              last edited by

              Hi!

              The only requirement would be to reassign the interfaces.

              What do you do when they are not an exact match?

              My pfSense box is behaving very erratically (my guess is bad caps on the motherboard) and I tried to, temporarily, setup a new box…

              Unfortunately even though both machines were more or less from the same era (Atom 330) they had different slots (PCIe vs PCI) and my real pfSense box had a mini-PCIe wireless NIC (Atheros based).

              They also had different onboard NICs...

              My real box has a PCIe Intel I340-T4 quad NIC and in the temporary replacement box I decided to reuse the old PCI Intel 21143 quad NIC I used in my previous non-pfSense based firewall.

              The onboard NIC was not used in my real pfSense box so I assigned it to the onboard NIC of the new machine.

              My WAN, LAN and DMZ which were provided by my I340-T4 were easy to match to to equivalent ports on the Intel 21143 based NIC...

              The last port on the I340-T4 I was no longer using. I used to use it to connect a wireless access point.

              The onboard mini-PCIe wifi card I could not match to anything... I am not sure if I was immediately able to delete it so it is possible I temporarily assigned to another port, I am not sure...

              Once everything was done I deleted the unused onboard NIC (which I had created anyway) and the port assigned to the wifi...

              What I ended up with was able to connect to the Internet since I was able to ping outside IPs but none of my Internal DNSes were working anymore...

              I also had this error message (or variants on it):

              
              There were error(s) loading the rules: /tmp/rules.debug:85: syntax error - The line in question reads [85]:  altq on  priq queue {  qLink,  qACK,  qVoIP  } 
              
              

              I believe this is traffic shapping stuff… Obviously it was quite unhappy about something I had done....

              Was it the cause of my internal DNSes not working?

              I don't know and could not investigate further when I tried this... I had to go back to the unstable box until I have time to try this again...

              Thank you and have a nice day!

              Season's Greetings!

              Nick

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