Both WAN connections go down at nearly the same time

PhlMike

SG-3100, 23.05.1

2023-10-18 12:17:38.585260-04:00dpinger51209send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr xxx.xxx.xx.x bind_addr xxx.xxx.xx.xxx identifier "WAN2_DHCP"

2023-10-18 12:17:38.551264-04:00dpinger50592send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr yy.yy.yyy.y bind_addr yy.yy.yyy.yy identifier "WAN_DHCP"

Happens, almost daily but at random times. Majority of the time its in the middle of the night so I don't notice. They share nothing prior to the SG-3100 - including poles. I have a unique property and due to the distance, some of my own poles, they go off in completely different directions.. One goes due north and the other south-west. I know where the ISP's hubs are which makes general sense to where they are going.

I'm assuming its time for an upgrade. It must be the firewall.

stephenw10

Those logs are not the WANs going down. Those are showing dpinger starting (or re-starting) on each WAN with the values it's using.

Something else will have caused dpinger to restart, probably logged just prior to that.

Steve

PhlMike

@stephenw10 What is weird, all of my internet goes down. music stops, remote connections reconnect, etc.. despite being primarily on WAN not WAN2, wan2 is just the backup

2023-10-18 12:17:38.585260-04:00	dpinger	51209	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr xxx.xxx.xx.x bind_addr xxx.xxx.xx.xxx identifier "WAN2_DHCP "
2023-10-18 12:17:38.551264-04:00	dpinger	50592	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr yy.yy.yyy.y bind_addr yy.yy.yyy.yy identifier "WAN_DHCP "
2023-10-18 12:17:38.497300-04:00	dpinger	34246	exiting on signal 15
2023-10-18 12:17:38.352434-04:00	dpinger	35080	exiting on signal 15
2023-10-18 12:17:13.739637-04:00	dpinger	35080	WAN2_DHCP xxx.xxx.xx.x: Alarm latency 13127us stddev 8815us loss 21%
2023-10-18 11:07:34.113872-04:00	dpinger	35080	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr xxx.xxx.xx.x bind_addr xxx.xxx.xx.xxx identifier "WAN2_DHCP "
2023-10-18 11:07:34.081641-04:00	dpinger	34246	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr yy.yy.yyy.y bind_addr yy.yy.yyy.yy identifier "WAN_DHCP "
2023-10-18 11:07:34.034695-04:00	dpinger	77841	exiting on signal 15
2023-10-18 11:07:33.951296-04:00	dpinger	78362	exiting on signal 15
2023-10-18 11:07:21.460916-04:00	dpinger	78362	WAN2_DHCP yy.yy.yyy.y: Alarm latency 11612us stddev 343us loss 21%

stephenw10

Check the other logs at that time. You can see in both those cases dpinger was restarted by something shortly after WAN was marked down due to packet loss.