Gateway shows as being down, but isn't.

jswj · Mar 10, 2014, 6:37 AM

turn off gateway ip monitoring on the WAN interface, see if that helps.

rizwan602 · Mar 23, 2014, 9:27 PM

I have turned off gateway monitoring and things start working again, but I need to keep the gateway monitoring on.

I have found that if the gateway goes down and comes back up pfSense still thinks its down. The only way I can get it to work is change the Monitor IP address on the gateways screen, save / apply the setting, and then change it back, save / apply and it automagically starts working again, until the gateway is either down or rebooted later. I constantly have to massage this setting.

I have tried many differnet Monitor IP addresses. I've tried 4.2.2.1, 8.8.8.8 and many others. Same behavior.

Is this an issue others are experiencing too?

finack · May 23, 2014, 7:33 PM

I am having the exact same problem, right down to your workaround with changing the monitor ip and it showing online again.

Were you ever able to find a better solution?

Cheetohz · May 29, 2014, 4:36 PM

Is the monitoring IP going down or blacklisting you temporarily due to high traffic?

finack · May 29, 2014, 11:10 PM

The monitor ip is set to 8.8.8.8 right now, so I doubt its blacklisting me, and it's not being blacklisted by anything on my end, as far as I can tell.

The gateway status appears to be showing an accurate RTT, but it also shows offline and 100% loss. The gateway still works fine and my traffic is still sent over it, but it shows offline and 100% loss.

Restarting the apinger service seems to fix it temporarily, but it ends up showing offline again at some point.

It's not a big issue for me since it's not in a gateway group like the OP's, I'm just curious as to what's causing it more than anything.

tokiebonilla · Nov 23, 2014, 11:41 PM

@finack:

I am having the exact same problem, right down to your workaround with changing the monitor ip and it showing online again.

Were you ever able to find a better solution?

Same here, same exact problem with Gateway monitoring.

Derelict · Nov 24, 2014, 12:13 AM

apinger is broken. It does all sorts of nonsense. It's pretty unthinkable that they don't do a 2.1.6 to fix it. Wait for 2.2 they say.

edosselio · Sep 19, 2015, 10:11 PM

@Derelict:

apinger is broken. It does all sorts of nonsense. It's pretty unthinkable that they don't do a 2.1.6 to fix it. Wait for 2.2 they say.

Hello,
any news about that? We're now on 2.2.4 but the problem still exists.
Apinger works perfectly when a gateway goes down and the traffic is correctly routed to the other one; but when the gateway comes up apinger does not do the "failback" until i don't manually restart the process….

doktornotor · Sep 19, 2015, 10:15 PM

@edosselio:

any news about that? We're now on 2.2.4 but the problem still exists.

No, no news at all… apinger is still the same unfixable garbage code.

edosselio · Sep 22, 2015, 5:16 PM

Ok, for now i've set a workaround cron task running every 15 minutes:

/usr/bin/killall -9 apinger && /usr/local/sbin/apinger -c /var/etc/apinger.conf

Thanks,

Edoardo