Project

General

Profile

Actions

Bug #3134

closed

Apinger is not updating monitor IP until it is manually restarted

Added by Jim Pingle over 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Ermal Luçi
Category:
Gateways
Target version:
Start date:
08/07/2013
Due date:
% Done:

100%

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

Description

After the latest apinger changes, If you edit a gateway and change the monitor IP, a save/apply is not changing the monitor IP as used by apinger, until the process is stopped and restarted.

Actions #1

Updated by Mastah Naleh over 8 years ago

Jim P wrote:

After the latest apinger changes, If you edit a gateway and change the monitor IP, a save/apply is not changing the monitor IP as used by apinger, until the process is stopped and restarted.

Confirming, after updating today to the 07-08-2013 snapshot, the aping service was down. I had to manually activate it.
Strangely, I've a fail-over (which require a gateway ping to be considered as up) that was been ping correctly even if aping was down ?!

WAN was marked as gathering data
Opt1 was marked as online (with ping)

I've also the feeling that if the connexion switch to the Opt1 (fail-over due to WAN offline), even if WAN come back alive, the connexion will never switch again to WAN unless Opt1 is put offline and bring back online manually.
WAN tier 1, Opt1 tier 2.

Actions #2

Updated by Ermal Luçi over 8 years ago

  • Status changed from New to Feedback

Should be solved in later snapshots.

Actions #3

Updated by Ermal Luçi over 8 years ago

  • Status changed from Feedback to Resolved
  • % Done changed from 0 to 100
Actions #4

Updated by Mastah Naleh over 8 years ago

Confirm it's working properly.

Also solved : https://redmine.pfsense.org/issues/3138

Actions #5

Updated by Florian Schaeffler about 8 years ago

I still have got a similar behavior with the version "2.1-RELEASE (i386) built on Wed Sep 11 18:16:44 EDT 2013 FreeBSD 8.3-RELEASE-p11"

Configuration:
Gateways:
WAN1
WAN2
WAN3

Gateway Group:
WAN1 > Tier 2
WAN2 > Tier 3
WAN3 > Tier 1

In case WAN3 goes down by unplugging the cable or a reboot of the endpoint of WAN3, all traffic is getting routed to WAN1, which is the next-highest fallback gateway. However, when WAN3 comes online again, all traffic is still being routed to WAN1 and not to WAN3. It`s not only a `broken states`-problem, as a traceroute also shows the same behavior for new / unestablished connections.

Actions

Also available in: Atom PDF