Since upgrading from 20.1.7 to 20.1.8 I've seen increased latency on the WAN. I use thinkbroadband to monitor the WAN link, plus I have a ping which runs regularly from a monitoring platform on my network. After I performed the upgrade at 14:30 yesterday, my latency and jitter has gone up significantly.
Attached are two graphs. Were there any code changes or package updates that might have caused this? At this stage, I can't rule out my ISP but the timing is exactly when I performed the upgrade.
(the large red spikes in the first graph are outages when I restarted opnsense)
Was there a reboot involved? Some type of filter reload? If not chances are very low the update itself caused this.
Cheers,
Franco
These are my results from a symmetric 100 mbit fibre connection after the 20.1.18 upgrade, with an EdgeRouter X as reference.
EdgeRouter X 1.10.11 - DL 107,92 UL 108,57 response time 3,32 ms
APU2C4 OPNsense 20.1.18_1 DL 32,16 UL 8,33 response time 12,73 ms
miroco
Quote from: miroco on July 04, 2020, 06:38:06 PM
These are my results from a symmetric 100 mbit fibre connection after the 20.1.18 upgrade, with an EdgeRouter X as reference.
EdgeRouter X 1.10.11 - DL 107,92 UL 108,57 response time 3,32 ms
APU2C4 OPNsense 20.1.18_1 DL 32,16 UL 8,33 response time 12,73 ms
miroco
What was the Version before?
The prior version was 20.1.7. I just noticed that I got a little too enthusiastic with the numbering scheme 20.1.18 -> 20.1.8 ;)
And it was faster with 20.1.7? Same uplink and increase of 11ms latency sounds like a different problem
I noticed and still notice that pages take longer to load after the 20.1.8 update. I therefore ran the speed test and searched the forum. I did not run a speed test with 20.1.7 because I didn't experience that there was something wrong with my setup; "health is silent" I presume. Can I revert to 20.1.7, if so how do I do it?
I have a symmetric 900 mbps service from Gigaclear and using either their own speedtest or speedtest.org my ping times are typically 5-7ms using default destinations (for the latter IOMART Maidenhead). I can get different ping times on speedtest.org by choosing different destinations (i.e. XILO Maidenhead is 7ms, University of Oxford, IT services 8ms, Vodafone Bracknell 8ms, KCOM Kingston Upon Hull 15ms, BT Lancashire 25ms). Generally the further away the longer the ping times. If I use ThinkBroadband the ping time is around 21-23ms. In my case the ping times haven't changed noticeably between the different versions of OPNsense (Currently on 20.1.8_1) as its never been better than 5-7ms.
Your observation makes total sense. The further away the greater the latency. However, the only variables in my use case are the EdgeRouter X vs. the APU2C4. I ran the test several times and with four different browsers.
In the past, usually after an update, I have had this happen to me twice. Usually a quick restore of the latest config and reboot cures the problem. Another time I had to perform a clean install and then restore the backup config. Usually after taking these steps, everything is good.
Thank you. I tried a reset and a subsequent restore of the latest config, but to no avail.
I have this since 20.1.7.
Change of BSD version??
Another Speedtest service gave a very different result. In hindsight, I should have done this from the very beginning. Gotten a second opinion that is. ::)
Some pages still take longer to load, something I guess can be attributet to a different user pattern caused by the ongoing covid-19 pandemic.
miroco