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

    Bug? Changing wan dhcp to static causes this error

    Scheduled Pinned Locked Moved General pfSense Questions
    11 Posts 3 Posters 605 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Hmm, can I assume you added a static gateway on the WAN when you switched?

      GPz1100G 1 Reply Last reply Reply Quote 0
      • GPz1100G
        GPz1100 @stephenw10
        last edited by GPz1100

        @stephenw10 Correct.

        Change from dhcp to static then enter ip/subnet. Click add gateway and enter gw ip details, save. Save in the main edit interface page, then apply.

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

          @GPz1100

          Why did you change to static? Were you assigned a static address by your ISP? If not, you shouldn't be doing that.

          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...

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

            @JKnott That's beside the point :). I was testing something. The concern is the error message in the log.

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

              Replicated that. It's config access bug. The result of extensive changes in how the config is accessed in 24.11.

              https://redmine.pfsense.org/issues/16105

              Interesting side note is that the system doesn't allow you to set the gateway to the same IP passed by DHCP...

              GPz1100G 2 Replies Last reply Reply Quote 0
              • GPz1100G
                GPz1100 @stephenw10
                last edited by

                @stephenw10 You are correct. I forgot about that. In testing, I incremented the last octet by 1, then corrected it after applying via system/routing/gateways.

                A bit of the horse fighting the buggy scenario?

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

                  Yes, it's probably safer to refuse duplicate gateways than to try and allow for dhcp to static transitions when it's relatively easy to work past. If annoying!

                  1 Reply Last reply Reply Quote 0
                  • GPz1100G
                    GPz1100 @stephenw10
                    last edited by GPz1100

                    @stephenw10 Is this patch supposed to work on 24.11 or only on 25.03? Even with the patch applied I was still seeing the same error in 24.11 and 25.03. I tested several variations including 24.11 with the patch, 24.11 without the patch upgraded to 25.03 then patch applied.

                    Testing consists of toggling between static and dhcp wan settings. It's important to delete the newly created gateway (under system/routing) after switching back to dhcp. Next time when setting it back to static, the bug would get triggered.

                    <confused>

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

                      Try the additional commit shown.

                      GPz1100G 1 Reply Last reply Reply Quote 0
                      • GPz1100G
                        GPz1100 @stephenw10
                        last edited by

                        @stephenw10 Success. I only tested as far as error messages in the logs.

                        It should be noted both earlier and later patches need to be applied in order. I was initially under the understanding the later just needs to be applied by itself.

                        1. 8286c27ca678dbada2d205f606e76fab48885f60

                        2. f51505bf15e7af39c909d63356089d5e247cf781

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