UncleNUC Wiki

Second chance for NUCs

User Tools

Site Tools

Trace:
network_testing_pc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
network_testing_pc [2021/09/10 01:13] – [Updating the Server] usernetwork_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://levelup.gitconnected.com/building-a-high-performance-linux-based-traffic-generator-with-dpdk-93bb9904416c|DPDK and Pktgen]]. A NUC isn't going to be able to drive traffic like a fully-featured packet generator. If you are looking for a serious packet generator to test firewalls (e.g. an IMIX benchmark), use  [[https://levelup.gitconnected.com/building-a-high-performance-linux-based-traffic-generator-with-dpdk-93bb9904416c|DPDK and Pktgen]]. A NUC isn't going to be able to drive traffic like a fully-featured packet generator.
  
-====== Server Setup ======+====== Setup ====== 
 +===== Server Setup =====
 Ubuntu 20.04 LTS is a solid server. The following is a "medium" difficult tutorial to configure it. We install our tools then turn it into a router. Ubuntu 20.04 LTS is a solid server. The following is a "medium" difficult tutorial to configure it. We install our tools then turn it into a router.
  
Line 36: Line 41:
     * login using the account information you chose during installation     * login using the account information you chose during installation
     * sudo apt update && sudo apt upgrade -y     * sudo apt update && sudo apt upgrade -y
-    * sudo apt install net-tools wireless-tools iftop -y +    * sudo apt install net-tools wireless-tools iftop wpasupplicant -y
-  - Limit the timeout to connect to the network to 15 seconds instead of some 2 minutes +
-    * ''sudo /usr/lib/systemd/systemd-networkd-wait-online --timeout=15''+
   - Install iperf server as a service   - Install iperf server as a service
     * We are using iPerf (iPerf4) instead of iPerf3 (which does not support multithreading)     * We are using iPerf (iPerf4) instead of iPerf3 (which does not support multithreading)
Line 53: Line 56:
 </code> </code>
     * sudo chmod 644 /etc/systemd/system/iperf.service     * sudo chmod 644 /etc/systemd/system/iperf.service
 +    * sudo systemctl daemon-reload
     * sudo systemctl start iperf     * sudo systemctl start iperf
     * sudo systemctl status iperf     * sudo systemctl status iperf
Line 91: Line 95:
     * sudo chown -R www-data /var/www/html     * sudo chown -R www-data /var/www/html
   - Convert to static IP and DHCP server   - Convert to static IP and DHCP server
 +    * sudo vi /etc/netplan/00-installer-config.yaml
 +      * under the interface add
 +        * optional: yes
     * sudo cp /etc/netplan/00-installer-config.yaml /etc/netplan/99-config.yaml     * sudo cp /etc/netplan/00-installer-config.yaml /etc/netplan/99-config.yaml
     * sudo vi /etc/netplan/99-config.yaml     * sudo vi /etc/netplan/99-config.yaml
Line 100: Line 107:
   ethernets:   ethernets:
     <interfacename>:     <interfacename>:
-    dhcp4: no +      optional: yes 
-    addresses: +      dhcp4: no 
-      - 192.168.178.1/24 +      addresses: 
-    gateway4: 192.168.178.1 +        - 192.168.178.1/24 
-    nameservers: +      gateway4: 192.168.178.1 
-      search: [localdomain] +      nameservers: 
-      addresses: [192.168.178.1]+        search: [localdomain] 
 +        addresses: [192.168.178.1]
 </code> </code>
     * NOTE: the unusual subnet was chose so as not to collide with commonly used network addresses     * NOTE: the unusual subnet was chose so as not to collide with commonly used network addresses
 +    * NOTE: adding optional: yes will boot the server quickly even if there is no network link, but your DHCP server will not come up with the network being up. We add a crude watchdog later.
     * TIP: don't run "sudo netplan apply" yet. If you do, connectivity to your network will be lost.     * TIP: don't run "sudo netplan apply" yet. If you do, connectivity to your network will be lost.
   - Install dhcp server   - Install dhcp server
Line 145: Line 154:
       * http://192.168.178.1       * http://192.168.178.1
       * ssh 192.168.178.1       * ssh 192.168.178.1
 +  - Auto restart DHCP server
 +    * If the server boots without a link on the network interface, the DHCP server will not start. Adding a basic watchdog for the DHCP server to start or restart it.
 +    * Add script /usr/local/bin/service.sh
 +    * <code>
 +#!/bin/env bash
 +#!/bin/bash
 +service=$@
 +/bin/systemctl -q is-active "$service.service"
 +status=$?
 +if [ "$status" != 0 ]; then
 +    /bin/systemctl start "$service.service"
 +fi
 +</code>
 +    * Make the script executable
 +      * sudo chmod +x /usr/local/bin/service.sh
 +    * Add the script to your root crontab to run every 2 minutes
 +      * ''*/2 * * * * /usr/local/bin/service.sh isc-dhcp-server''
 +    * Or every minute
 +      * ''* * * * * /usr/local/bin/service.sh isc-dhcp-server''
 +    * Look up "Ubuntu watchdog service" for using a proper service watchdog
   - If you have more that one interface and want to enable routing across these interfaces   - If you have more that one interface and want to enable routing across these interfaces
     * temporary     * temporary
