I've got my RPI4/EM7565 router up for testing. I'm seeing RSSI in the -77dB to -85dB range. Speetest.net and fast.com shows me getting 10-12 Mb downloads and 2 up, which I'm thrilled with (my DSL is 3Mb/768k).
What I'm not thrilled with is latency. Both speedtest and fast.com reports my latency at around 1s (as in 1000ms). I ping my employer's VPN port and get 1200ms! I'm using a SIM on an AT&T business account that is set up to use the i2gold APN (static routable IP). I don't need a routable IP. Would a different SIM not using i2gold provide better latency?
Is this to be expected? I noticed that the modem jumps around bands while in operation. Are different bands likely to have less latency?
Do I need to look at trying Verizon?
AT&T put their routers on the moon?
Re: AT&T put their routers on the moon?
No. Raspberry Pi4 running OpenWRT. Sierra Wireless EM7565 in a USB3 M.2 enclosure (with extra USB connection for extra power). Two Wilson Electric yagi antennas.
Re: AT&T put their routers on the moon?
Your latency is terrible. I have read about others that also seem have bad latency with their wireless plans and setups. I have used AT&T wireless LTE for many years now. From there prepaid hotspot offering and now through Crickets Simply data plan and a Netgear LTE router. Through out that time my latency has always been in the 38ms to 41ms range. Even when I tested out a WG3526 build a few months back with a Redpocket data sim (also AT&T) my latency was still below 50ms.
Don't know what to tell you but you might try buying a prepaid data only hotspot plan to test to see if you get better latency from it.
Don't know what to tell you but you might try buying a prepaid data only hotspot plan to test to see if you get better latency from it.
Re: AT&T put their routers on the moon?
I now believe my huge latency was caused by the modem overheating. I noticed that while I was testing the EM7655 went to 65 degrees.
After powering down for a while and back up, the latencies were back to normal values.
After powering down for a while and back up, the latencies were back to normal values.
