Bug #14248
openStatic routes to monitor IP disappears if you set a gateway group as a default gateway.
0%
Description
Tested on 23.01.
Steps to reproduce:
Set the monitor IP on each gateway
Create a gateway group Tier1 Tier2
Set Gateway group as default gateway at System=>Routing
Route table prior
After setting the gateway group
If you try to revert the default gateway option back you'll need to up/down the interface to restore the static route and sometimes it requires a reboot.
Files
Updated by Danilo Zrenjanin over 1 year ago
I couldn't reproduce it on:
23.01-RELEASE (arm64) built on Fri Feb 10 20:06:48 UTC 2023 FreeBSD 14.0-CURRENT
After defining a gateway group and setting it as the default system gateway, I can still see the routes for the monitoring IPs in the system routing table.
I tested with static and DHCP WAN interface types.
Updated by aleksei prokofiev over 1 year ago
I can't reproduce it
Version 23.01-RELEASE (amd64)
built on Fri Feb 10 20:06:33 UTC 2023
FreeBSD 14.0-CURRENT
Updated by Jim Pingle over 1 year ago
- Status changed from New to Feedback
If anyone can reproduce this starting with a completely fresh stock configuration, we'll need the steps involved to make it happen since so far nobody can reproduce it.
It might make a difference if WANs are static vs dynamic, for example, and also make sure there are no sources of conflicting routes (e.g. gateway monitor set the same as a DNS server pinned to a specific WAN).
Updated by Jordan G over 1 year ago
also unable to replicate this condition in multi-wan environment