OPNsense Forum

Archive => 23.1 Legacy Series => Topic started by: geek on May 05, 2023, 12:28:35 PM

Title: ALL 3 gateways flapping after latest 23.1.7 update
Post by: geek on May 05, 2023, 12:28:35 PM
I use multiwan with different priorities for gateways.
default gateway switching is enabled.
all three gateways are marked as upstream gateways. Everything was fine until I upgraded to 23.1.17

Now all three gateways go offline and online repeatedly at the same time. This has caused a major outage.

In the release notes I read the line
:"system: restructure routing to carry out default gateway switching and address family specific reconfig"

Would this have anything to do with my problem?
Thank you.
Title: Re: ALL 3 gateways flapping after latest 23.1.7 update
Post by: franco on May 05, 2023, 02:23:35 PM
Can you make sure to update to 23.1.7_2 and then apply the following on top?

https://github.com/opnsense/core/issues/6544#issuecomment-1535790249


Cheers,
Franco
Title: Re: ALL 3 gateways flapping after latest 23.1.7 update
Post by: geek on May 05, 2023, 06:20:46 PM
I just updated to OPNsense 23.1.7_3

Do I need to do anything else? At thhat time I went into gateways and checked the "Disable Host Route" option to fix the problem. I could not find any documentation on what exactly that option is used for other than the help item which said "Do not create a dedicated host route for this monitor.".
Title: Re: ALL 3 gateways flapping after latest 23.1.7 update
Post by: RedVortex on May 05, 2023, 08:39:20 PM
We're discussing this parameter and similar issue in this thread as well: https://forum.opnsense.org/index.php?topic=33831.0
Title: Re: ALL 3 gateways flapping after latest 23.1.7 update
Post by: fryrpc on July 31, 2023, 08:05:19 PM
Quote from: geek on May 05, 2023, 06:20:46 PM
I just updated to OPNsense 23.1.7_3

Do I need to do anything else? At thhat time I went into gateways and checked the "Disable Host Route" option to fix the problem. I could not find any documentation on what exactly that option is used for other than the help item which said "Do not create a dedicated host route for this monitor.".

I think this just masks the issue as without the route to the IP Address that is being used to monitor the link then the monitor ping packet will just be sent down the default gateway and thus not really test the link that you want it too.