Multiwan problem, possible a bug.
-
Hello guys,
We are using pfsense 2.3.1-RELEASE-p5 in a multi wan configuration.
The problem we have found is like this, when a dsl goes down pfsense removes this gateway from the gateway group we have and reload the iptables with the new configuration, now if the gateway not become online before the next probe pfsense will repeat the process of removal and that means that its reload iptables again causing mini disconnects everytime. we thing that pfsense it must check the last state of the gateway and if it was down to bypass the entire process until the gateway become online again.
Is there anything we can do to quick fix this issue ?
-
First, Multi-WAN doesn't do what you're describing. What's in your Status > System Logs, Gateways?? How is your gateway failover group configured?
Second, there are no iptables in pfSense. Only pf.
-
well maybe im wrong about how it works, i just describe what we see, we have total 5 gateways, 2 days now one dsl is down because of a problem in dslam in this area.
every time that pfsense tries to communicate (we have set it to 80000ms) with this dsl to see if it is online and of course its not cause of the dslam problem, all the states have a mini disconnect and its send an email to us "MONITOR: DSL1_OTEGW is down, omitting from routing group oteDsl". why pfsense repeat this process when the last state of the dsl is the same with the new state.btw if i disable the gateway monitoring in that dsl, the problem stops but then pfsense thinks that this dsl is back online and it is trying to send states from that line, causing of course timeouts because the line its not actually online. i will collect and post the system logs you ask.
Thanks in advance,
George. -
Here is the log
Jun 22 12:24:44 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 46836us stddev 41923us loss 21%
Jun 22 12:25:43 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 85148us stddev 46617us loss 12%
Jun 22 12:49:16 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 32966us stddev 22022us loss 21%
Jun 22 12:50:35 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 33486us stddev 23395us loss 5%
Jun 22 13:25:01 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 118669us stddev 60640us loss 21%
Jun 22 13:26:27 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 98652us stddev 50367us loss 15%
Jun 22 14:24:17 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 57217us stddev 37804us loss 22%
Jun 22 14:25:28 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 67861us stddev 42567us loss 12%
Jun 23 00:46:27 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 24358us stddev 960us loss 21%
Jun 23 00:47:32 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 26411us stddev 17599us loss 5%
Jun 23 09:31:53 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 154639us stddev 44606us loss 21%
Jun 23 09:32:03 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 154914us stddev 44866us loss 18%
Jun 23 09:40:32 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 500174us stddev 150098us loss 0%
Jun 23 09:41:35 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 483529us stddev 140342us loss 0%
Jun 23 09:46:09 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 500050us stddev 137498us loss 2%
Jun 23 09:46:19 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 464468us stddev 143386us loss 2%
Jun 23 11:25:54 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 182043us stddev 53477us loss 21%
Jun 23 11:26:58 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 155630us stddev 51269us loss 16%
Jun 23 12:54:47 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 143201us stddev 47642us loss 21%
Jun 23 12:55:32 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 158320us stddev 55273us loss 15%
Jun 23 13:01:24 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 157542us stddev 43783us loss 21%
Jun 23 13:03:06 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 150640us stddev 32527us loss 16%
Jun 23 13:24:31 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 167059us stddev 49448us loss 21%
Jun 23 13:25:01 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 163023us stddev 47523us loss 18%
Jun 23 13:25:46 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 161920us stddev 47098us loss 21%
Jun 23 13:26:23 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 155146us stddev 44622us loss 18%
Jun 23 13:33:39 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 173871us stddev 63108us loss 21%
Jun 23 13:35:16 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 152623us stddev 36155us loss 15%
Jun 23 15:55:38 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 119043us stddev 53037us loss 21%
Jun 23 15:56:06 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 101716us stddev 49231us loss 16%
Jun 23 16:06:58 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 149319us stddev 40999us loss 21%
Jun 23 16:07:19 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 134881us stddev 41304us loss 18%
Jun 23 16:24:18 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 153979us stddev 40050us loss 21%
Jun 23 16:24:28 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 144816us stddev 43808us loss 15%
Jun 23 18:02:00 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 23 18:13:18 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 505650us stddev 150824us loss 6%
Jun 23 18:13:32 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 469397us stddev 166144us loss 14%
Jun 24 09:46:21 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 83021us stddev 29742us loss 21%
Jun 24 09:47:28 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 45437us stddev 28816us loss 15%
Jun 24 11:04:50 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 144895us stddev 36749us loss 21%
Jun 24 11:06:23 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 147626us stddev 39464us loss 20%
Jun 24 11:06:25 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 147364us stddev 40560us loss 22%
Jun 24 11:06:47 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 118876us stddev 61853us loss 15%
Jun 24 11:50:28 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 128758us stddev 54563us loss 21%
Jun 24 11:50:53 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 127106us stddev 57111us loss 17%
Jun 24 12:01:50 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 155780us stddev 52842us loss 21%
Jun 24 12:03:10 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 188221us stddev 81075us loss 16%
Jun 24 12:43:38 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 24 12:45:05 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 24 12:46:15 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 24 15:16:30 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 25 20:42:09 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 24506us stddev 1994us loss 21%
Jun 25 20:44:36 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 24845us stddev 6073us loss 5%
Jun 26 19:17:07 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 25525us stddev 6931us loss 22%
Jun 26 19:18:13 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 24004us stddev 1391us loss 5%
Jun 26 20:14:29 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 25793us stddev 16271us loss 22%
Jun 26 20:15:29 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 25117us stddev 5827us loss 5%
Jun 27 09:40:38 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 84175us stddev 38999us loss 21%
Jun 27 09:40:49 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 90879us stddev 50908us loss 20%
Jun 27 15:16:35 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 28 01:10:13 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 28 01:10:24 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 28 16:51:36 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 28 16:51:52 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 28 17:24:14 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 28 20:50:15 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 500341us stddev 184747us loss 0%
Jun 28 20:50:25 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 456834us stddev 162358us loss 0%
Jun 28 20:50:39 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 506265us stddev 143694us loss 1%
Jun 28 20:51:56 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 403405us stddev 243206us loss 0%
Jun 28 22:17:29 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 35479us stddev 49785us loss 21%
Jun 28 22:18:41 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 25227us stddev 5778us loss 5%
Jun 29 00:21:52 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 00:21:59 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 00:22:37 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 00:39:49 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 00:42:47 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 01:29:13 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 09:19:25 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 30567us stddev 23494us loss 22%
Jun 29 09:38:13 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 09:38:16 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 0us stddev 0us loss 100%
Jun 29 10:36:25 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 10:36:28 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 0us stddev 0us loss 100%
Jun 29 14:15:53 dpinger send_interval 86400ms loss_interval 2000ms time_period 180000ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 14:16:21 dpinger send_interval 86400ms loss_interval 2000ms time_period 180000ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 14:19:07 dpinger send_interval 86400ms loss_interval 2000ms time_period 180000ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 14:20:03 dpinger send_interval 86400ms loss_interval 2000ms time_period 180000ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 14:20:48 dpinger send_interval 86400ms loss_interval 2000ms time_period 180000ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 14:23:41 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 0us stddev 0us loss 100%
Jun 29 19:00:38 dpinger send_interval 86400ms loss_interval 2000ms time_period 180000ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 29 19:03:31 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 0us stddev 0us loss 100%
Jun 30 00:52:26 dpinger send_interval 86400ms loss_interval 345600ms time_period 527400ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 30 00:53:18 dpinger send_interval 86400ms loss_interval 345600ms time_period 527400ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 30 00:53:49 dpinger send_interval 86400ms loss_interval 345600ms time_period 527400ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 30 00:59:00 dpinger send_interval 86400ms loss_interval 345600ms time_period 527400ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 30 01:06:13 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 0us stddev 0us loss 100%
Jun 30 12:38:46 dpinger send_interval 86400ms loss_interval 345600ms time_period 527400ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 30 12:45:58 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 0us stddev 0us loss 100%
Jun 30 12:48:23 dpinger send_interval 86400ms loss_interval 345600ms time_period 527400ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 30 12:48:53 dpinger send_interval 5000ms loss_interval 345600ms time_period 527400ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW "
Jun 30 12:49:04 dpinger send_interval 5000ms loss_interval 345600ms time_period 527400ms report_interval 0ms data_len 0 alert_interval 86500ms latency_alarm 800ms loss_alarm 20% dest_addr xxx.xxx.xxx.xxx bind_addr 192.168.4.253 identifier "DSL1_OTEGW " -
Jun 22 12:24:44 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 46836us stddev 41923us loss 21%
Jun 22 12:25:43 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 85148us stddev 46617us loss 12%
Jun 22 12:49:16 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 32966us stddev 22022us loss 21%
Jun 22 12:50:35 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 33486us stddev 23395us loss 5%
Jun 22 13:25:01 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 118669us stddev 60640us loss 21%
Jun 22 13:26:27 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 98652us stddev 50367us loss 15%
Jun 22 14:24:17 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 57217us stddev 37804us loss 22%
Jun 22 14:25:28 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 67861us stddev 42567us loss 12%
Jun 23 00:46:27 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 24358us stddev 960us loss 21%
Jun 23 00:47:32 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 26411us stddev 17599us loss 5%
Jun 23 09:31:53 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Alarm latency 154639us stddev 44606us loss 21%
Jun 23 09:32:03 dpinger DSL1_OTEGW xxx.xxx.xxx.xxx: Clear latency 154914us stddev 44866us loss 18%In that case Multi-WAN is doing exactly what it is supposed to be doing. For a persistent case like that, you might want to just mark the gateway as down in System > Routing, Gateways, Force state - Mark gateway as down.
In more detail even though the ISP connection is practically useless, it is responding to pings on its monitoring IP address enough to flap the gateway. You can either change the monitoring characteristics or perhaps change the monitoring IP address to something farther out. 8.8.8.8 or 8.8.4.4 are good initial choices. System > Routing, Gateways, Edit - Monitor IP. It looks like you might have made some headway in that regard later in the logs.
-
Well thanks for your respond Derelict but i think you miss understand me.
I just didn't want pfsense to flush the states and causing disconnects when a dsl goes down
Our problem has been resolved from the following setting: System/Advanced/Miscellaneous/Gateway Monitoring -> State Killing on Gateway Failure (Flush all states when a gateway goes down)
Thanks a lot for your time and your help.