Line 153: Line 182:
       * sudo sysctl -p       * sudo sysctl -p
  
-====== Updating the Server ====== +===== Setting Up the Workstation =====
-Most NUCs have only 1 RJ45 interface. Since your NUC currently runs a DHCP server on that interface, plugging it into your network could take your network down. +
- +
-Here are some options to connect to your network for updates. +
-  - Shutdown the DHCP server and set the interface to get an IP via DHCP +
-    * sudo systemctl stop isc-dhcp-server +
-    * sudo mv /etc/netplan/99-config.yaml ~ +
-    * sudo netplan apply +
-    * connect the NUC to your network +
-    * when done +
-      * disconnect from your network +
-      * sudo mv ~/etc/netplan/99-config.yaml /etc/netplan/99-config.yaml +
-      * sudo netplan apply +
-      * sudo systemctl start isc-dhcp-server +
-    * TODO - need to test +
-  - If the NUC as a Wifi card, configure it and join your wifi network +
-    * TODO - need to test +
-  - Plug a USB RJ45 ethernet adapter into the NUC and configure this interface before connecting to your network. You can then save this configuration and plug/unplug this adapter as needed. +
-    * Details at [[https://schillernet.wordpress.com/2020/07/17/setting-up-a-usb-wifi-dongle-in-ubuntu-server-18-04-or-later/]] +
-    * lsusb +
-    * lshw -C network +
-    * ip link show +
-    * iwconfig +
-      * record the name of the interface +
-    * sudo vi /etc/netplan/01-netcfg.yaml +
-      * <code> +
-network: +
-  version: 2 +
-  renderer: networkd +
-  wifis: +
-    <similarto:wlx00e0262f73ec>: +
-      optional: yes +
-      dhcp4: yes +
-      dhcp6: yes +
-      access-points: +
-        "ESSID": +
-          password: "yourpassphrasehere" +
-</code> +
-    * sudo netplan apply -debug +
-    * sudo dhclient <similarto:wlx00e0262f73ec> +
-    * ip address show dev <similarto:wlx00e0262f73ec> +
-    * sudo iwlist <similarto:wlx00e0262f73ec> scan +
-    * troubleshooting +
-      * sudo ip link set <similarto:wlx00e0262f73ec> up +
-      * dmesg | grep -e wlp -e network +
-      * cat /var/log/syslog | grep -i network +
-      * networkctl +
- +
- +
-To update Ubuntu and its software packages: +
-  * sudo apt-get update && sudo apt-get upgrade -y +
- +
-====== Server Performance ====== +
-After building your server, you will want to test it from a directly connected workstation. See below on how to set up your workstation. +
- +
-You can use **top** or **htop** in conjunction with **iftop** to view CPU and the amount of bandwidth you are able to drive to the NUC and if the CPU is the limiting factor. If you don't mind a little overhead, installing and running **glances** does both in a handy dashboard. +
- +
-One reason to choose a NUC over a RaspberryPi for this use case is the drastic bandwidth limitation on the Pi's network interface being connected to the USB bus. It's too slow for this use case. +
- +
-From your testing you will find the maximum bandwidth you can drive to the server, which you can compare to your tests through a firewall or over a network link. +
- +
-====== Setting Up the Workstation ======+
 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 224: Line 192:
 {{::screenshot-librespeed.png?400|}} {{::screenshot-librespeed.png?400|}}
  
-===== iperf =====+==== iperf ====
 //See [[https://iperf.fr/]]// //See [[https://iperf.fr/]]//
  
Line 240: 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 260: Line 228:
 ./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/demo.borland.com/testsite/stadyn_largepagewithimages.html ./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/demo.borland.com/testsite/stadyn_largepagewithimages.html
 ./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/1kb.bin ./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/1kb.bin
-./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/1mp.bin+./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/1mb.bin
 </code> </code>
  
--t 2 assigned 2 threats+-t 2 assigned 2 threads
  
 -c50 assigns 50 connections -c50 assigns 50 connections
Line 269: 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://www.gnu.org/software/wget/
  
 <code> <code>
Line 276: Line 248:
 wget -r http://127.0.0.1/wrk/demo.borland.com/testsite/stadyn_largepagewithimages.html -O /tmp/blob.fil wget -r http://127.0.0.1/wrk/demo.borland.com/testsite/stadyn_largepagewithimages.html -O /tmp/blob.fil
 </code> </code>
 +====== How to Use ======
 +  - Test direct connection from test workstation to the server
 +    * HTML5 bandwidth test: [[https://192.168.178.1]]
 +    * 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://<ip address>/wrk/index.html
 +      * ./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/demo.borland.com/testsite/stadyn_largepagewithimages.html
 +      * ./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/1kb.bin
 +      * ./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/1mb.bin
 +    * wget
 +      * wget http://127.0.0.1/wrk/demo.borland.com/testsite/stadyn_largepagewithimages.html -O /dev/null
 +      * wget -r http://127.0.0.1/wrk/demo.borland.com/testsite/stadyn_largepagewithimages.html -O /tmp/blob.fil
 +    * Check workstation and server interfaces for errors
 +      * Linux
 +        * ifconfig
 +        * ethtool -S <interfacename>
 +      * 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://192.168.178.1]]
 +    * 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://<ip address>/wrk/index.html
 +      * ./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/demo.borland.com/testsite/stadyn_largepagewithimages.html
 +      * ./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/1kb.bin
 +      * ./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/1mb.bin
 +    * wget
 +      * wget http://127.0.0.1/wrk/demo.borland.com/testsite/stadyn_largepagewithimages.html -O /dev/null
 +      * wget -r http://127.0.0.1/wrk/demo.borland.com/testsite/stadyn_largepagewithimages.html -O /tmp/blob.fil
 +    * Check switch(es) for interface errors
 +  - Test a firewall
 +    * HTML5 bandwidth test: [[https://192.168.178.1]]
 +    * 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://<ip address>/wrk/index.html
 +      * ./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/demo.borland.com/testsite/stadyn_largepagewithimages.html
 +      * ./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/1kb.bin
 +      * ./wrk -t2 -c50 -d30s http://<ipaddress>/wrk/1mb.bin
 +    * wget
 +      * wget http://127.0.0.1/wrk/demo.borland.com/testsite/stadyn_largepagewithimages.html -O /dev/null
 +      * wget -r http://127.0.0.1/wrk/demo.borland.com/testsite/stadyn_largepagewithimages.html -O /tmp/blob.fil
 +====== Maintenance ======
 +===== Updating the Server =====
 +Most NUCs have only 1 RJ45 interface. Since your NUC currently runs a DHCP server on that interface, plugging it into your network could take your network down.
 +
 +Here are some options to connect to your network for updates.
 +  - Shutdown the DHCP server and set the interface to get an IP via DHCP
 +    * sudo systemctl stop isc-dhcp-server
 +    * sudo mv /etc/netplan/99-config.yaml ~
 +    * sudo netplan apply
 +    * connect the NUC to your network
 +    * when done
 +      * disconnect from your network
 +      * sudo mv ~/etc/netplan/99-config.yaml /etc/netplan/99-config.yaml
 +      * sudo netplan apply
 +      * sudo systemctl start isc-dhcp-server
 +  - Plug a USB RJ45 ethernet adapter into the NUC and configure this interface before connecting to your network.
 +    * ip a
 +    * sudo ip link set <interfacename> up
 +    * sudo dhclient <interfacename>
 +    * This interface is unmanaged (sudo networkctl) unless you configure it in netplan
 +  - If the NUC as a Wifi card, configure it and join your wifi network
 +    * TODO - need to test
 +  - Plug in a USB wireless adapter and use that
 +    * Details at [[https://schillernet.wordpress.com/2020/07/17/setting-up-a-usb-wifi-dongle-in-ubuntu-server-18-04-or-later/]]
 +    * **WARNING** this is problematic
 +    * lsusb
 +    * lshw -C network
 +    * ip link show
 +    * iwconfig
 +      * record the name of the interface
 +    * sudo vi /etc/netplan/01-netcfg.yaml
 +      * <code>
 +network:
 +  version: 2
 +  renderer: networkd
 +  wifis:
 +    <similarto:wlx00e0262f73ec>:
 +      optional: yes
 +      dhcp4: yes
 +      dhcp6: yes
 +      access-points:
 +        "ESSID":
 +          password: "yourpassphrasehere"
 +</code>
 +    * ''sudo netplan --debug apply''
 +    * sudo dhclient <similarto:wlx00e0262f73ec>
 +    * ip address show dev <similarto:wlx00e0262f73ec>
 +    * sudo iwlist <similarto:wlx00e0262f73ec> scan
 +    * troubleshooting
 +      * sudo ip link set <similarto:wlx00e0262f73ec> up
 +      * dmesg | grep -e wlp -e network
 +      * cat /var/log/syslog | grep -i network
 +      * networkctl
 +
 +To update Ubuntu and its software packages:
 +  * sudo apt-get update && sudo apt-get upgrade -y
 +
 +===== Server Performance =====
 +After building your server, you will want to test it from a directly connected workstation. See below on how to set up your workstation.
 +
 +You can use **top** or **htop** in conjunction with **iftop** to view CPU and the amount of bandwidth you are able to drive to the NUC and if the CPU is the limiting factor. If you don't mind a little overhead, installing and running **glances** does both in a handy dashboard.
 +
 +One reason to choose a NUC over a RaspberryPi for this use case is the drastic bandwidth limitation on the Pi's network interface being connected to the USB bus. It's too slow for this use case.
 +
 +From your testing you will find the maximum bandwidth you can drive to the server, which you can compare to your tests through a firewall or over a network link.
 +
network_testing_pc.1631236422.txt.gz · Last modified: 2021/09/10 01:13 by user