network_testing_pc
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| network_testing_pc [2021/09/12 19:14] – formatting user | network_testing_pc [2021/09/13 16:21] (current) – updated user | ||
|---|---|---|---|
| Line 16: | Line 16: | ||
| * iPerf server | * iPerf server | ||
| * Web server with sample pages for testing using wrk, wget, etc. | * Web server with sample pages for testing using wrk, wget, etc. | ||
| + | |||
| + | Ideas: | ||
| + | * JTest to the server | ||
| + | * Testing NUCs with 2.5Gb capable interfaces | ||
| If you are looking for a serious packet generator to test firewalls (e.g. an IMIX benchmark), use [[https:// | If you are looking for a serious packet generator to test firewalls (e.g. an IMIX benchmark), use [[https:// | ||
| Line 52: | Line 56: | ||
| </ | </ | ||
| * sudo chmod 644 / | * sudo chmod 644 / | ||
| + | * sudo systemctl daemon-reload | ||
| * sudo systemctl start iperf | * sudo systemctl start iperf | ||
| * sudo systemctl status iperf | * sudo systemctl status iperf | ||
| Line 180: | Line 185: | ||
| I like to set up a laptop with a wired ethernet connection for this testing. A Windows workstation with WSL2 and Ubuntu is my preferred method. However, you don't need a virtual server to run the HTML5 speed test and iperf. | I like to set up a laptop with a wired ethernet connection for this testing. A Windows workstation with WSL2 and Ubuntu is my preferred method. However, you don't need a virtual server to run the HTML5 speed test and iperf. | ||
| - | ===== HTML5 SpeedTest | + | ==== HTML5 SpeedTest ==== |
| Point your browser the to IP address of the server. Click Start. | Point your browser the to IP address of the server. Click Start. | ||
| Line 187: | Line 192: | ||
| {{:: | {{:: | ||
| - | ===== iperf ===== | + | ==== iperf ==== |
| //See [[https:// | //See [[https:// | ||
| Line 203: | Line 208: | ||
| -e selects enhanced reporting | -e selects enhanced reporting | ||
| - | ===== wrk ===== | + | ==== wrk ==== |
| Instructions are for a Linux environment such as WSL2 on Windows. | Instructions are for a Linux environment such as WSL2 on Windows. | ||
| Line 223: | Line 228: | ||
| ./wrk -t2 -c50 -d30s http://< | ./wrk -t2 -c50 -d30s http://< | ||
| ./wrk -t2 -c50 -d30s http://< | ./wrk -t2 -c50 -d30s http://< | ||
| - | ./wrk -t2 -c50 -d30s http://< | + | ./wrk -t2 -c50 -d30s http://< |
| </ | </ | ||
| - | -t 2 assigned 2 threats | + | -t 2 assigned 2 threads |
| -c50 assigns 50 connections | -c50 assigns 50 connections | ||
| Line 232: | Line 237: | ||
| -d assigns 30 second duration | -d assigns 30 second duration | ||
| - | ===== wget ===== | + | ==== wget ==== |
| Pull one or more files from the web server. Note that the recursion flag (-r) cannot be used with a special file like /dev/null. | Pull one or more files from the web server. Note that the recursion flag (-r) cannot be used with a special file like /dev/null. | ||
| + | |||
| + | Installation: | ||
| + | * Linux - apt install wget | ||
| + | * Windows - https:// | ||
| < | < | ||
| Line 239: | Line 248: | ||
| wget -r http:// | wget -r http:// | ||
| </ | </ | ||
| + | ====== How to Use ====== | ||
| + | - Test direct connection from test workstation to the server | ||
| + | * HTML5 bandwidth test: [[https:// | ||
| + | * iperf test | ||
| + | * iperf -c 192.168.178.1 -e | ||
| + | * iperf -c 192.168.178.1 -u -e | ||
| + | * iperf -c 192.168.178.1 -P 10 -e | ||
| + | * wrk | ||
| + | * ./wrk -t2 -c50 -d30s http://< | ||
| + | * ./wrk -t2 -c50 -d30s http://< | ||
| + | * ./wrk -t2 -c50 -d30s http://< | ||
| + | * ./wrk -t2 -c50 -d30s http://< | ||
| + | * wget | ||
| + | * wget http:// | ||
| + | * wget -r http:// | ||
| + | * Check workstation and server interfaces for errors | ||
| + | * Linux | ||
| + | * ifconfig | ||
| + | * ethtool -S < | ||
| + | * Windows | ||
| + | * windows powershell: netsh interface ipv6 show ipstats | Select-String errors | ||
| + | * Note that rx overruns can occur with load testing even on a perfect link | ||
| + | - Test a link (fiber link, wireless link, wired trunk) | ||
| + | * HTML5 bandwidth test: [[https:// | ||
| + | * iperf test | ||
| + | * iperf -c 192.168.178.1 -e | ||
| + | * iperf -c 192.168.178.1 -u -e | ||
| + | * iperf -c 192.168.178.1 -P 10 -e | ||
| + | * wrk | ||
| + | * ./wrk -t2 -c50 -d30s http://< | ||
| + | * ./wrk -t2 -c50 -d30s http://< | ||
| + | * ./wrk -t2 -c50 -d30s http://< | ||
| + | * ./wrk -t2 -c50 -d30s http://< | ||
| + | * wget | ||
| + | * wget http:// | ||
| + | * wget -r http:// | ||
| + | * Check switch(es) for interface errors | ||
| + | - Test a firewall | ||
| + | * HTML5 bandwidth test: [[https:// | ||
| + | * iperf test | ||
| + | * iperf -c 192.168.178.1 -e | ||
| + | * iperf -c 192.168.178.1 -u -e | ||
| + | * iperf -c 192.168.178.1 -P 10 -e | ||
| + | * wrk | ||
| + | * ./wrk -t2 -c50 -d30s http://< | ||
| + | * ./wrk -t2 -c50 -d30s http://< | ||
| + | * ./wrk -t2 -c50 -d30s http://< | ||
| + | * ./wrk -t2 -c50 -d30s http://< | ||
| + | * wget | ||
| + | * wget http:// | ||
| + | * wget -r http:// | ||
| ====== Maintenance ====== | ====== Maintenance ====== | ||
| ===== Updating the Server ===== | ===== Updating the Server ===== | ||
network_testing_pc.1631474081.txt.gz · Last modified: 2021/09/12 19:14 by user