How to test WiFi speed in AP mode?

[njsss]

I set up my Pi to AP mode, and I want to know its wifi speed. Is there an easy way or a script to find out the speed?

thanks

[Andyroo]

Best way is to use two machines on the WiFi network and run something like iperf or netstress

This will give you a best possible figure that will go down when you add an application into the mix

Interested to see the result - here the broadband is the limiting device

[Ernst]

I set up my Pi to AP mode, and I want to know its wifi speed. Is there an easy way or a script to find out the speed?

thanks

You asked for speed, this is the answer as seen from a client:

Code: Select all

pi@raspi4:~ $ iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11  ESSID:"XXXXXXX"
          Mode:Managed  Frequency:2.462 GHz  Access Point: 74:DA:38:FF:FF:FF
          Bit Rate=65 Mb/s   Tx-Power=31 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=44/70  Signal level=-66 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:9044  Invalid misc:0   Missed beacon:0

If you want to ask about performance see the post before this post.

[jahboater]

Another performance test is "iperf" which is very simple to use:
sudo apt install iperf
This is a down clocked Pi Zero W

Code: Select all

$ iperf -c piclk
------------------------------------------------------------
Client connecting to piclk, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[  3] local 192.168.0.5 port 52260 connected with 192.168.0.88 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.7 sec  21.2 MBytes  16.6 Mbits/sec

A very quick test is to send large packets with ping:

The Pi Zero W connected over Wifi

Code: Select all

$ ping -s 65500 -c 4 piclk
PING piclk (192.168.0.88) 65500(65528) bytes of data.
65508 bytes from piclk (192.168.0.88): icmp_seq=1 ttl=64 time=124 ms
65508 bytes from piclk (192.168.0.88): icmp_seq=2 ttl=64 time=66.7 ms
65508 bytes from piclk (192.168.0.88): icmp_seq=3 ttl=64 time=59.8 ms
65508 bytes from piclk (192.168.0.88): icmp_seq=4 ttl=64 time=48.9 ms

--- piclk ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 48.972/74.982/124.335/29.193 ms

ethernet connected Pi Zero

Code: Select all

$ ping -s 65500 -c 4 pi0   
PING pi0 (192.168.0.112) 65500(65528) bytes of data.
65508 bytes from pi0 (192.168.0.112): icmp_seq=1 ttl=64 time=13.2 ms
65508 bytes from pi0 (192.168.0.112): icmp_seq=2 ttl=64 time=13.2 ms
65508 bytes from pi0 (192.168.0.112): icmp_seq=3 ttl=64 time=13.2 ms
65508 bytes from pi0 (192.168.0.112): icmp_seq=4 ttl=64 time=13.2 ms

--- pi0 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 13.212/13.232/13.259/0.083 ms

ethernet connected Pi3B+

Code: Select all

$ ping -s 65500 -c 4 pi    
PING pi (192.168.0.80) 65500(65528) bytes of data.
65508 bytes from pi (192.168.0.80): icmp_seq=1 ttl=64 time=6.07 ms
65508 bytes from pi (192.168.0.80): icmp_seq=2 ttl=64 time=6.04 ms
65508 bytes from pi (192.168.0.80): icmp_seq=3 ttl=64 time=5.58 ms
65508 bytes from pi (192.168.0.80): icmp_seq=4 ttl=64 time=5.58 ms

--- pi ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 5.584/5.820/6.072/0.253 ms