Works for a while. But just a while.
-
I've got a strange issue with a new pfSense install. 2.5, brand new clean install on bare metal i3-4130, 8GB RAM, Intel quad NIC. It works for a few page loads, then stops.
I am switching from a USG (minimal configuration), which works as expected. The Xfinity/Comcast modem is in bridge mode. For pfSense, the only thing I've done after the install is the wizard, setting the timezone and password. Nothing else, no packages or other changed settings. WAN is DHCP and pulls an IP from the modem.
The first few (roughly 20, more or less) sites load normally, including pages I haven't been to in years. tracert's look like this:
tracert pbs.org
Tracing route to pbs.org [54.225.206.152]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms pfSense.localdomain [192.168.1.1]
2 14 ms 14 ms 14 ms 10.61.220.2
3 6 ms 6 ms 11 ms ge-101-0-0-0-sur02.kernan.fl.jacksvil.comcast.net [68.85.95.129]
4 8 ms 7 ms 7 ms 96.108.89.245
5 7 ms 7 ms 7 ms 96.108.89.209
6 16 ms 16 ms 16 ms be-33489-cr02.miami.fl.ibone.comcast.net [68.86.95.45]
7 14 ms 15 ms 17 ms be-12297-pe03.nota.fl.ibone.comcast.net [68.86.82.70]
8 18 ms 15 ms 13 ms 96-87-8-158-static.hfc.comcastbusiness.net [96.87.8.158]
...But after going to a few sites, suddenly things just stop. Websites sit in a loading status until they finally fail with a message that the server took too long to reply. Even websites that loaded normally minutes earlier. pfsense page is still working fine, as is the internal network. pfsense System Info shows CPU temp is 28 degrees, memory usage 4%, /var/run is 3%, and State table size, cpu usage, swap usage and disk usage all at 0%.
tracert's now look like this:
tracert pbs.org
Tracing route to pbs.org [54.225.206.152]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms pfSense.localdomain [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * 15 ms * be-12297-pe03.nota.fl.ibone.comcast.net [68.86.82.70]
8 * * * Request timed out.
...I'm not a log expert, but I don't see anything obvious. I've swapped the NIC with another, and swapped the motherboard with a Supermicro with E3-1230v3, swapped SSD (new install obviously), and see the same issue. Tried version 2.4.4 - same thing. Swapped DNS servers to 1.1.1.1 and 1.0.0.1, unchecked the DNS Server Override, same thing.
Any idea what's going on here? And why it doesn't happen until a few minutes into browsing? Rebooting pfsense lets things load normally for a few more minutes, then it quits again a while later. Switching back to the USG gets things back to normal indefinitely. I don't get it.