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

    Tackling migration config from mini PC to SG-1100

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 2 Posters 392 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.
    • D
      DominikHoffmann
      last edited by

      I had to replace a Protectli FW20216 Mini PC running 22.05 for amd64 with a brand-new SG-1100 that came pre-installed with 22.05 for arm.

      I saved the Protectli’s configuration via Diagnostics → Backup & Restore. I then powered up the SG-1100 in its place with my laptop connected via Ethernet to the physical SG-1100 LAN port. Once booted up, I bypassed the installation Wizard and went to Diagnostics → Backup & Restore and restored the configuration.

      That’s when I ran into the first problem. On the Protectli the ports are called em0 and em1. On the SG-1100 they are mvneta0. My SG-1100 was bricked.

      I had to pull out my serial cable and connect it to the console port and run a serial terminal program on my laptop. I chose a trial on the $40 Serial by Decisive Tactics. I did not get anywhere with trying to install the PL2303 on my Mac running macOS Ventura, so that I could establish a serial port in the Mac’s /dev/ list.

      I restored the SG-1100 to factory settings two or three times, before I realized how to properly treat the VLANs on boot-up. In my Protectli config file I replaced all occurrences of “em0” with “mvneta0.4090” and all those of “em1” with “mvneta0.4091”. On boot-up the process paused with the question: “Do VLANs need to be set up first?” I answered “y.” It then asked,

      Enter the parent interface name for the new VLAN (or nothing if finished): mvneta0
      Enter the VLAN tag (1-4094): 4090
      

      and repeated the same for mvneta0.4091 (LAN interface). Subsequently, this came up:

      Enter the WAN interface name or 'a' for auto-detection
      (mvneta0.4090 mvneta0.4091 mvneta0.4091.20 mvneta0.4091.21 or a): mvneta0.4090
      
      Enter the LAN interface name or 'a' for auto-detection
      NOTE: this enables full Firewalling/NAT mode.
      (mvneta0.4091 mvneta0.4091.20 mvneta0.4091.21 a or nothing if finished): mvneta0.4091
      

      This got everything working. I then used the WebConfigurator to set up the physical OPT port with mvneta0.4092.

      1 Reply Last reply Reply Quote 0
      • jimpJ jimp moved this topic from Problems Installing or Upgrading pfSense Software on
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        If you open a ticket with us we can convert your config so it imports to the 1100 directly:
        https://www.netgate.com/tac-support-request

        The config needs to include both the VLAN and switch sections required for the 1100.

        Steve

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