Project

General

Profile

Actions

Bug #2537

closed

Packet loss thresholds set in System->Routing-><WAN interface> do not effect apinger

Added by Tim Economides over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Gateways
Target version:
Start date:
07/05/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0.x
Affected Architecture:

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

gwlb.inc (19.9 KB) gwlb.inc Tim Economides, 07/05/2012 07:00 AM
Actions #1

Updated by Chris Buechler over 9 years ago

  • Project changed from 3 to pfSense
Actions #2

Updated by Chris Buechler over 9 years ago

  • Category set to Gateways
  • Priority changed from High to Normal
  • Target version set to 2.1
Actions #3

Updated by Carlos Cesario over 9 years ago

Fixed to me.

Actions #4

Updated by Phillip Davis over 9 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

Actions #5

Updated by Seth Mos over 9 years ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF