Gateways Log Question/WAN Failover
-
I was hoping I could get some help understanding some intermittent latency entries in my Gateways log. I am using dual wan with failover and monitor with google dns. It looks like the intervals are coming from Routing->Gateways->Advanced and I just use the defaults. I did not bother masking my FTTH IP since it is CGNat. I know around 13:32, when I was doing a tracert, the wan did fail over for a few minutes based on trace I was seeing. Is there a log entry when pfsense fails over from a tier 1 Wan to a tier 2 Wan due to settings Latency and Packet Loss. I looked at Gateway Groups and there is no option for logging. Since this is my first time using Dual Wan Failover, should I be using the Latency and Packet Loss trigger or would Member Down be more reasonable. I am starting to see that the packet loss/latency trigger could cause the wan to bounce back and forth a lot. I would like to know when the Wan does fail over to tier 2 in a log if possible.
Thank you.
Dec 12 13:32:26 dpinger 38132 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.8.8 bind_addr 100.67.139.70 identifier "FTTH" Dec 12 13:32:26 dpinger 37623 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.4.4 bind_addr 67.190.xxx.xxx identifier "Comcast " Dec 12 13:32:26 dpinger 89788 exiting on signal 15 Dec 12 13:32:26 dpinger 89356 exiting on signal 15 Dec 12 13:32:38 dpinger 25420 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.8.8 bind_addr 100.67.139.70 identifier "FTTH" Dec 12 13:32:38 dpinger 24808 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.4.4 bind_addr 67.190.xxx.xxx identifier "Comcast " Dec 12 13:32:38 dpinger 38132 exiting on signal 15 Dec 12 13:32:38 dpinger 37623 exiting on signal 15 -
@jpvonhemel They are normal when the dpinger service restarts.
-
@rcoleman-netgate Do you mean the exiting on signal 15? I did see that it was normal and not a crash on a different thread. My question was more on the error and how it relates to dual wan failover and what is typical for the trigger.
-
@jpvonhemel All of it. The exit, the send_interval, that's all due to dpinger restarting.
-
@rcoleman-netgate Thank you. OK, I see. Should the dpinger process restart on a routine basis? I am seeing these log entries, and as you say, it is restarting, anywere from every 1-20 minutes. I am going to clear the log and see what it is doing without me making any changes to the Wan gateways.
-
@jpvonhemel Yes, some changes will trigger a restart. Some auto-update scripts as well.