Navigation

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

    Migrating from sg3100 to a i5 firewall

    General pfSense Questions
    4
    8
    185
    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.
    • A
      amarcino last edited by

      I am going to move to an intel i5 firewall. I am hoping to use a backup xml from my sg3100 to load all of the settings to the new device.

      A potential problem I see are the interfaces are named differently on the sg3100. Do I need to edit the xml file to capture the new interface names or is there another method?

      I sm hoping the rest of the configuration goes EZ so I don't have to duplicate everything by hand.

      Thanks in advance for the insights.

      V S JKnott 3 Replies Last reply Reply Quote 0
      • V
        vjizzle @amarcino last edited by

        @amarcino Hi I did this a couple of times when moving my config from physical to VMware. It should be no problem once you make some preperations.

        What you can do is:

        • remove all extra packages (like pfblocker etc)
        • export the config file
        • find the name of the network interface on your new firewall. To do this just install pfsense and login to check it. No need to configure anything yet.
        • find the network interface name of your sg3100
        • using notepad++ find and replace the old network interface names with the new one from your new i5 system. Like replace igb0 with em0 etc.
        • import the modified config.xml on your new i5 system.

        This method always worked for me. Goodluck!

        A 1 Reply Last reply Reply Quote 1
        • A
          amarcino @vjizzle last edited by

          @vjizzle

          Thanks. I guess all of the additional packages you want will have to installed and configured on the new device by hand?

          I was hoping to avoid that if at all possible.

          V 1 Reply Last reply Reply Quote 0
          • V
            vjizzle @amarcino last edited by

            @amarcino Hi. Depending on the package there should be an option there to Keep Settings (pfblocker has that option for example). That option should be enabled before uninstalling the package. On your new system when you install the same package it should restore the configuration.

            1 Reply Last reply Reply Quote 1
            • S
              SteveITS @amarcino last edited by

              @amarcino If you're familiar with XML, you can edit the interface names in the file and then restore. But, IIRC pfSense will prompt to select interfaces during the restore.

              Steve

              Only install packages for your version, or risk breaking it. If yours is older, select it in System/Update/Update Settings.
              When upgrading, let it finish. Allow 10 minutes, or more depending on packages and device speed.

              1 Reply Last reply Reply Quote 0
              • A
                amarcino last edited by

                Thanks for the insights. I will be doing this in the next few days.

                1 Reply Last reply Reply Quote 0
                • JKnott
                  JKnott @amarcino last edited by

                  @amarcino

                  When I changed firewall hardware, I just copied over the config.xml and then tweaked it for the new interface names. My old firewall had 1 each Intel, Broadcom and Realtek NICs. The new one has 4 Intel.

                  PfSense running on Qotom mini PC
                  i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                  UniFi AC-Lite access point

                  I haven't lost my mind. It's around here...somewhere...

                  A 1 Reply Last reply Reply Quote 0
                  • A
                    amarcino @JKnott last edited by

                    Thanks you all for the insight. The XML file and modifications worked great.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post