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

    Upgrading pfsense hardware – interface names changes cause problems

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    5 Posts 4 Posters 1.1k 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.
    • J
      jantypas
      last edited by

      With pfSense 2.5 someday, we had a chance to update our pfSense 2.3.4 router to somehting more modern anway.  We were running on one of those nice little Celeron boxes with four Intel GB interfaces and 8GB of ram.  We acquired an i5 version (yes, I know it's far more power tha pfSense needs), with four interfaces BUT, these show up in FreeBSD as igb0-3 as oppsoed to enc0-3. 
      If we try to restore a backup – as expected, many things break.  We did a little hand editting but in general, the web interface just will not start.

      Is there a proper way to ugprade when the interface names change?

      1 Reply Last reply Reply Quote 0
      • w0wW
        w0w
        last edited by

        @jantypas:

        We did a little hand editting but in general, the web interface just will not start.

        What exactly you have edited? In general you need only replace igb0, igb2, igb3 (exact match) with enc0, enc2, enc3 in config, but it does not mean you have the same physical layout on new hardware and there can be some port mess around it, so you need to check for real, physical port numbering and find out which port is which and put you cables according to this new layout.

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by

          enc? Are you sure?

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          1 Reply Last reply Reply Quote 0
          • K
            kpa
            last edited by

            Must be an error because encX is the IPSEC filtering interface:

            https://www.freebsd.org/cgi/man.cgi?query=enc&apropos=0&sektion=4&manpath=FreeBSD+11.0-RELEASE+and+Ports&arch=default&format=html

            1 Reply Last reply Reply Quote 0
            • w0wW
              w0w
              last edited by

              Yep… enc can not be used in replacing igb, so triple check that also, but in general you should replace it with your new interface, ex em0 or whatever else

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