2 ms·
Oh okay, then FTTB is more appropriate. Anyway the 30ms it’s only on this service/server, my setup adds about 1-1,5ms: https://www.speedtest.net/result/i/52368
by giuliomagnifico 4y ago
Oh okay, then FTTB is more appropriate. Anyway the 30ms it’s only on this service/server, my setup adds about 1-1,5ms: https://www.speedtest.net/result/i/5236800213 https://www.speedtest.net/result/i/5236800213
Ping time from router to AP
root@R4S:~# ping 192.168.1.3
PING 192.168.1.3 (192.168.1.3): 56 data bytes
64 bytes from 192.168.1.3: seq=0 ttl=64 time=1.150 ms64 bytes from 192.168.1.3: seq=1 ttl=64 time=1.252 ms64 bytes from 192.168.1.3: seq=2 ttl=64 time=1.117 ms64 bytes from 192.168.1.3: seq=3 ttl=64 time=1.170 ms64 bytes from 192.168.1.3: seq=4 ttl=64 time=1.210 ms64 bytes from 192.168.1.3: seq=5 ttl=64 time=1.204 ms64 bytes from 192.168.1.3: seq=6 ttl=64 time=1.232 ms64 bytes from 192.168.1.3: seq=7 ttl=64 time=1.190 ms64 bytes from 192.168.1.3: seq=8 ttl=64 time=1.207 ms^C
--- 192.168.1.3 ping statistics ---
9 packets transmitted, 9 packets received, 0% packet loss
round-trip min/avg/max = 1.117/1.192/1.252 ms
- runjake 4y agoReadable: PING 192.168.1.3 (192.168.1.3): 56 data bytes 64 bytes from 192.168.1.3: seq=0 ttl=64 time=1.150 ms 64 bytes from 192.168.1.3: seq=1 ttl=64 time=1.252 ms 64 bytes from 192.168.1.3: seq=2 ttl=64 time=1.117 ms 64 bytes from 192.168.1.3: seq=3 ttl=64 time=1.170 ms 64 bytes from 192.168.1.3: seq=4 ttl=64 time=1.210 ms 64 bytes from 192.168.1.3: seq=5 ttl=64 time=1.204 ms 64 bytes from 192.168.1.3: seq=6 ttl=64 time=1.232 ms 64 bytes from 192.168.1.3: seq=7 ttl=64 time=1.190 ms 64 bytes from 192.168.1.3: seq=8 ttl=64 time=1.207 ms ^C --- 192.168.1.3 ping statistics --- 9 packets transmitted, 9 packets received, 0% packet loss round-trip min/avg/max = 1.117/1.192/1.252 ms
- giuliomagnifico 4y agoThanks, I inserted two spaces before the text but it didn’t format all the code, just the first line, maybe because I’m on mobile?