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

    Bug in Default gateway selection

    Scheduled Pinned Locked Moved General pfSense Questions
    12 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.
    • F
      Fabiano1 @bingo600
      last edited by

      @bingo600

      I don't want. It was an error selecting None. But until discover this was the error... it was possible to discover too that the behaviour is not to apply the choice imediatly, so the difficulty in finding the root cause.

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

        Mmm, that does seem unexpected. Though the globe icon indicates which gateway is default and it still showed which was correct.
        I assume it was not shown after rebooting?

        F 1 Reply Last reply Reply Quote 0
        • F
          Fabiano1 @stephenw10
          last edited by

          @stephenw10
          Exactly.

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

            Did it log an error when setting the gateway to none? Something that might indicate it was unable to remove the default route?

            F 1 Reply Last reply Reply Quote 0
            • F
              Fabiano1 @stephenw10
              last edited by

              @stephenw10
              No, I couldn't find any error in the logs. I found this only (under Status menu -> System Logs -> System -> Gateways):

              Jun 22 14:27:33 dpinger 44595 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr <WAN gateway IP> bind_addr <WAN IP> identifier "WANGW "
              Jun 22 14:27:33 dpinger 44759 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr <LAN gateway IP> bind_addr <LAN IP> identifier "LANGW "

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

                Hmm, that's just dpinger restarting, which is expected when you make any gateway change.

                F 1 Reply Last reply Reply Quote 0
                • F
                  Fabiano1 @stephenw10
                  last edited by

                  @stephenw10
                  Coming back to the two points I have suggested in the first topic:
                  1 - it could have a better message after changing the default gateway field;
                  2 - it could apply the change immediatly, or print a message alerting the user about what will happen.
                  Could be submitted a suggestion for improvement? (so it can be fixed, or it could have at least a message informing...).

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

                    You can open a bug report or feature request: https://redmine.pfsense.org/

                    F 1 Reply Last reply Reply Quote 0
                    • F
                      Fabiano1 @stephenw10
                      last edited by

                      @stephenw10
                      https://redmine.pfsense.org/issues/14634

                      Thank you!

                      K 1 Reply Last reply Reply Quote 1
                      • K
                        Kyouko @Fabiano1
                        last edited by

                        @Fabiano1 I have had similar behavior. However, CARP was still involved, which was also the reason for the problem.
                        But from the description it sounds very similar.
                        Therefore here is the link to the issue: https://redmine.pfsense.org/issues/14171

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