Project

General

Profile

Actions

Bug #5053

closed

Apinger Problem with VPN interface

Added by Simon Büttgen over 8 years ago. Updated over 8 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Gateway Monitoring
Target version:
-
Start date:
08/31/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
All

Description

Apinger does´t track VPN Tunnel on startup.

After reboot of pfsense the apinger.conf only shows the WAN IF

target "10.0.0.1" {
description "WAN_DHCP"
srcip "10.0.0.106"
alarms override "loss","delay","down";
rrd file "/var/db/rrd/WAN_DHCP-quality.rrd"
}

after a reboot of the apinger service everything works fine...

target "xxx.xxx.xxx.xxx" {
description "GW_VPN_HETZNER"
srcip "xxx.xxx.xxx.xxx"
alarms override "loss","delay","down";
rrd file "/var/db/rrd/GW_VPN-quality.rrd"
}

target "10.0.0.1" {
description "WAN_DHCP"
srcip "10.0.0.106"
alarms override "loss","delay","down";
rrd file "/var/db/rrd/WAN_DHCP-quality.rrd"
}

Is there a workaround (maby restart apinger after boot) or something ?

Actions #1

Updated by Chris Buechler over 8 years ago

  • Project changed from Bootstrap to pfSense
Actions #2

Updated by Chris Buechler over 8 years ago

  • Subject changed from Apinger Problem to Apinger Problem with VPN interface
  • Category set to Gateway Monitoring
  • Status changed from New to Confirmed
  • Affected Version changed from 2.2.4 to All
  • Affected Architecture All added
  • Affected Architecture deleted (amd64)
Actions #3

Updated by Chris Buechler over 8 years ago

  • Status changed from Confirmed to Duplicate

duplicate of #4587

Actions

Also available in: Atom PDF