OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 16.1 Legacy Series »
  • apinger completely unreliable on 16.1.13
« previous next »
  • Print
Pages: [1]

Author Topic: apinger completely unreliable on 16.1.13  (Read 4488 times)

interfaSys

  • Full Member
  • ***
  • Posts: 165
  • Karma: 13
    • View Profile
    • interfaSys ltd
apinger completely unreliable on 16.1.13
« on: May 11, 2016, 01:47:06 pm »
I have a gateway group with 3 tiers.
Traffic fails to switch to tier2 when tier1 is down.

I get lots of these errors in the logs:

Code: [Select]
May 11 13:28:22 apinger: Error while starting command form alarm(down) on target(8.8.4.4-VPN_TCP_VPNV4)
May 11 13:28:12 apinger: ALARM: VPN_TCP_VPNV4(8.8.4.4) *** down ***

which seem to indicate that the tier switch action fails to be triggered

And also these

Code: [Select]
apinger: command (al/opnsense/service/configd_ctl.py -m 'dyndns reload VPN_TCP_VPNV4' 'ipsecdns reload' 'openvpn reload VPN_TCP_VPNV4' 'filter reload' ) exited with status: 127
But that could be because it's trying to reload ipsec when ipsec has not even been setup.
Logged

AdSchellevis

  • Administrator
  • Hero Member
  • *****
  • Posts: 849
  • Karma: 163
    • View Profile
Re: apinger completely unreliable on 16.1.13
« Reply #1 on: May 11, 2016, 02:47:49 pm »
can you try the version from 16.1.12 to confirm that your issue started with the apinger version in 16.1.13?

Code: [Select]
pkg add -f https://pkg.opnsense.org/FreeBSD:10:amd64/16.1.12/OpenSSL/All/apinger-0.6.1_8.txz
(and restart the service)

Maybe Franco has some other things to inspect later on, but this one should be easy to test.
Logged

interfaSys

  • Full Member
  • ***
  • Posts: 165
  • Karma: 13
    • View Profile
    • interfaSys ltd
Re: apinger completely unreliable on 16.1.13
« Reply #2 on: May 11, 2016, 02:56:01 pm »
Good idea, thanks. I've switched and will monitor the situation.
Logged

interfaSys

  • Full Member
  • ***
  • Posts: 165
  • Karma: 13
    • View Profile
    • interfaSys ltd
Re: apinger completely unreliable on 16.1.13
« Reply #3 on: May 11, 2016, 04:39:38 pm »
I can confirm that things behave better with that previous version.

Code: [Select]
May 11 15:03:15 opnsense: /usr/local/etc/rc.filter_configure_sync: Could not find IPv6 gateway for interface(wan).
May 11 15:03:14 opnsense: /usr/local/etc/rc.filter_configure_sync: MONITOR: VPN_TCP_VPNV4 is down, removing from routing group VPN
Logged

interfaSys

  • Full Member
  • ***
  • Posts: 165
  • Karma: 13
    • View Profile
    • interfaSys ltd
Re: apinger completely unreliable on 16.1.13
« Reply #4 on: May 11, 2016, 10:54:28 pm »
Actually, that wasn't it. The exact same error came back later on when the gateway went down. Tier switching doesn't seem to work.
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 13602
  • Karma: 1170
    • View Profile
Re: apinger completely unreliable on 16.1.13
« Reply #5 on: May 17, 2016, 10:06:54 am »
Sorry I was on holiday... I don't believe this has anything to do with my rework so far, it looks like a memory corruption, the log line should yield a full command, but the command is mangled:

command (al/opnsense/service/configd_ctl.py -m 'dyndns reload VPN_TCP_VPNV4' 'ipsecdns reload' 'openvpn reload VPN_TCP_VPNV4' 'filter reload' )

The code responsible hasn't been touched...

https://github.com/opnsense/apinger/blob/master/src/apinger.c#L194

I will take a look at this later.
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 16.1 Legacy Series »
  • apinger completely unreliable on 16.1.13
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2