Project

General

Profile

Actions

Bug #14248

open

Static routes to monitor IP disappears if you set a gateway group as a default gateway.

Added by Lev Prokofev about 1 year ago. Updated 12 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
Gateways
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:

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

clipboard-202304081428-lowc6.png (15.1 KB) clipboard-202304081428-lowc6.png Lev Prokofev, 04/08/2023 05:29 AM
clipboard-202304081430-l6jdx.png (17.1 KB) clipboard-202304081430-l6jdx.png Lev Prokofev, 04/08/2023 05:30 AM
clipboard-202304081430-adooo.png (15.7 KB) clipboard-202304081430-adooo.png Lev Prokofev, 04/08/2023 05:31 AM
Actions #1

Updated by Danilo Zrenjanin about 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.

Actions #2

Updated by aleksei prokofiev about 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

Actions #3

Updated by Jim Pingle about 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).

Actions #4

Updated by Jordan G 12 months ago

also unable to replicate this condition in multi-wan environment

Actions

Also available in: Atom PDF