Default gateway can not be created with GUI
-
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
-
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
-
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.
-
@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.
-
@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.
-
use patch id 087d28fa3f5cfebfd4af7f4a4479b0fac053e062
see https://redmine.pfsense.org/issues/11433 -
@viktor_g Thank you. The patch is working fine.
