WAN disconnects then reconnects several times each day
-
I installed PFSense 2.0.1 about 2 years ago at home and it ran fine until about 2 weeks ago. At that time I began experiencing WAN disconnects. Although the disconnects were somewhat random, the majority were 18-20 minutes apart. The WAN link would be down for 1-3 minutes then return without any intervention on my part. My WAN is on a static IP address. My ISP changed my static IP and gateway but that made no difference. I installed PFSense 2.1 (vanilla – no rules, no VPN, etc.). Same issue. I then tried various settings for the NICs. Same issue. I also disabled state killing then disabled gateway monitoring (as per https://forum.pfsense.org/index.php?topic=63052.msg340719#msg340719) but that had no effect. Flushing ARP cache was also useless.
Over the weekend I installed a new disk in another PC and built a new PFSense box. This install also has different NICs and Ethernet cables. This install was done from scratch - I did not restore a previous config. Same issue but I found one interesting thing. If I leave the Web Configurator running on my main PC and begin doing something on the internet, when the WAN link goes down I can tap SAVE/APPLY in the web configurator and my WAN is instantly restored - otherwise I have to wait 1-3 minutes for the connection to return on its own.
When the WAN goes down there is always a line on system logs (below) that points to ‘updating dyndns WANGW’. I disabled dyndns in CRON but wasn’t aware of where else I may need to make changes for additional troubleshooting. Also in the logs it references ‘restarting ipsec tunnels and OpenVPN’. I disabled my ipsec vpn and there are no entries for OpenVPN in my config. Same issue.
The current hardware config is a Dell Optiplex 360 with 2 GB RAM, a Broadcom 10/100/1000 (bge0) for the WAN and a VIA Technologies 10/100 (vr0) for the LAN side. BTW, I also swapped the NICs and reconfigured PFSense but the problem remained.
Note: If PFSense is removed from the environment, everything runs flawless – no disconnects.
I’ve included a portion of the system and gateway logs below. Gateway monitoring has been turned back on since disabling it made no difference.
If anyone can tell me what I’ve overlooked, I’d REALLY appreciate it!!!!!!!! Thanks in advance for any suggestions.
Mar 20 06:56:49 check_reload_status: updating dyndns WANGW
Mar 20 06:56:49 check_reload_status: Restarting ipsec tunnels
Mar 20 06:56:49 check_reload_status: Restarting OpenVPN tunnels/interfaces
Mar 20 06:56:49 check_reload_status: Reloading filter
Mar 20 06:57:07 php: rc.newipsecdns: IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
Mar 20 06:58:22 check_reload_status: updating dyndns WANGW
Mar 20 06:58:22 check_reload_status: Restarting ipsec tunnels
Mar 20 06:58:22 check_reload_status: Restarting OpenVPN tunnels/interfaces
Mar 20 06:58:22 check_reload_status: Reloading filter
Mar 20 06:58:40 php: rc.newipsecdns: IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
Mar 20 08:16:57 check_reload_status: updating dyndns WANGW
Mar 20 08:16:57 check_reload_status: Restarting ipsec tunnels
Mar 20 08:16:57 check_reload_status: Restarting OpenVPN tunnels/interfaces
Mar 20 08:16:57 check_reload_status: Reloading filter
Mar 20 08:17:15 php: rc.newipsecdns: IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
Mar 20 08:18:06 check_reload_status: updating dyndns WANGW
Mar 20 08:18:06 check_reload_status: Restarting ipsec tunnels
Mar 20 08:18:06 check_reload_status: Restarting OpenVPN tunnels/interfaces
Mar 20 08:18:06 check_reload_status: Reloading filter
Mar 20 08:18:24 php: rc.newipsecdns: IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.Mar 20 03:58:00 apinger: ALARM: WANGW(173.239.90.1) *** down ***
Mar 20 03:58:47 apinger: alarm canceled: WANGW(173.239.90.1) *** down ***
Mar 20 04:14:23 apinger: ALARM: WANGW(173.239.90.1) *** down ***
Mar 20 04:18:43 apinger: alarm canceled: WANGW(173.239.90.1) *** down ***
Mar 20 05:17:59 apinger: ALARM: WANGW(173.239.90.1) *** down ***
Mar 20 05:18:31 apinger: alarm canceled: WANGW(173.239.90.1) *** down ***
Mar 20 05:36:12 apinger: ALARM: WANGW(173.239.90.1) *** down ***
Mar 20 05:38:27 apinger: alarm canceled: WANGW(173.239.90.1) *** down ***
Mar 20 05:57:39 apinger: ALARM: WANGW(173.239.90.1) *** down ***
Mar 20 05:58:24 apinger: alarm canceled: WANGW(173.239.90.1) *** down ***
Mar 20 06:56:39 apinger: ALARM: WANGW(173.239.90.1) *** down ***
Mar 20 06:58:12 apinger: alarm canceled: WANGW(173.239.90.1) *** down ***
Mar 20 08:16:47 apinger: ALARM: WANGW(173.239.90.1) *** down ***
Mar 20 08:17:56 apinger: alarm canceled: WANGW(173.239.90.1) *** down *** -
Hi!
Any errors on interface status?
-
If the error count is accumulative, there are none shown.
Status up
MAC address 1c:af:f7:0e:57:da
IPv4 address xxx.xxx.xx.xx
Subnet mask IPv4 255.255.255.0
Gateway IPv4 WANGW xxx.xxx.xx.x
IPv6 Link Local fe80::1eaf:f7ff:fe0e:57da%vr0
ISP DNS servers 127.0.0.1
xxx.xxx.xxx.xxx
x.x.x.x
Media 100baseTX <full-duplex>In/out packets 701359/732555 (328.44 MB/324.27 MB)
In/out packets (pass) 701359/732555 (328.44 MB/324.27 MB)
In/out packets (block) 716/2 (121 KB/152 bytes)
In/out errors 0/0
Collisions 0</full-duplex>