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

    Default gateway can not be created with GUI

    Routing and Multi WAN
    3
    7
    956
    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.
    • L
      lg75
      last edited by lg75

      Hello,

      We use pfSense on Proxmox at OVH (french hosting provider). They have a specific procedure for setting the default gateway when using an IP Failover :
      https://docs.ovh.com/sg/en/dedicated/pfSense-bridging/

      It works as described in the procedure with version 2.4.5p1, but not with version 2.5.0. We can create the setup described in the procedure in the GUI, but the default gateway is not actually created. If we add it manually on the shell it works again.

      Is there a solution to repair the GUI configuration ?

      Thanks

      2021-02-20_08-39.png
      2021-02-20_08-41.png
      2021-02-20_08-42.png
      2021-02-20_08-44.png
      2021-02-20_08-47.png
      2021-02-20_08-48.png
      2021-02-20_08-49.png

      1 Reply Last reply Reply Quote 0
      • L
        lg75
        last edited by

        We have found a workaround. But we believe this is a bug in the GUI interface. Can we open a bug request?

        The solution we found is to install the "shellcmd" plugin and run the commands to add the default gateway at boot.

        Thx

        2021-02-20_11-44.png

        1 Reply Last reply Reply Quote 0
        • L
          lg75
          last edited by

          We point out that as indicated in the OVH documentation, the gateway of a Failover IP address is outside its network. It is for this reason that it is necessary to check the box "System / Routing / Gateways / Edit / Use non-local gateway through interface specific route"
          But when restarting the pfSense we got three error messages.

          2021-02-20_16-22.png
          2021-02-20_16-22_1.png
          2021-02-20_16-04.png

          C 1 Reply Last reply Reply Quote 0
          • C
            capt_scurrrvy @lg75
            last edited by

            @lg75 I saw the same issue. I am on OVH. Running Proxmox and pfsense 2.4.5. Upgraded to 2.5 and got the same errors you highlighted. Thank goodness for the backup I made. I simply restored that and now up and running.

            To check if this was only related to upgrading a system, I created a new VM and installed 2.5 directly. Got the same errors. Not isolated to just upgrades.

            L 1 Reply Last reply Reply Quote 0
            • L
              lg75 @capt_scurrrvy
              last edited by lg75

              @capt_scurrrvy Thank you for your reply. In reality we did exactly the same thing, we freshly installed a pfSense 2.5.0 to identify if the problem was not related to the update. And I confirm that we have come to the same conclusion as you, the problem is specific to version 2.5.0, but for now we leave it with the workaround in case someone from Netgate ask us to do some more tests. We will keep you informed if there is something new.

              1 Reply Last reply Reply Quote 0
              • viktor_gV
                viktor_g Netgate
                last edited by

                use patch id 087d28fa3f5cfebfd4af7f4a4479b0fac053e062
                see https://redmine.pfsense.org/issues/11433

                L 1 Reply Last reply Reply Quote 1
                • L
                  lg75 @viktor_g
                  last edited by

                  @viktor_g Thank you. The patch is working fine.

                  2021-02-22_00-59.png

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