Bug #2537
closedPacket loss thresholds set in System->Routing-><WAN interface> do not effect apinger
0%
Description
I was noticing that the packet loss thresholds I set for my WANs were not being paid attention to by apinger and were NOT being entered in /var/etc/apinger.conf.
I did some digging and discovered that line 163 in /etc/inc/gwlb.inc is incorrect - it currently reads:
[code]if (!empty($gateway['lowloss'])) {[/code]
$gateway['lowloss'] does not exist in the config file, it is called $gateway['losslow'] as evidenced further down on line 165.
I've corrected this on my own platform and line 163 is now:
[code]if (!empty($gateway['losslow'])) {[/code]
Things are now working properly. I've attached the updated /etc/inc/gwlb.inc file for review.
Files
Updated by Chris Buechler about 12 years ago
- Category set to Gateways
- Priority changed from High to Normal
- Target version set to 2.1
Updated by Phillip Davis about 12 years ago
Me too - as part of testing Validate advanced gateway monitoring settings https://github.com/bsdperimeter/pfsense/commit/eb2335174c30b976d79963785c3731a937292467 I can confirm that the packet loss thresholds are getting correctly into apinger.conf