Ping spike every 10 seconds?

I am using 5ghz and a not congested channel, but every 10 seconds I get a ping spike to my router. I am guessing that the device having a scan every 10 seconds. I also notice that when the signal goes from -72 to -70 (vice versa), I got a very bad ping.

The ping goes from consistent 1-2ms for about 8 seconds then 40-480ms for the rest 9-10seconds.

Is there any way to disable that constant scanning?

My device is Ubiquiti LiteBeam AC Gen2

Ubiquiti LiteBeam AC Gen2 -->> connected to -->>> ISP 5ghz router(192.168.254.254)

If I connect directly my pc and ping 192.168.254.254 I got no issue. But if I log in to root to my Ubiquiti LiteBeam AC Gen2 and ping the gateway(192.168.254.254) then constant ping spike.

Please don't ask me to use wired.
Thank you!

64 bytes from 192.168.254.254: seq=1871 ttl=64 time=97.145 ms
64 bytes from 192.168.254.254: seq=1872 ttl=64 time=1.896 ms
64 bytes from 192.168.254.254: seq=1873 ttl=64 time=2.653 ms
64 bytes from 192.168.254.254: seq=1874 ttl=64 time=3.259 ms
64 bytes from 192.168.254.254: seq=1875 ttl=64 time=6.773 ms
64 bytes from 192.168.254.254: seq=1876 ttl=64 time=2.250 ms
64 bytes from 192.168.254.254: seq=1877 ttl=64 time=1.889 ms
64 bytes from 192.168.254.254: seq=1878 ttl=64 time=2.222 ms
64 bytes from 192.168.254.254: seq=1879 ttl=64 time=2.384 ms
64 bytes from 192.168.254.254: seq=1880 ttl=64 time=2.531 ms
64 bytes from 192.168.254.254: seq=1881 ttl=64 time=94.282 ms
64 bytes from 192.168.254.254: seq=1882 ttl=64 time=2.113 ms
64 bytes from 192.168.254.254: seq=1883 ttl=64 time=2.876 ms
64 bytes from 192.168.254.254: seq=1884 ttl=64 time=2.287 ms
64 bytes from 192.168.254.254: seq=1885 ttl=64 time=2.465 ms
64 bytes from 192.168.254.254: seq=1886 ttl=64 time=2.223 ms
64 bytes from 192.168.254.254: seq=1887 ttl=64 time=3.595 ms
64 bytes from 192.168.254.254: seq=1888 ttl=64 time=2.756 ms
64 bytes from 192.168.254.254: seq=1889 ttl=64 time=2.558 ms
64 bytes from 192.168.254.254: seq=1890 ttl=64 time=2.233 ms
64 bytes from 192.168.254.254: seq=1891 ttl=64 time=89.640 ms
64 bytes from 192.168.254.254: seq=1892 ttl=64 time=2.348 ms
64 bytes from 192.168.254.254: seq=1893 ttl=64 time=2.346 ms
64 bytes from 192.168.254.254: seq=1894 ttl=64 time=2.013 ms
64 bytes from 192.168.254.254: seq=1895 ttl=64 time=2.186 ms
64 bytes from 192.168.254.254: seq=1896 ttl=64 time=2.109 ms
64 bytes from 192.168.254.254: seq=1897 ttl=64 time=1.901 ms
64 bytes from 192.168.254.254: seq=1898 ttl=64 time=2.073 ms
64 bytes from 192.168.254.254: seq=1899 ttl=64 time=2.168 ms
64 bytes from 192.168.254.254: seq=1900 ttl=64 time=2.162 ms
64 bytes from 192.168.254.254: seq=1901 ttl=64 time=336.590 ms
64 bytes from 192.168.254.254: seq=1902 ttl=64 time=4.491 ms
64 bytes from 192.168.254.254: seq=1903 ttl=64 time=2.032 ms
64 bytes from 192.168.254.254: seq=1904 ttl=64 time=2.181 ms
64 bytes from 192.168.254.254: seq=1905 ttl=64 time=2.022 ms
64 bytes from 192.168.254.254: seq=1906 ttl=64 time=2.949 ms
64 bytes from 192.168.254.254: seq=1907 ttl=64 time=2.189 ms
64 bytes from 192.168.254.254: seq=1908 ttl=64 time=2.046 ms
64 bytes from 192.168.254.254: seq=1908 ttl=64 time=2.046 ms
64 bytes from 192.168.254.254: seq=1909 ttl=64 time=2.011 ms
64 bytes from 192.168.254.254: seq=1910 ttl=64 time=2.162 ms
64 bytes from 192.168.254.254: seq=1911 ttl=64 time=69.196 ms
64 bytes from 192.168.254.254: seq=1912 ttl=64 time=2.191 ms
64 bytes from 192.168.254.254: seq=1913 ttl=64 time=3.732 ms
64 bytes from 192.168.254.254: seq=1914 ttl=64 time=2.279 ms
64 bytes from 192.168.254.254: seq=1915 ttl=64 time=2.136 ms
64 bytes from 192.168.254.254: seq=1916 ttl=64 time=3.227 ms
64 bytes from 192.168.254.254: seq=1917 ttl=64 time=1.961 ms
64 bytes from 192.168.254.254: seq=1918 ttl=64 time=2.071 ms
64 bytes from 192.168.254.254: seq=1919 ttl=64 time=2.393 ms
64 bytes from 192.168.254.254: seq=1920 ttl=64 time=2.188 ms
64 bytes from 192.168.254.254: seq=1921 ttl=64 time=183.908 ms
64 bytes from 192.168.254.254: seq=1922 ttl=64 time=2.178 ms
64 bytes from 192.168.254.254: seq=1923 ttl=64 time=2.062 ms
64 bytes from 192.168.254.254: seq=1924 ttl=64 time=7.441 ms
64 bytes from 192.168.254.254: seq=1925 ttl=64 time=2.461 ms
64 bytes from 192.168.254.254: seq=1926 ttl=64 time=1.941 ms
64 bytes from 192.168.254.254: seq=1927 ttl=64 time=2.059 ms

Moved to the Installing and Using OpenWrt forum.

1 Like

Rather than posting screenshots of data, post the results in preformatted text, by using the icon highlighted in red...

OpenWRT Posting Icons

Thanks.

1 Like

The ubiquity AP and the ISP router are connected via ethernet or via WiFi?

it is connected via wifi

Too bad, now both sides of that WiFi link can be responsible for your problem....

Or rather any of the three nodes in your setup:

PC <-> WiFi <-> Ubiquity <-> router

might introduce this cyclic 10 second behaviour... making debugging certainly fun.

1 Like

My PC is connected via lan to Ubiquity and then Ubiquity to router. I performed the ping via ssh to openwrt.

Are you running AP and client both on the same radio-- the Litebeam's 5 GHz radio?

Ah okay, so only one wireless link, OpenWrt on the Ubiquity and a proprietary OS on the main router?

No. Only client mode

Yes indeed

Mmh, you could try to connect to the proprietary router with a WiFi client and see whether the ping spikes go away (which would indicate whether fiddling with OpenWrt on the Ubiquity is worthwhile at all).