PFSense hangs when certain device connects to network
-
@bmeeks said in PFSense hangs when certain device connects to network:
seem to be able to login to the Unifi Controller
But is he doing that remote from another device on the network - or is he local on the device running the controller?
Can not really tell from the info given so far.
-
Yeah, not enough information to make a more definitive hypothesis. But the only two things I can imagine that would account for the symptoms he posted are a network loop or an IP address conflict. The fact he has tried two different Ring devices with the same result would tend to rule out a defective Ring device.
-
@bmeeks Kind of also rules out a static IP set wrong? But not exactly sure how ring sets IP - might be like unifi when you set a device to a static IP, it learns that from the controller?
Would be moronic for such a device to default to .1 or .254 that would most likely conflict with router on network.
-
@johnpoz said in PFSense hangs when certain device connects to network:
@bmeeks Kind of also rules out a static IP set wrong? But not exactly sure how ring sets IP - might be like unifi when you set a device to a static IP, it learns that from the controller?
I've never configured one of those Ring devices, so not sure how it defaults out of the box. I would assume some kind of wireless SSID of its own that you connect to with your phone to initially configure it by giving it the credentials for your own wireless network.
I set up a Wyze camera a while back for someone and that's how it worked. Out of the box it had its own little wireless that you connected to (or it might have been Bluetooth), and then you configured it for your network from your phone.
-
@Sikh said in PFSense hangs when certain device connects to network:
That’s one thing I forgot to mention. When this happens, it’s only the LAN that’s choking. I can sit at the shell and do a speedtest and I can go back to the main menu and do a ping out to anything and it works fine. I can also run a trade route and no issues at all.
So during this WAN works fine but LAN is completely choking. I checked top and idle was 97% like it always is. Memory was also mostly free like it always is.
I have a feeling this either has something to do with DHCP leases and when the doorbell goes to renew it OR something with this update and some piece of traffic the doorbell is sending is choking the NIC. At first I thought it was the doorbell but after getting a brand new one and having the issue, I’m thinking it might be something in 2.5.2 but I also know rolling back means reinstalling the entire OS and there’s no other way to downgrade.
I also thought of something else I can do. I’m going to start a packet capture from the shell and then have my doorbell connect and see if I’m able to capture the traffic it sends until my LAN is choked. Hopefully I can see something before my LAN gets choked and I have to block it on my unifi controller.
Did you ever solve this? My LAN is also choking randomly every few hours - pfSense LAN interface becomes unresponsive. WAN works fine, no errors in my logs either.
-
@coolspot said in PFSense hangs when certain device connects to network:
pfSense LAN interface becomes unresponsive.
In what way? How are you testing it?
Are other LAN side devices able to connect to each other?
-
@stephenw10 said in PFSense hangs when certain device connects to network:
@coolspot said in PFSense hangs when certain device connects to network:
pfSense LAN interface becomes unresponsive.
In what way? How are you testing it?
Are other LAN side devices able to connect to each other?
It is very odd - I've be struggling with this for the past few weeks:
-
LAN interface becomes unresponsive and drops packets
-
Console remains functional and I can ping to WAN (next time I'm going to run to the console to ping LAN as well)
-
I can ping other LAN devices from my PC - no dropped packets, so I have isolated the issue to pfSense
-
Smart Netgear Switch reports no errors
-
No obvious errors in logs or dmesg, closest perhaps is unbound has a HUP exit and restart
-
System recovers after 1-2 minutes but that is enough to interrupt streams
-
Ran memtest86 no issues
-
Swapped three different NICs and ports
-
Swapped CAT6 cables
-
Swapped Network ports and Switch
-
Did a reinstall of CE and still see the issue albeit much less frequently
-
System has Intel I219 and I225-LM NICs - it used to be virtualized and ran solid for years. My issues seem to have cropped up when I reverted to baremetal
Nothing is logged in pfSense which I find very odd.
As a side note, is there a way to get timestamps from dmesg?
-
-
@coolspot said in PFSense hangs when certain device connects to network:
As a side note, is there a way to get timestamps from dmesg?
No, but you can check the system log from the console to see timestamps. /var/log/system.log
Is LAN the i225 NIC? Is there anything logged when it stops responding?
Can you re-assign LAN to a different NIC?
-
@stephenw10 I moved my NICs around and the issue remains.
I ran a PingPlotter overnight and interesting found that the issue happens almost every two hours - it seems too coincidental to be hardware related?
I ran a Wireshark trace but couldn't see anything obvious in the logs.
Nothing is logged on my switch either - errors or otherwise.
Is there any cronjob on the firewall that runs every two hours? I did a fresh installation and restore of pfSense 2.7.2 CE so the config should be pretty standard.
-
I would have to say it's more likely a rogue DHCP server stealing the IP address. That could be at 2 hour intervals.
I would try checking the ARP table on a client when it stops and make sure it's still using the correct MAC address.
