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

    Problem "Network interface mismatch"on pfSense Beta 2.0 while importing settings

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    13 Posts 4 Posters 7.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.
    • T
      toomeek
      last edited by

      Anyone else has problem with importing setting from 1.2.3 to 2.0? Please confirm. I'm still getting this.

      1 Reply Last reply Reply Quote 0
      • S
        simby
        last edited by

        I have problem with boot panic

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

          @TooMeeK:

          Anyone else has problem with importing setting from 1.2.3 to 2.0? Please confirm. I'm still getting this.

          Can you send me your config privately so I can run some tests with it, to see if it's something specific to your config?

          You can mail it to me at jimp (at) pfsense (dot) org

          @simby:

          I have problem with boot panic

          That has nothing to do with this thread. There are already threads for the boot panic issue on amd64.

          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
          • G
            geewhz01
            last edited by

            I have this same problem.  A upgrade from 1.2.3 works fine upon the first boot, but once it finishes the upgrade if you reboot again then it comes up with the network interface mismatch each time.  If I install 2.0 and import the settings I'm getting the same interface mismatch.  I have not changed any settings before rebooting when the error comes up.  Even if I try to assign the interfaces after reboot it keeps in a loop with interface mismatch.

            Andy

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

              @geewhz01:

              I have this same problem.  A upgrade from 1.2.3 works fine upon the first boot, but once it finishes the upgrade if you reboot again then it comes up with the network interface mismatch each time.  If I install 2.0 and import the settings I'm getting the same interface mismatch.  I have not changed any settings before rebooting when the error comes up.  Even if I try to assign the interfaces after reboot it keeps in a loop with interface mismatch.

              Please e-mail me a copy of your 1.2.3 configuration so I can try to replicate the problem. Send it to jimp at pfsense . org.

              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
              • G
                geewhz01
                last edited by

                @jimp:

                @geewhz01:

                I have this same problem.  A upgrade from 1.2.3 works fine upon the first boot, but once it finishes the upgrade if you reboot again then it comes up with the network interface mismatch each time.  If I install 2.0 and import the settings I'm getting the same interface mismatch.  I have not changed any settings before rebooting when the error comes up.  Even if I try to assign the interfaces after reboot it keeps in a loop with interface mismatch.

                Please e-mail me a copy of your 1.2.3 configuration so I can try to replicate the problem. Send it to jimp at pfsense . org.

                It has been sent.  If you need anything else please let me know.

                Thanks,
                Andy

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

                  OK I think I fixed this.

                  If you had the load balancer configured, the upgraded monitor IPs were accidentally getting created as interfaces. So the next reboot had interfaces that really didn't exist and had no physical hardware associated, so it believed there was a mismatch.

                  Hopefully the next new snapshot dated after this post (note: Not the one building now, the one after it!) should include the fix.

                  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
                  • G
                    geewhz01
                    last edited by

                    Ok thanks.  I'll test tomorrow :).

                    Thanks,

                    Andy

                    1 Reply Last reply Reply Quote 0
                    • T
                      toomeek
                      last edited by

                      Finally ;) hehe
                      I hope my 1st post was helpfuly.

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

                        @geewhz01:

                        Ok thanks.  I'll test tomorrow :).

                        Thanks,

                        Andy

                        This is fixed for me.  THANKS!!!!

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