Bug #11694
closed
Upstream Gateway Not Being Set Repeatedly
0%
Description
Hi all,
I have been experiencing a consistent issue with my pfSense virtual machine. My current set up is 2 ESXi hosts with pfSense installed as a vRouter on both of the hosts, the hosts are public facing. Ever since upgrading to 2.5 (everything was working perfectly before), I have been experiencing an issue where my Upstream Gateway is not being set - I have to input the following command into Command Prompt to actually get networking on the vLAN (which has nearly severely screwed me once): route add -host XXX.XXX.XXX.XXX -iface vmx0 ; route add default XXX.XXX.XXX.XXX
A week ago I set up a new ESXi host, the second, a fresh install, and I am still experiencing issues. 'Use non-local gateway through interface specific route' is configured on both. Gateway Monitoring, Traffic Shaping are disabled.
Thank you
Updated by Alasdair Corton over 4 years ago
The "Fix" link isn't working
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/139
Updated by Viktor Gurov over 4 years ago
Alasdair Corton wrote:
The "Fix" link isn't working
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/139
Please apply Patch ID a97987a5d1df8219f40433270fce0e3ef49345dc or test it on the latest 2.5.1/2.6 snapshot
see https://docs.netgate.com/pfsense/en/latest/development/system-patches.html
Updated by Alasdair Corton over 4 years ago
Hi there,
Thanks for the patch ID, apologies it took so long to come back to you, yes - this patch has resolved the issue
Your responses are much appreciated!