Project

General

Profile

Actions

Feature #2513

closed

Associate applicable static route to Gateway Monitor rule

Added by Moshe Katz about 10 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Gateways
Target version:
-
Start date:
06/21/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

This is based on a message to the pfSense email list:

Hi there,

While playing with gateways and monitoring alternative IP addresses,
I've noticed a problem.

When you add an alternative IP address to monitor, a static route is
added between the gateway address and the address to monitor.

But when you delete this alternative IP address, click on "save" and
then on "apply changes", the static route is not removed as can be seen
with netstat -nr.

Once you know this it's OK, but when you don't know and try to monitor
the external IP addresses of two links to two different ISP, each one
monitoring the other one, this creates some funny routing problems even
when you disable this monitoring, and this renders the problem difficult
to understand, and then fix.

Is this a bug or normal behavior ?

TIA

It would be nice if these configurations could be linked, similarly to the way Port Forwarding rules and Firewall Rules are associated as of 2.0.

Actions

Also available in: Atom PDF