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

    Stop interface reassignment on reboot

    Scheduled Pinned Locked Moved Off-Topic & Non-Support Discussion
    5 Posts 2 Posters 697 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.
    • G
      guntery
      last edited by

      Guys, I am playing around with a second USB LAN interface.

      I have

      WAN
      LAN (ue0)
      VPN

      If I delete the second (ue1) interface, remove it and reboot, the interface reassignment mode ALWAYS comes up, even though it was working fine pre-reboot as above.

      If i plug back in the USB adapter even though there is no interface assigned it boots successfully and previous interfaces are correct.

      So if I want a stable working system I cannot remove this not-in-use USB adapter.

      It seems really dumb behavior. It may be something to do with how USB is recognized, any ideas?

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        You will only hit that if ue1 is still referenced somewhere in the config. Check the config file directly /conf/config.xml.

        Steve

        1 Reply Last reply Reply Quote 0
        • G
          guntery
          last edited by

          Hey Steve, you would think so right...

          there is no mention at all of ue1
          I have deleted it from the gui and its not in conf...

          When I boot, the ue0 is not seen UNLESS ue1 is plugged in... regardless of which usb port

          So its perhaps not a pfsense issue but an underlying usb driver issue... I may just say stuff it and leave the $20 adapter in there...

          It would be much easier if the was an option to boot fully regardless of interfaces - better than a broken system

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hmm, well that's an interesting issue. That seems like a hardware or maybe bios bug. But you will need ue0 to be present since it's LAN so...

            The purpose of that check is to prevent it booting to a broken system. If the ruleset contains references to interfaces that are not present you are in an unknown siotuation. From a security view point it's better to not pass anything.

            You can add ue to the list of interfaces not to check but I would not recommend it.
            https://github.com/pfsense/pfsense/blob/0bdd1774a1666852e35452ea3f17bb9dc075ecec/src/etc/inc/util.inc#L2227

            Steve

            1 Reply Last reply Reply Quote 0
            • G
              guntery
              last edited by

              That seems like a hardware or maybe bios bug

              its a old Atom 64bit system but was going fine till this ue1 took over

              The purpose of that check is to prevent it booting to a broken system.

              yeh yo're right in this case ue0 often wasnt loading at all so no point continuing

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