pfSense goes silent, then resumes operation, repeatedly
-
My device looses connection repeatedly during the day. Noticed this issue after updating to 2.4.4-RELEASE-p3. Don't know if it is related.
My pings are going through for several minutes then there is silence for several seconds, after which my device begins responding to pings again.
I've noticed this in my log:
Jun 9 04:27:30 check_reload_status Reloading filter Jun 9 04:27:30 check_reload_status Reloading filter Jun 9 04:27:30 php-fpm 341 /rc.linkup: Linkup detected on disabled interface...Ignoring Jun 9 04:27:30 php-fpm 48611 /rc.linkup: Linkup detected on disabled interface...Ignoring Jun 9 04:27:30 php-fpm 65905 /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.168.1.1 ) Jun 9 04:27:29 check_reload_status Linkup starting igb1.10 Jun 9 04:27:29 check_reload_status Linkup starting igb1.20 Jun 9 04:27:29 kernel igb1.10: link state changed to DOWN Jun 9 04:27:29 kernel igb1.20: link state changed to DOWN Jun 9 04:27:29 kernel igb1: link state changed to DOWN Jun 9 04:27:29 check_reload_status Linkup starting igb1 Jun 9 04:19:49 check_reload_status Reloading filter Jun 9 04:19:49 php-fpm 65905 /rc.newwanip: rc.newwanip: on (IP address: 192.168.1.1) (interface: LAN[lan]) (real interface: igb1). Jun 9 04:19:49 php-fpm 65905 /rc.newwanip: rc.newwanip: Info: starting on igb1. Jun 9 04:19:48 check_reload_status rc.newwanip starting igb1 Jun 9 04:19:48 check_reload_status Reloading filter Jun 9 04:19:48 check_reload_status Reloading filter Jun 9 04:19:48 php-fpm 340 /rc.linkup: Linkup detected on disabled interface...Ignoring Jun 9 04:19:48 php-fpm 48611 /rc.linkup: Linkup detected on disabled interface...Ignoring Jun 9 04:19:48 php-fpm 65905 /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.168.1.1 ) Jun 9 04:19:47 check_reload_status Linkup starting igb1.10 Jun 9 04:19:47 check_reload_status Linkup starting igb1.20 Jun 9 04:19:47 check_reload_status Linkup starting igb1 Jun 9 04:19:47 kernel igb1.10: link state changed to UP Jun 9 04:19:47 kernel igb1.20: link state changed to UP Jun 9 04:19:47 kernel igb1: link state changed to UP Jun 9 04:19:22 check_reload_status Reloading filter Jun 9 04:19:22 check_reload_status Reloading filter Jun 9 04:19:22 php-fpm 65905 /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.168.1.1 ) Jun 9 04:19:22 php-fpm 341 /rc.linkup: Linkup detected on disabled interface...Ignoring Jun 9 04:19:22 php-fpm 340 /rc.linkup: Linkup detected on disabled interface...Ignoring Jun 9 04:19:21 check_reload_status Linkup starting igb1.10 Jun 9 04:19:21 check_reload_status Linkup starting igb1.20 Jun 9 04:19:21 kernel igb1.10: link state changed to DOWN Jun 9 04:19:21 kernel igb1.20: link state changed to DOWN Jun 9 04:19:21 kernel igb1: link state changed to DOWN Jun 9 04:19:21 check_reload_status Linkup starting igb1 Jun 9 03:30:28 check_reload_status Reloading filter Jun 9 03:30:28 php-fpm 65905 /rc.newwanip: rc.newwanip: on (IP address: 192.168.1.1) (interface: LAN[lan]) (real interface: igb1). Jun 9 03:30:28 php-fpm 65905 /rc.newwanip: rc.newwanip: Info: starting on igb1. Jun 9 03:30:27 check_reload_status rc.newwanip starting igb1 Jun 9 03:30:27 check_reload_status Reloading filter Jun 9 03:30:27 check_reload_status Reloading filter Jun 9 03:30:27 php-fpm 340 /rc.linkup: Linkup detected on disabled interface...Ignoring Jun 9 03:30:27 php-fpm 48611 /rc.linkup: Linkup detected on disabled interface...Ignoring Jun 9 03:30:27 php-fpm 65905 /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.168.1.1 ) Jun 9 03:30:26 check_reload_status Linkup starting igb1.10 Jun 9 03:30:26 check_reload_status Linkup starting igb1.20 Jun 9 03:30:26 check_reload_status Linkup starting igb1 Jun 9 03:30:26 kernel igb1.10: link state changed to UP Jun 9 03:30:26 kernel igb1.20: link state changed to UP Jun 9 03:30:26 kernel igb1: link state changed to UP Jun 9 03:30:01 php-fpm 65905 /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.168.1.1 ) Jun 9 03:30:01 check_reload_status Reloading filter Jun 9 03:30:01 check_reload_status Reloading filterAny recommendations on the cause and a possible fix?
-
@MarekAndreansky
verify cabling and check switch logs. Post those as well please. -
Apologies for the timestamps having the incorrect date , it seems it was not set up when the device was first configured.
1 2006-08-12 09:17:48 Log level_6 Backup log file by user on web (192.168.1.1). 2 2006-08-12 09:17:27 Link level_5 Gi1/0/8 changed state to up. 3 2006-08-12 09:17:01 Link level_5 Gi1/0/8 changed state to down. 4 2006-08-12 09:16:08 Link level_5 Gi1/0/8 changed state to up. 5 2006-08-12 09:16:07 Monitor level_4 CPU RISING THRESHOLD: Total CPU Utilization is 85%. 6 2006-08-12 09:16:02 User level_5 Login the web by user on web (192.168.1.1). 7 2006-08-12 09:15:43 Link level_5 Gi1/0/8 changed state to down. 8 2006-08-12 08:41:42 Link level_5 Gi1/0/8 changed state to up. 9 2006-08-12 08:41:17 Link level_5 Gi1/0/8 changed state to down. 10 2006-08-12 08:33:10 Link level_5 Gi1/0/8 changed state to up. 11 2006-08-12 08:32:44 Link level_5 Gi1/0/8 changed state to down. 12 2006-08-12 08:26:58 Link level_5 Gi1/0/8 changed state to up. 13 2006-08-12 08:26:32 Link level_5 Gi1/0/8 changed state to down. 14 2006-08-12 08:24:25 Link level_5 Gi1/0/8 changed state to up. 15 2006-08-12 08:23:59 Link level_5 Gi1/0/8 changed state to down. 16 2006-08-12 08:21:03 Link level_5 Gi1/0/8 changed state to up. 17 2006-08-12 08:20:38 Link level_5 Gi1/0/8 changed state to down. 18 2006-08-12 08:14:26 Link level_5 Gi1/0/8 changed state to up. 19 2006-08-12 08:14:01 Link level_5 Gi1/0/8 changed state to down. 20 2006-08-12 08:08:54 Link level_5 Gi1/0/8 changed state to up. 21 2006-08-12 08:08:28 Link level_5 Gi1/0/8 changed state to down. 22 2006-08-12 07:59:43 Link level_5 Gi1/0/8 changed state to up. 23 2006-08-12 07:59:18 Link level_5 Gi1/0/8 changed state to down. 24 2006-08-12 07:23:52 Link level_5 Gi1/0/8 changed state to up. 25 2006-08-12 07:23:26 Link level_5 Gi1/0/8 changed state to down. 26 2006-08-12 07:07:42 Link level_5 Gi1/0/8 changed state to up. 27 2006-08-12 07:07:17 Link level_5 Gi1/0/8 changed state to down. 28 2006-08-12 06:57:29 Link level_5 Gi1/0/8 changed state to up. 29 2006-08-12 06:57:03 Link level_5 Gi1/0/8 changed state to down. 30 2006-08-12 06:38:06 Link level_5 Gi1/0/8 changed state to up. 31 2006-08-12 06:37:40 Link level_5 Gi1/0/8 changed state to down. 32 2006-08-12 06:08:02 Link level_5 Gi1/0/8 changed state to up. 33 2006-08-12 06:07:37 Link level_5 Gi1/0/8 changed state to down. 34 2006-08-12 03:46:56 Link level_5 Gi1/0/8 changed state to up. 35 2006-08-12 03:46:31 Link level_5 Gi1/0/8 changed state to down. 36 2006-08-12 03:26:23 Link level_5 Gi1/0/8 changed state to up. 37 2006-08-12 03:25:57 Link level_5 Gi1/0/8 changed state to down. 38 2006-08-12 02:39:44 Link level_5 Gi1/0/8 changed state to up. 39 2006-08-12 02:39:18 Link level_5 Gi1/0/8 changed state to down. 40 2006-08-12 02:26:32 Link level_5 Gi1/0/8 changed state to up. 41 2006-08-12 02:26:07 Link level_5 Gi1/0/8 changed state to down. 42 2006-08-12 02:14:27 Link level_5 Gi1/0/8 changed state to up. 43 2006-08-12 02:14:01 Link level_5 Gi1/0/8 changed state to down. 44 2006-08-12 02:07:08 Link level_5 Gi1/0/8 changed state to up. 45 2006-08-12 02:06:42 Link level_5 Gi1/0/8 changed state to down. 46 2006-08-12 02:01:27 Link level_5 Gi1/0/8 changed state to up. 47 2006-08-12 02:01:02 Link level_5 Gi1/0/8 changed state to down. 48 2006-08-12 01:54:01 Link level_5 Gi1/0/8 changed state to up. 49 2006-08-12 01:53:35 Link level_5 Gi1/0/8 changed state to down. 50 2006-08-12 01:46:33 Link level_5 Gi1/0/8 changed state to up. 51 2006-08-12 01:46:08 Link level_5 Gi1/0/8 changed state to down. 52 2006-08-12 01:43:18 Link level_5 Gi1/0/8 changed state to up. 53 2006-08-12 01:42:53 Link level_5 Gi1/0/8 changed state to down. 54 2006-08-12 01:30:27 Link level_5 Gi1/0/8 changed state to up. 55 2006-08-12 01:30:01 Link level_5 Gi1/0/8 changed state to down. 56 2006-08-12 01:22:18 Link level_5 Gi1/0/8 changed state to up. 57 2006-08-12 01:21:53 Link level_5 Gi1/0/8 changed state to down. 58 2006-08-12 00:32:57 Link level_5 Gi1/0/8 changed state to up. 59 2006-08-12 00:32:32 Link level_5 Gi1/0/8 changed state to down. 60 2006-08-11 23:58:04 Link level_5 Gi1/0/8 changed state to up. 61 2006-08-11 23:57:39 Link level_5 Gi1/0/8 changed state to down. 62 2006-08-11 23:56:26 Link level_5 Gi1/0/8 changed state to up. 63 2006-08-11 23:56:01 Link level_5 Gi1/0/8 changed state to down. 64 2006-08-11 23:53:01 Link level_5 Gi1/0/8 changed state to up. 65 2006-08-11 23:52:35 Link level_5 Gi1/0/8 changed state to down. 66 2006-08-11 23:05:30 Link level_5 Gi1/0/8 changed state to up. 67 2006-08-11 23:05:04 Link level_5 Gi1/0/8 changed state to down. -
Is there a way to test cabling via pfSense?
-
There isn't. I'd suggest double checking the cable and ensuring (if it was self crimped) that all cables are fully seated, and the pins on the rj45 aren't bent. Also verify the cable is fully seated on both ends.
If the cable wasn't self crimped, first start by swapping ports on the switch side to verify if the switch port is fine. if the issue continues to happen then change the cable out.
-
That shows the link is actually going down, both ends logging it.
What is that link?
If no other switch ports of pfSense interfaces are flapping it's probably a bad cable or port.
Swap out the cable if it's easy to do.
Try re-assigning that interface to a different NIC in pfSense, does the fault follow the interface or remain with the NIC.
Try changing the port on the switch.
Steve
-
Thanks for the help @isolatedvirus and @stephenw10
My plan is to replace the cable, and if that fails use a different port on a switch, then on the firewall to determine the cause of the issue.
-
@MarekAndreansky said in pfSense goes silent, then resumes operation, repeatedly:
Is there a way to test cabling via pfSense?
As said : there isn't.
But, as you know, you have a WAN and LAN.
What about swapping cables
If the problems move to a new interface - on WAN for example then you know that your problem is the cable.
If it is the same interface, you know that you should focus on a that interface (NIC) - check both sides.
