Feature #3151
Disable gateway monitoring actions without disabling gateway monitoring
100%
Description
Mentioned in this thread: http://forum.pfsense.org/index.php/topic,65452.0.html
In sites with single WAN, I still put a realistic gateway monitoring IP (e.g. Google 8.8.8.8) so I can see what the WAN performance is like. By, like the OP in the thread, I don't want apinger/pfSense to take any action at all based on the monitored stats (latency, loss, even member down).
Associated revisions
Feature #3151 Disable gateway monitoring actions
without disabling gateway monitoring.
This allows the user to continue to monitor the gateway with dpinger, so
they can see how it is performing, but for the system not to take any
real action if the latency/loss exceeds the given limits.
A typical use case for this would be on a single-WAN system. There is no
failover option, so there is no point taking any real action when the
latency/loss is high. Having stuff try to failover (and stop/start
stuff...) is just disruptive.
In ths case the use could have disabled monitoring completely, but then
they get no feedback abut gateway performance.
Feature #3151 Disable gateway monitoring actions
without disabling gateway monitoring.
This allows the user to continue to monitor the gateway with dpinger, so
they can see how it is performing, but for the system not to take any
real action if the latency/loss exceeds the given limits.
A typical use case for this would be on a single-WAN system. There is no
failover option, so there is no point taking any real action when the
latency/loss is high. Having stuff try to failover (and stop/start
stuff...) is just disruptive.
In ths case the use could have disabled monitoring completely, but then
they get no feedback abut gateway performance.
(cherry picked from commit f396d2b715b27312c9bc056b3423db8198f7d52a)
History
#1
Updated by Phillip Davis 10 months ago
I finally remembered and cared enough :)
Pull Request https://github.com/pfsense/pfsense/pull/3259
#2
Updated by Renato Botelho 10 months ago
- Assignee set to Renato Botelho
- Target version changed from Future to 2.4.0
I'll check it
#3
Updated by Renato Botelho 10 months ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Merged, thanks!
#4
Updated by Phillip Davis 9 months ago
Been working for me, but it would be good to get some feedback from anyone else who has tried/tested this.
#5
Updated by Jim Pingle 9 months ago
- Status changed from Feedback to Resolved
Works here, too. Gateway status shows it going up/down but no actions are taken when it transitions.
#6
Updated by Jim Pingle 7 months ago
- Target version changed from 2.4.0 to 2.3.3