Synology Backup Kills PFSense
-
I recently started using a Synology NAS for backup of M365 environment and since enabling theBackup for M365 have had problems with my PFSense going offline and requiring me to turn off/on the power to the device. It is happening consistently whenever the backup job kicks off.
My internet connection is a 1GB cable connection (1gbps down / 45 mbps up). My PFSense box is a Zotac MI660Nano (quad core intel, 8gb ram, Samsung SSD).
When running the ABforM365 sometimes it will die after a few minutes and other times it can download 50-150GB before an issue occurs. I can see during this time it may have download speeds of anywhere from 5-70MBs as reported by the PFSense dashboard. PFSense will then randomly go totally offline - non-pingable totally locked up, can’t access the internet from any device. If I force it off and back on the downloads can resume and internet access from other machines resume.
I can see an error 64 in the PFSense gateway log as well as a php-fpm error (after the fact) but I can’t do or try anything as its totally locked up and unresponsive.
I have run this same PFSense box for years with no issues when downloading large files (several GB files, streaming video) or even uploading TBs of data to a backup provider.
I was able to capture the system & gateway logs but haven't been able to discern anything use from them. Any ideas on what's going on or how to fix it?
SYSTEM:
Feb 26 23:00:24 pfsense php-fpm[81785]: /rc.openvpn: Gateway, none 'available' for inet6, use the first one configured. ''
Feb 26 23:00:24 pfsense php-fpm[14541]: /rc.dyndns.update: phpDynDNS (pfsense.bluehome.xyz): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Feb 26 23:00:27 pfsense check_reload_status[381]: updating dyndns wan
Feb 26 23:00:27 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:00:28 pfsense php-fpm[81785]: /rc.dyndns.update: phpDynDNS (pfsense.bluehome.xyz): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Feb 26 23:01:21 pfsense rc.gateway_alarm[2077]: >>> Gateway alarm: WAN_DHCP (Addr:66.123.145.1 Alarm:0 RTT:10.865ms RTTsd:21.684ms Loss:5%)
Feb 26 23:01:21 pfsense check_reload_status[381]: updating dyndns WAN_DHCP
Feb 26 23:01:21 pfsense check_reload_status[381]: Restarting ipsec tunnels
Feb 26 23:01:21 pfsense check_reload_status[381]: Restarting OpenVPN tunnels/interfaces
Feb 26 23:01:21 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:01:22 pfsense php-fpm[28364]: /rc.openvpn: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Feb 26 23:01:22 pfsense php-fpm[28364]: /rc.openvpn: Gateway, none 'available' for inet6, use the first one configured. ''
Feb 26 23:01:22 pfsense php-fpm[342]: /rc.dyndns.update: phpDynDNS (pfsense.bluehome.xyz): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Feb 26 23:20:07 pfsense kernel: re0: watchdog timeout
Feb 26 23:20:07 pfsense kernel: re0: link state changed to DOWN
Feb 26 23:20:07 pfsense check_reload_status[381]: Linkup starting re0
Feb 26 23:20:08 pfsense php-fpm[343]: /rc.linkup: DEVD Ethernet detached event for wan
Feb 26 23:20:09 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:20:11 pfsense check_reload_status[381]: Linkup starting re0
Feb 26 23:20:11 pfsense kernel: re0: link state changed to UP
Feb 26 23:20:12 pfsense php-fpm[28364]: /rc.linkup: DEVD Ethernet attached event for wan
Feb 26 23:20:12 pfsense php-fpm[28364]: /rc.linkup: HOTPLUG: Configuring interface wan
Feb 26 23:20:12 pfsense check_reload_status[381]: rc.newwanip starting re0
Feb 26 23:20:12 pfsense php-fpm[28364]: /rc.linkup: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Feb 26 23:20:12 pfsense php-fpm[28364]: /rc.linkup: Gateway, none 'available' for inet6, use the first one configured. ''
Feb 26 23:20:12 pfsense check_reload_status[381]: Restarting ipsec tunnels
Feb 26 23:20:13 pfsense php-fpm[14541]: /rc.newwanip: rc.newwanip: Info: starting on re0.
Feb 26 23:20:13 pfsense php-fpm[14541]: /rc.newwanip: rc.newwanip: on (IP address: 66.123.145.43) (interface: WAN[wan]) (real interface: re0).
Feb 26 23:20:13 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:20:17 pfsense check_reload_status[381]: updating dyndns wan
Feb 26 23:20:17 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:20:18 pfsense php-fpm[342]: /rc.dyndns.update: phpDynDNS (pfsense.bluehome.xyz): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Feb 26 23:23:12 pfsense kernel: re0: watchdog timeout
Feb 26 23:23:12 pfsense kernel: re0: link state changed to DOWN
Feb 26 23:23:12 pfsense check_reload_status[381]: Linkup starting re0
Feb 26 23:23:13 pfsense php-fpm[343]: /rc.linkup: DEVD Ethernet detached event for wan
Feb 26 23:23:14 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:23:16 pfsense rc.gateway_alarm[71224]: >>> Gateway alarm: WAN_DHCP (Addr:66.123.145.1 Alarm:1 RTT:9.597ms RTTsd:2.095ms Loss:21%)
Feb 26 23:23:16 pfsense check_reload_status[381]: updating dyndns WAN_DHCP
Feb 26 23:23:16 pfsense check_reload_status[381]: Restarting ipsec tunnels
Feb 26 23:23:16 pfsense check_reload_status[381]: Restarting OpenVPN tunnels/interfaces
Feb 26 23:23:16 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:23:16 pfsense check_reload_status[381]: Linkup starting re0
Feb 26 23:23:16 pfsense kernel: re0: link state changed to UP
Feb 26 23:23:17 pfsense php-fpm[342]: /rc.openvpn: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Feb 26 23:23:17 pfsense php-fpm[342]: /rc.openvpn: Gateway, none 'available' for inet6, use the first one configured. ''
Feb 26 23:23:17 pfsense php-fpm[14541]: /rc.dyndns.update: Dynamic DNS (pfsense.bluehome.xyz) There was an error trying to determine the public IP for interface - wan (re0 ).
Feb 26 23:23:17 pfsense php-fpm[28364]: /rc.linkup: DEVD Ethernet attached event for wan
Feb 26 23:23:17 pfsense php-fpm[28364]: /rc.linkup: HOTPLUG: Configuring interface wan
Feb 26 23:23:17 pfsense check_reload_status[381]: rc.newwanip starting re0
Feb 26 23:23:17 pfsense php-fpm[28364]: /rc.linkup: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Feb 26 23:23:17 pfsense php-fpm[28364]: /rc.linkup: Gateway, none 'available' for inet6, use the first one configured. ''
Feb 26 23:23:17 pfsense check_reload_status[381]: Restarting ipsec tunnels
Feb 26 23:23:18 pfsense php-fpm[342]: /rc.newwanip: rc.newwanip: Info: starting on re0.
Feb 26 23:23:18 pfsense php-fpm[342]: /rc.newwanip: rc.newwanip: on (IP address: 66.123.145.43) (interface: WAN[wan]) (real interface: re0).
Feb 26 23:23:18 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:23:22 pfsense check_reload_status[381]: updating dyndns wan
Feb 26 23:23:22 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:23:23 pfsense php-fpm[14541]: /rc.dyndns.update: phpDynDNS (pfsense.bluehome.xyz): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Feb 26 23:24:01 pfsense php-fpm[81785]: /index.php: Successful login for user 'cmd' from: 192.168.1.111 (Local Database)
Feb 26 23:24:15 pfsense rc.gateway_alarm[64997]: >>> Gateway alarm: WAN_DHCP (Addr:66.123.145.1 Alarm:0 RTT:10.712ms RTTsd:19.592ms Loss:5%)
Feb 26 23:24:15 pfsense check_reload_status[381]: updating dyndns WAN_DHCP
Feb 26 23:24:15 pfsense check_reload_status[381]: Restarting ipsec tunnels
Feb 26 23:24:15 pfsense check_reload_status[381]: Restarting OpenVPN tunnels/interfaces
Feb 26 23:24:15 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:24:16 pfsense php-fpm[14541]: /rc.openvpn: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Feb 26 23:24:16 pfsense php-fpm[14541]: /rc.openvpn: Gateway, none 'available' for inet6, use the first one configured. ''
Feb 26 23:24:16 pfsense php-fpm[343]: /rc.dyndns.update: phpDynDNS (pfsense.bluehome.xyz): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Feb 26 23:26:19 pfsense nginx: 2021/02/26 23:26:19 [crit] 48669#100216: *1661 SSL_write() failed (13: Permission denied) while processing HTTP/2 connection, client: 192.168.1.111, server: 0.0.0.0:8443
Feb 26 23:30:47 pfsense kernel: re0: watchdog timeout
Feb 26 23:30:47 pfsense kernel: re0: link state changed to DOWN
Feb 26 23:30:47 pfsense check_reload_status[381]: Linkup starting re0
Feb 26 23:30:48 pfsense php-fpm[342]: /rc.linkup: DEVD Ethernet detached event for wan
Feb 26 23:30:49 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:30:49 pfsense rc.gateway_alarm[25091]: >>> Gateway alarm: WAN_DHCP (Addr:66.123.145.1 Alarm:1 RTT:9.196ms RTTsd:1.720ms Loss:22%)
Feb 26 23:30:49 pfsense check_reload_status[381]: updating dyndns WAN_DHCP
Feb 26 23:30:49 pfsense check_reload_status[381]: Restarting ipsec tunnels
Feb 26 23:30:49 pfsense check_reload_status[381]: Restarting OpenVPN tunnels/interfaces
Feb 26 23:30:49 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:30:50 pfsense php-fpm[14541]: /rc.openvpn: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Feb 26 23:30:50 pfsense php-fpm[14541]: /rc.openvpn: Gateway, none 'available' for inet6, use the first one configured. ''
Feb 26 23:30:51 pfsense php-fpm[28364]: /rc.dyndns.update: Dynamic DNS (pfsense.bluehome.xyz) There was an error trying to determine the public IP for interface - wan (re0 ).
Feb 26 23:30:51 pfsense check_reload_status[381]: Linkup starting re0
Feb 26 23:30:51 pfsense kernel: re0: link state changed to UP
Feb 26 23:30:52 pfsense php-fpm[14541]: /rc.linkup: DEVD Ethernet attached event for wan
Feb 26 23:30:52 pfsense php-fpm[14541]: /rc.linkup: HOTPLUG: Configuring interface wan
Feb 26 23:30:52 pfsense check_reload_status[381]: rc.newwanip starting re0
Feb 26 23:30:52 pfsense php-fpm[14541]: /rc.linkup: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Feb 26 23:30:52 pfsense php-fpm[14541]: /rc.linkup: Gateway, none 'available' for inet6, use the first one configured. ''
Feb 26 23:30:52 pfsense check_reload_status[381]: Restarting ipsec tunnels
Feb 26 23:30:53 pfsense php-fpm[28364]: /rc.newwanip: rc.newwanip: Info: starting on re0.
Feb 26 23:30:53 pfsense php-fpm[28364]: /rc.newwanip: rc.newwanip: on (IP address: 66.123.145.43) (interface: WAN[wan]) (real interface: re0).
Feb 26 23:30:53 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:30:56 pfsense nginx: 2021/02/26 23:30:56 [crit] 48669#100216: *1664 SSL_write() failed (13: Permission denied) while processing HTTP/2 connection, client: 192.168.1.111, server: 0.0.0.0:8443
Feb 26 23:30:57 pfsense check_reload_status[381]: updating dyndns wan
Feb 26 23:30:57 pfsense check_reload_status[381]: Reloading filter
Feb 26 23:30:58 pfsense php-fpm[28364]: /rc.dyndns.update: phpDynDNS (pfsense.bluehome.xyz): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.GATEWAY:
Feb 26 23:00:17 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:00:17 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:00:18 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:00:18 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:00:19 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:00:19 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:00:20 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:00:21 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:00:21 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:00:22 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:00:23 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: Alarm latency 9370us stddev 1735us loss 22%
Feb 26 23:01:21 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: Clear latency 10865us stddev 21684us loss 5%
Feb 26 23:20:07 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:20:08 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:20:08 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:20:09 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:20:09 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:20:10 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:20:10 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:20:11 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:20:11 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:23:12 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:23:13 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:23:13 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:23:14 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:23:14 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:23:15 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:23:15 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:23:16 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: Alarm latency 9597us stddev 2095us loss 21%
Feb 26 23:23:16 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:23:16 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:23:17 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:24:15 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: Clear latency 10712us stddev 19592us loss 5%
Feb 26 23:30:47 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:30:48 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:30:48 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:30:49 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:30:49 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:30:49 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: Alarm latency 9196us stddev 1720us loss 22%
Feb 26 23:30:50 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:30:50 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:30:51 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:30:51 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:30:52 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 65
Feb 26 23:31:00 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:01 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:01 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:02 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:03 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:03 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:04 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:04 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:05 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:05 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:06 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:06 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:07 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:07 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:08 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:08 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:09 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:09 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:10 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:11 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:11 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:12 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:12 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:13 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:13 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:14 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:14 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:15 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:15 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:16 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:16 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:17 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:17 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:18 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:18 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:19 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:20 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:20 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:21 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:21 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:22 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:22 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:23 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:23 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:24 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:24 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:25 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:25 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:26 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:26 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:27 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:27 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:28 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:28 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:29 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:29 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:30 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:30 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:31 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:31 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:32 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:32 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:33 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:33 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:34 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:34 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:35 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:35 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:36 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:36 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:37 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:37 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:38 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:39 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:39 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:40 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:40 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:41 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:41 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:42 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:42 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:43 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:43 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:44 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:44 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:45 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:45 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:46 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:46 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:47 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:47 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:48 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:49 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:49 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:50 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:50 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:51 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:51 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:52 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:52 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:53 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:53 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:54 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:54 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:55 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:55 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:56 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:56 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:57 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:57 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:58 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:58 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:59 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:31:59 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:00 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:00 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:01 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:01 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:02 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:02 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:03 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:04 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:04 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:05 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:05 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:06 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:06 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:07 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:07 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:08 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:08 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:09 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:09 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:10 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:10 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:11 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:11 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64
Feb 26 23:32:12 pfsense dpinger[30300]: WAN_DHCP 66.123.145.1: sendto error: 64 -
First of all : be ware : you are using Realtek NIC's. Start pushing them and you'll discover that they will 'fail' on you.
This is the classic indicator :
@commonsense said in Synology Backup Kills PFSense:
re0: watchdog timeout
You could try the 'other' realtek package that is available for pfSense 2.5.0. See this forum for details, as the realtek is an ongoing source of issues.
Also :
@commonsense said in Synology Backup Kills PFSense:
My internet connection is a 1GB cable connection (1gbps down / 45 mbps up).
Yeah .... and if your NAS is really using this "45 Mbits up" to send it's content on the M365 cloud, it will grab all the bandwidth, and more.
Leaving no space for dpinger to have it's "gateway up test" which also isn't good.
I'm using a Syn NAS myself, and used the build in speed limiter (from the Syno NAS) so it doesn't fill the up pipe completely. -
I wondered if I was experiencing the realtek nic issue.
Also, all of this traffic is inbound. I am pulling from the M365 cloud to my onsite nas as a backup. I have seen the WAN side read as high as about 100MB (megabytes second) but mostly its sitting somewhere in the 20-50MB range when downloading this data.
Thanks @Gertjan. Based on your mention of the RealTek Issue I searched that out and found the updated driver.
After implementing the changes below my job was able to complete. I checked the logs and I no longer see any dpinger issues in the gateway log nor link state changed to DOWN messages in the system log.
For anyone looking for this it appears the old consensus was to compile the updated driver from scratch but FreeBSD does now have an official package available so that is the route I went. For anyone that isn't experienced with install packages on FreeBSD it can all be done directly from the PFSense backend as I did.
Login to your PFSense Dashboard.
- Go to Diagnostics > Command Prompt and enter the command below
pkg add https://pkg.FreeBSD.org/FreeBSD:12:amd64/latest/All/realtek-re-kmod-v196.04_2.txz
(*Note: I am using PFSense v 2.4.5 on freebsd 12. If you are using an older version of pfsense you might need to change the 12 in the above line to 11)
- After this command successfully completes go to Diagnostics > Edit File
- Click browse and open /boot/loader.conf
- Add these two lines & save the file
if_re_load="YES"
if_re_name="/boot/modules/if_re.ko"- Reboot your pfsense
-
@commonsense said in Synology Backup Kills PFSense:
I am using PFSense v 2.4.5 on freebsd 12
2.4.5-p1 is/was FreeBSD 11.x, right ?
2.4.5-p1 with 12 ??
Wow. -
@gertjan I mis-typed. I running 2.5.0 on top of freebsd 12.2.
https://docs.netgate.com/pfsense/en/latest/releases/2-5-0.html