Multi WAN on OffLine State

heper

have you tried changing monitor ip's ?

Derelict

You should probably at least upgrade to current release code level.

Post some diagnostics from the WAN that is showing down when it should be showing up. Things like manual pings from the firewall to the monitor IP address, quality graphs, etc.

For the ping do something like ping -i.5 -c 60 monitor.ip.address. That will be basically what dpinger does.

v.smaldino

Until few days ago, every time i changed the monitor ips, but the problem doesn't change.

Today it happened two times :-( , i searched the logs for something useful, but nothing!

I attach the ping on the monitor_ip of the WAN and the gateways logs.

In my opinion the problem is related with dpinger; i'm not able to check what happend when it triggerred the alarm, but i'm SURE that when i successfully pinged the monitor ip, the WAN is marked as OFFLINE.

I don't know how dpinger integrates with the system, but checking dpingers PIDs, i observed that dpinger restarts after saving any GW config and then all goes ok.

In order to debug the problem:

Is there any way to check (from the shell) what dpinger "thinks" about the status of its monitor_ip at any time?
Is there any way to manually restart (from the shell) the instance of dpinger relatively to the WAN marked offline?

Thanks to all
V

ping.png_thumb

log1.png_thumb

lo2.png_thumb

heper

fetchin straws here but, have you tried changing dpingers data payload?

v.smaldino

Just changed all payloads from 0 to 56. Let's see :)

Thanks

Gildresh

Where can you change the payload?

v.smaldino

@Gildresh
in System->Routing->Edit your GW->Advanced->Data Payload.

Read below ;)

v.smaldino

I just ended a cycle of tests about this matter. I share with you what happened:
I put in service a Zeroshell box acting as a failover/load balancer on a test LAN using the same GWs as pfSense box, on the same ethernet infrastructure and with the same monitor ip and parameters.

Changing data payloads doesn't solve the problem
When for some reason any of the GWs went down, both pfSense and Zeroshell marked it as Offline
When the GW came up again, ZS recognized the event and marked it Online, PFS kept it Offline until dpinger restarted

Restarting dpinger seems to be the only solution :(

Attachments:

Logs of pfSense boxes
Log of Zeroshell box

cinque.png_thumb

quattro.png_thumb

tre.png_thumb

Alesk13Fr

Hello,

I've done the same things, I've try to compare it with ZeroShell too and OPNSense, and see the same things, with PfSense Gateway never goes back in Online mode when link goes back, with OPNSense, problem is present but only 25% of time (when PfSense go offline, it never go back, when OPNSense go back, 1 of 4 times gateway stay down, and I can use a cron task with to launch back /usr/local/sbin/apinger -c /var/etc/apinger.conf, but this don't exist on PfSense, I hope I'm wrong ?), with ZeroShell I've 100% success.

I'm pretty sure dpinger or apinger aren't going to test anymore the gateway and stay stuck to OffLine mode …
It would be really cool if somebody can help in first time, to give us a way to restart dpinger via cron if gateway goes down, and in second time to correct this things, for me it's just a little bug, to stop this behaviour ...

I'm using PfSense since 6 years now, and this problem is recuring since the begining ... I Hope this time my report will be understand and earn !

Thanks in advance, I love so much PfSense since the begining, but this things is driving me nuts, I'm tired to go don't do any changes on each gateway down and apply no changes just to get dpinger restarting, this is done 4 to 25 times a day ...

Best regards,
Alex.

v.smaldino

Just an addendum.

I'm not able to manually replicate the problem. Every time i shutdown and restart or i disconnect and reconnect wan or lan cable of any of my adsl modems, pfsense works correctly, very strange :-\

Thanks all

V