pfSense upgrade to 2.5.2 | now slow with bad latency

Networking & Firewalls
1

I waited to upgrade pfSense at my folks’ house until I visited. I’m glad I did.

I am having an issue with their low-end Protectli box that was working fine with v2.4.x and after the upgrade, it’s having all sorts of latency issues.

The specs…
Intel(R) Celeron(R) CPU J1800 @ 2.41GHz
Current: 2407 MHz, Max: 2408 MHz
2 CPUs: 1 package(s) x 2 core(s)
AES-NI CPU Crypto: No
QAT Crypto: No

Ping response times…
64 bytes from 172.217.5.14: icmp_seq=390 ttl=51 time=83.815 ms64 bytes from 172.217.5.14: icmp_seq=391 ttl=51 time=88.073 ms64 bytes from 172.217.5.14: icmp_seq=392 ttl=51 time=87.271 ms64 bytes from 172.217.5.14: icmp_seq=393 ttl=51 time=151.528 ms64 bytes from 172.217.5.14: icmp_seq=394 ttl=51 time=204.154 ms64 bytes from 172.217.5.14: icmp_seq=395 ttl=51 time=265.428 ms64 bytes from 172.217.5.14: icmp_seq=396 ttl=51 time=336.697 ms64 bytes from 172.217.5.14: icmp_seq=397 ttl=51 time=421.490 ms64 bytes from 172.217.5.14: icmp_seq=398 ttl=51 time=255.369 ms64 bytes from 172.217.5.14: icmp_seq=399 ttl=51 time=357.525 ms64 bytes from 172.217.5.14: icmp_seq=400 ttl=51 time=378.723 ms64 bytes from 172.217.5.14: icmp_seq=401 ttl=51 time=273.796 ms64 bytes from 172.217.5.14: icmp_seq=402 ttl=51 time=293.075 ms64 bytes from 172.217.5.14: icmp_seq=403 ttl=51 time=305.444 ms64 bytes from 172.217.5.14: icmp_seq=404 ttl=51 time=344.075 ms64 bytes from 172.217.5.14: icmp_seq=405 ttl=51 time=323.331 ms64 bytes from 172.217.5.14: icmp_seq=406 ttl=51 time=222.642 ms64 bytes from 172.217.5.14: icmp_seq=407 ttl=51 time=231.732 ms64 bytes from 172.217.5.14: icmp_seq=408 ttl=51 time=251.255 ms64 bytes from 172.217.5.14: icmp_seq=409 ttl=51 time=262.901 ms64 bytes from 172.217.5.14: icmp_seq=410 ttl=51 time=262.905 ms64 bytes from 172.217.5.14: icmp_seq=411 ttl=51 time=267.915 ms64 bytes from 172.217.5.14: icmp_seq=412 ttl=51 time=266.892 ms64 bytes from 172.217.5.14: icmp_seq=413 ttl=51 time=263.518 ms64 bytes from 172.217.5.14: icmp_seq=414 ttl=51 time=266.615 ms64 bytes from 172.217.5.14: icmp_seq=415 ttl=51 time=277.149 ms64 bytes from 172.217.5.14: icmp_seq=416 ttl=51 time=299.083 ms64 bytes from 172.217.5.14: icmp_seq=417 ttl=51 time=308.553 ms64 bytes from 172.217.5.14: icmp_seq=418 ttl=51 time=347.940 ms64 bytes from 172.217.5.14: icmp_seq=419 ttl=51 time=398.902 ms64 bytes from 172.217.5.14: icmp_seq=420 ttl=51 time=90.512 ms64 bytes from 172.217.5.14: icmp_seq=421 ttl=51 time=80.538 ms64 bytes from 172.217.5.14: icmp_seq=422 ttl=51 time=102.377 ms64 bytes from 172.217.5.14: icmp_seq=423 ttl=51 time=84.182 ms64 bytes from 172.217.5.14: icmp_seq=424 ttl=51 time=50.987 ms64 bytes from 172.217.5.14: icmp_seq=425 ttl=51 time=50.873 ms64 bytes from 172.217.5.14: icmp_seq=426 ttl=51 time=49.042 ms

Initially, I couldn’t connect to any web sites at all, after the upgrade. I created a new WAN interface and set it as default and things got better, but not by much. I have tried restoring the config xml file, but did not yet to a full reset, then restore of the config xml file. As you can see above, the ping response times are horrible and speed tests on their 100/10 connection is now more like 30/1.

If you have any suggestions, please share.

Thank you,
Sean

2

All my upgrades have been fine, though I usually upgrade from the previous release.

My guess is something has gone wrong from the update between such a wide range in the releases.

I’d take a backup, then I’d do a clean install to see if there are still latency issues.

Or if you have the option roll back to the last working version you had, then do incremental upgrades up to 2.5.2.

I don’t think there is anything wrong with your box (I have a similar one) or 2.5.2.

You won’t be able to download the previous ISO’s from pfsense if you don’t already have them.

3

There is a mirror set up, but it is not official, they go back several versions.