Project

General

Profile

Actions

Bug #12920

open

Gateway behavior differs when the gateway does not exist in the configuration

Added by Marcos M about 2 years ago. Updated about 2 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Gateway Monitoring
Target version:
Start date:
Due date:
% Done:

100%

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

Description

The gateway status and dpinger behave differently when the respective gateway entry does not exist in the config.xml file. This behavior difference results in failure to fail back after WAN failover.

Test:
  • DHCP WAN
  • Bounce interface physically and with ifconfig.
  • no gw = no gateway entry in config.xml
  • gw = gateway entry exists in config.xml

Netgate 5100

ifconfig produced same results.

            unplug cable                            plug cable
            gateway status      dpinger status      gateway status      dpinger status
22.01 no gw missing             RUNNING             ONLINE              RUNNING
22.01 gw    pending             stopped             pending             stopped

22.05 no gw missing             stopped             ONLINE              RUNNING
22.05 gw    pending             stopped             ONLINE              RUNNING

Netgate 1100

            unplug cable                            plug cable
            gateway status      dpinger status      gateway status      dpinger status
22.01 no gw missing             RUNNING             ONLINE              RUNNING
22.01 gw    pending             stopped             pending             stopped

22.05 no gw missing             stopped             ONLINE              RUNNING
22.05 gw    pending             stopped             ONLINE              RUNNING

            ifconfig down                           ifconfig up
            gateway status      dpinger status      gateway status      dpinger status
22.01 no gw offline             RUNNING             ONLINE              RUNNING
22.01 gw    offline             RUNNING             ONLINE              RUNNING

22.05 no gw offline             RUNNING             ONLINE              RUNNING
22.05 gw    offline             RUNNING             ONLINE              RUNNING
A missing gateway can have other undesired behavior:
  • The Automatic default gateway detection will choose disabled gateways over an enabled and online gateway which has the missing config.xml entry.
  • dpinger will not start and the gateway status will remain pending after releasing/renewing the WAN DHCP lease.

Files

rm12920-5100-igb0-connected.png (79.2 KB) rm12920-5100-igb0-connected.png WAN connected Ryan Coleman, 12/19/2022 11:19 AM
rm12920-5100-igb0-disconnected.png (51.2 KB) rm12920-5100-igb0-disconnected.png WAN disconnected Ryan Coleman, 12/19/2022 11:19 AM

Related issues

Related to Regression #14616: dpinger does not start after renewing DHCPResolvedMarcos M

Actions
Related to Regression #11570: Gateway monitoring services is not always restarted on interface events, which may prevent a WAN from recovering back to an online stateClosed

Actions
Actions

Also available in: Atom PDF