Hi, I have a setup on MediaTek MT7628AN, UniElec U7628-01 (16M flash), OpenWrt 22.03.2, r19803-9a599fee93 on a roof and 3g pci-e modem. And i noticed that ping over 2.4Ghz wifi is so bad...
64 bytes from 192.168.0.1: icmp_seq=2839 ttl=65 time=39.945 ms
64 bytes from 192.168.0.1: icmp_seq=2840 ttl=65 time=114.151 ms
64 bytes from 192.168.0.1: icmp_seq=2841 ttl=65 time=3.558 ms
64 bytes from 192.168.0.1: icmp_seq=2842 ttl=65 time=5.187 ms
64 bytes from 192.168.0.1: icmp_seq=2843 ttl=65 time=3.194 ms
64 bytes from 192.168.0.1: icmp_seq=2844 ttl=65 time=3.530 ms
64 bytes from 192.168.0.1: icmp_seq=2845 ttl=65 time=3.107 ms
64 bytes from 192.168.0.1: icmp_seq=2846 ttl=65 time=3.914 ms
64 bytes from 192.168.0.1: icmp_seq=2847 ttl=65 time=5.058 ms
64 bytes from 192.168.0.1: icmp_seq=2848 ttl=65 time=11.356 ms
64 bytes from 192.168.0.1: icmp_seq=2849 ttl=65 time=3.418 ms
64 bytes from 192.168.0.1: icmp_seq=2850 ttl=65 time=3.220 ms
64 bytes from 192.168.0.1: icmp_seq=2851 ttl=65 time=2.285 ms
64 bytes from 192.168.0.1: icmp_seq=2852 ttl=65 time=3.428 ms
64 bytes from 192.168.0.1: icmp_seq=2853 ttl=65 time=2.373 ms
64 bytes from 192.168.0.1: icmp_seq=2854 ttl=65 time=95.826 ms
64 bytes from 192.168.0.1: icmp_seq=2855 ttl=65 time=6.022 ms
64 bytes from 192.168.0.1: icmp_seq=2856 ttl=65 time=3.420 ms
64 bytes from 192.168.0.1: icmp_seq=2857 ttl=65 time=4.453 ms
64 bytes from 192.168.0.1: icmp_seq=2858 ttl=65 time=2.617 ms
64 bytes from 192.168.0.1: icmp_seq=2859 ttl=65 time=4.589 ms
64 bytes from 192.168.0.1: icmp_seq=2860 ttl=65 time=4.025 ms
64 bytes from 192.168.0.1: icmp_seq=2861 ttl=65 time=76.170 ms
64 bytes from 192.168.0.1: icmp_seq=2862 ttl=65 time=34.783 ms
64 bytes from 192.168.0.1: icmp_seq=2863 ttl=65 time=115.453 ms
64 bytes from 192.168.0.1: icmp_seq=2864 ttl=65 time=8.005 ms
64 bytes from 192.168.0.1: icmp_seq=2865 ttl=65 time=487.762 ms
64 bytes from 192.168.0.1: icmp_seq=2866 ttl=65 time=4.293 ms
64 bytes from 192.168.0.1: icmp_seq=2867 ttl=65 time=3.093 ms
64 bytes from 192.168.0.1: icmp_seq=2868 ttl=65 time=4.245 ms
64 bytes from 192.168.0.1: icmp_seq=2869 ttl=65 time=2.453 ms
64 bytes from 192.168.0.1: icmp_seq=2870 ttl=65 time=4.003 ms
64 bytes from 192.168.0.1: icmp_seq=2871 ttl=65 time=5.026 ms
64 bytes from 192.168.0.1: icmp_seq=2872 ttl=65 time=85.787 ms
64 bytes from 192.168.0.1: icmp_seq=2873 ttl=65 time=147.754 ms
64 bytes from 192.168.0.1: icmp_seq=2874 ttl=65 time=357.326 ms
64 bytes from 192.168.0.1: icmp_seq=2875 ttl=65 time=107.770 ms
64 bytes from 192.168.0.1: icmp_seq=2876 ttl=65 time=3.243 ms
64 bytes from 192.168.0.1: icmp_seq=2877 ttl=65 time=959.384 ms
64 bytes from 192.168.0.1: icmp_seq=2878 ttl=65 time=21.899 ms
64 bytes from 192.168.0.1: icmp_seq=2879 ttl=65 time=8.252 ms
Is this a hardware issue? Does anyone can confirm that MediaTek MT7628AN is not good as a WiFi router? Or issue could be in missconfiguration?
Upgrade to latest and best OpenWRT 23.05.5 - make a configuration backup, sysupgrade, if sysupgrade shows red warning you will have to unzip backup and type settings back. Note that you have to upgrade without copying software lists as SSL framework changed.
then survey your surroundings using eg https://github.com/VREMSoftwareDevelopment/WiFiAnalyzer - normally 2.4GHz is overused, and you get latency spikes every time your neighbour clicks a button on a webpage.
Likely automatic channel selection is the best choice.
Then post output of following (formatting using </> code button):
ubus call system board
cat /etc/config/network
cat /etc/config/firewall
cat /etc/config/wireless
PING 192.168.43.1 (192.168.43.1): 56 data bytes
64 bytes from 192.168.43.1: icmp_seq=0 ttl=65 time=4.053 ms
64 bytes from 192.168.43.1: icmp_seq=1 ttl=65 time=3.954 ms
64 bytes from 192.168.43.1: icmp_seq=2 ttl=65 time=3.711 ms
64 bytes from 192.168.43.1: icmp_seq=3 ttl=65 time=41.148 ms
64 bytes from 192.168.43.1: icmp_seq=4 ttl=65 time=3.983 ms
64 bytes from 192.168.43.1: icmp_seq=5 ttl=65 time=3.500 ms
64 bytes from 192.168.43.1: icmp_seq=6 ttl=65 time=4.876 ms
64 bytes from 192.168.43.1: icmp_seq=7 ttl=65 time=3.902 ms
64 bytes from 192.168.43.1: icmp_seq=8 ttl=65 time=4.426 ms
64 bytes from 192.168.43.1: icmp_seq=9 ttl=65 time=4.101 ms
64 bytes from 192.168.43.1: icmp_seq=10 ttl=65 time=4.195 ms
64 bytes from 192.168.43.1: icmp_seq=11 ttl=65 time=4.680 ms
64 bytes from 192.168.43.1: icmp_seq=12 ttl=65 time=3.976 ms
64 bytes from 192.168.43.1: icmp_seq=13 ttl=65 time=24.127 ms
64 bytes from 192.168.43.1: icmp_seq=14 ttl=65 time=3.478 ms
64 bytes from 192.168.43.1: icmp_seq=15 ttl=65 time=3.696 ms
64 bytes from 192.168.43.1: icmp_seq=16 ttl=65 time=141.897 ms
64 bytes from 192.168.43.1: icmp_seq=17 ttl=65 time=4.539 ms
64 bytes from 192.168.43.1: icmp_seq=18 ttl=65 time=4.878 ms
64 bytes from 192.168.43.1: icmp_seq=19 ttl=65 time=4.393 ms
Even on 5G network, no more 5G Wireless STA around.
I updated the firmware to the latest on MT7628AN router
Latency still spikes from time to time.
When it is on roof, I have even see spikes up to 100ms.
Going to try the same but with Google Wifi hardware.
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=3.707 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=3.518 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=3.664 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=3.405 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=3.719 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=3.464 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=3.578 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=3.554 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=3.665 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=3.841 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=11.693 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=3.654 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=11.838 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=3.503 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=3.623 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=3.403 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=3.521 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=3.687 ms
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=11.259 ms
64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=3.492 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=3.459 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=3.631 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=26.992 ms
64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=3.676 ms
64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=3.660 ms
64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=19.064 ms
64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=3.665 ms
64 bytes from 192.168.0.1: icmp_seq=41 ttl=64 time=3.439 ms
64 bytes from 192.168.0.1: icmp_seq=42 ttl=64 time=3.717 ms
64 bytes from 192.168.0.1: icmp_seq=43 ttl=64 time=3.688 ms
64 bytes from 192.168.0.1: icmp_seq=44 ttl=64 time=5.637 ms
64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=3.547 ms
64 bytes from 192.168.0.1: icmp_seq=46 ttl=64 time=4.251 ms
64 bytes from 192.168.0.1: icmp_seq=47 ttl=64 time=11.762 ms
64 bytes from 192.168.0.1: icmp_seq=48 ttl=64 time=11.777 ms
64 bytes from 192.168.0.1: icmp_seq=49 ttl=64 time=3.976 ms
64 bytes from 192.168.0.1: icmp_seq=50 ttl=64 time=3.797 ms
64 bytes from 192.168.0.1: icmp_seq=51 ttl=64 time=3.619 ms
64 bytes from 192.168.0.1: icmp_seq=52 ttl=64 time=4.059 ms
64 bytes from 192.168.0.1: icmp_seq=53 ttl=64 time=11.656 ms
64 bytes from 192.168.0.1: icmp_seq=54 ttl=64 time=11.444 ms
64 bytes from 192.168.0.1: icmp_seq=55 ttl=64 time=3.519 ms
64 bytes from 192.168.0.1: icmp_seq=56 ttl=64 time=3.510 ms
64 bytes from 192.168.0.1: icmp_seq=57 ttl=64 time=3.690 ms