Project

General

Profile

Actions
Copy link

Bug #16069

closed

The monitoring IP address for dynamic gateways may be unexpectedly routed via a different gateway

Added by Marcos M about 2 months ago. Updated 30 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Marcos M
Category:
Gateway Monitoring
Target version:
2.8.0
Start date:
Due date:
% Done:

100%

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

Description

When the option Static route is unchecked, it's expected that the monitoring IP address for a dynamic gateway is always routed via that gateway. Sometimes the gateway address is not available and the monitoring traffic may exit out a different gateway.

As an example, WAN2 is configured with DHCPv6 and a manual monitoring IP address. Additionally a floating outbound rule is created to catch the monitoring traffic going out the wrong interface. While it's offline, the system log can show:

Feb 27 13:20:54     php-fpm     84260     /rc.linkup: Removing static route for monitor 2001:4860:4860::8888 and adding a new route through dynamic
Feb 27 13:20:54     php-fpm     84260     /rc.linkup: route_add_or_change: Invalid gateway (dynamic)
Feb 27 13:23:17     php-fpm     75951     /rc.linkup: Accept router advertisements on interface igc2

and the following filter log is shown:
Feb 27 14:12:25     WAN3     Invalid routing (1683153300)     [fd6d:2aa9:fc80:0:208:a2ff:fe12:ec7a]        [2001:4860:4860::8888]        ICMPv6

Actions
Copy link

Also available in: Atom PDF