Computers & Hardware > Networking

WLAN latency any good?

<< < (4/4)

NEXUS2345:
I used to see those sorts of pings too on my old Asus DSL-N55U. May have to invest in an Asus again at some point, probably an RT-AC8*U. The TP-Link is much better than my old N55U, but the N55U still had better range and latency.

ejs:

--- Quote from: Weaver on September 12, 2016, 10:04:49 PM ---My iPad is reading 5 / 5, but only a miserable 65 Mbps on an 802.11n access point. The signal has to go through a couple of wood + plasterboard walls, but the access point is fairly close.

--- End quote ---

To be useful, signal strength readings need to be the actual values in dBm, 5 out of 5 or 100% doesn't really mean very much.

My computer is receiving -48 dBm from the router, and my router is receiving -42 dBm from my computer. Probably about -60 to -65 dBm would be the minimum for it to be a good signal to achieve the full rate.

65 Mbps is the maximum rate for a single stream 11n device, using 20 MHz of bandwidth, and without SGI.

tickmike:
Laptop to WiFi Access Point

Link Quality=47/70  Signal level=-63 dBm

$ ping -c5 192.168.0.16
PING 192.168.0.16 (192.168.0.16) 56(84) bytes of data.
64 bytes from 192.168.0.16: icmp_req=1 ttl=64 time=2.29 ms
64 bytes from 192.168.0.16: icmp_req=2 ttl=64 time=0.972 ms
64 bytes from 192.168.0.16: icmp_req=3 ttl=64 time=0.943 ms
64 bytes from 192.168.0.16: icmp_req=4 ttl=64 time=0.955 ms
64 bytes from 192.168.0.16: icmp_req=5 ttl=64 time=0.986 ms

--- 192.168.0.16 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 0.943/1.230/2.295/0.533 ms


Laptop to Hardware firewall/router

$ ping -c5 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_req=1 ttl=64 time=1.60 ms
64 bytes from 192.168.0.1: icmp_req=2 ttl=64 time=1.66 ms
64 bytes from 192.168.0.1: icmp_req=3 ttl=64 time=2.14 ms
64 bytes from 192.168.0.1: icmp_req=4 ttl=64 time=1.67 ms
64 bytes from 192.168.0.1: icmp_req=5 ttl=64 time=1.68 ms

--- 192.168.0.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.600/1.752/2.145/0.200 ms

Weaver:
My latency figures argue really horrible compared with some but not all of these other results. Wonder what's the story?

aesmith:
First pings are often higher if arp needs to be resolved.   That probably won't apply if it's the default router you're pinging.   At the moment I'm monitoring PC to router,  via first wireless to the AP, then over Powerline.  Total is around 3ms, see graph.   PC <> AP is less than one ms.

Navigation

[0] Message Index

[*] Previous page