Bug #10819
closed
Gateway group configuration for multi-wan ignored after upgrade to 2.5.0-DEVELOPMENT image
0%
Description
Hello! I recently upgraded to 2.5.0-DEV to overcome this issue: https://redmine.pfsense.org/issues/8987, which was totally destroying my Zoom calls, live streams, and everything else that needed bandwidth. I would like to ask you to roll that bugfix back into 2.4 because of its severity.
I'm here to report that after upgrading, the gateway groups no longer worked. PreferWAN1, PreferWAN2, and LoadBalance no longer had any effect. I could only direct traffic directly to WAN1_GW or WAN2_GW. Everything else just went out WAN1, even when WAN2 was the default gateway. WAN1 would be totally saturated while WAN2 had nothing more than the ping traffic from the firewall.
I fixed it today by deleting and recreating the two PreferWANx groups, and then on a whim I just changed LoadBalance to MemberDown instead of "High Latency or Packet Loss." It also started working again.
I don't know if it was the actual change that mattered or if changing something re-registered it with the configuration and caused it to start working, but in either case - upgrading to 2.5.0-DEV broke it.
Updated by Jim Pingle almost 5 years ago
- Category set to Multi-WAN
- Status changed from New to Rejected
The bug you linked is already fixed in 2.4.5-p1 and it was unlikely to be related to anything except accessing the GUI.
As for the other issues, there isn't enough information here to classify it as a bug.
For assistance in solving problems, please post on the Netgate Forum and if an actionable bug can be identified after discussing and diagnosing your issue there, a new issue can be opened with more accurate information.
Updated by Adrian G almost 5 years ago
Jim Pingle wrote:
The bug you linked is already fixed in 2.4.5-p1 and it was unlikely to be related to anything except accessing the GUI.
In my case the whole firewall would lock up for 30 seconds several times an hour. The dpinger process would hijack all of the CPU. All network traffic would come to a screeching halt. If I killed dpinger, it would eventually recover, only to recur again. I've found no reference to anything that sounds remotely like it other than the one I linked, and it most definitely was not limited to the GUI.
Upgrading to 2.5.0-DEV fixed it. I don't remember what version I was on before, but if it's possible to find that out from the firewall, I'm happy to share it so you can be a little less smug.
As for the rest of it, I've reported that after upgrading to 2.5.0-DEV the firewall no longer honored the pre-existing, working multi-WAN configuration and included steps I had to take to resolve it. You, as a developer or whatever you are, should be able to say, "oh interesting, that sounds like it might be X or Y, and we'll take a look."
Forums are most often the blind leading the blind, and I didn't come here asking for help. I came here telling you that your 2.5.0-DEV is broken and how I was able to work around it. Ignore it if you want - it's still broken.