For very close servers and the time in cs, expect strange things like 0ms RTT. It uses either /proc/timer_list or /proc/uptime to measue time, although uptime resolution is in cs (1/100s). With slow CPUs, the socat seems to be the best option. If the script detects the CPU is at 100%, it will For slow CPU devices, like many OpenWrt routers, that limit would be even lower. I could not test anything over 170 Mbps but I cannot garantee this is the connection, target server or script limit. First, it pings the server (through the TCP connection) and then download 50M and upload 20M.Īs a shell script, this client has its limitations. The standard est is executed through a TCP connection. If no server is specified, it gets a list of servers from, choose the closest one (based on the server answers) and run a test. It also requires some basic unix tools like sed, awk, dd, tr, grep, cut, nslookup, ip
It requires a web client (curl or wget), a tcp client (socat, netcat or nc) and a POSIX shell (tested with ash and bash). If not server was provided, it will look for the best one at: u Define the upload payload size in bytes Default is 20971520 Default is to look for the fastest server. s Define the server address (name or ip address) with port. I Bind to interface (only works with socat)
i Define number of times a PING command is issued.
d Define the download payload size in bytes. By default, it tries, socat, netcat and nc 6 Connect only to IPv6 servers Default is IPv6 or IPv4.
0 kommentar(er)
