Zageron Posted November 23, 2020 Posted November 23, 2020 ❯ sudo iperf3 -s ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 192.167.0.1, port 23497 [ 5] local 192.167.0.2 port 5201 connected to 192.167.0.1 port 23498 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 163 MBytes 1.37 Gbits/sec [ 5] 1.00-2.00 sec 149 MBytes 1.25 Gbits/sec [ 5] 2.00-3.00 sec 104 MBytes 868 Mbits/sec [ 5] 3.00-4.00 sec 141 MBytes 1.19 Gbits/sec [ 5] 4.00-5.00 sec 174 MBytes 1.46 Gbits/sec [ 5] 5.00-6.00 sec 125 MBytes 1.05 Gbits/sec [ 5] 6.00-7.00 sec 106 MBytes 891 Mbits/sec [ 5] 7.00-8.00 sec 177 MBytes 1.48 Gbits/sec [ 5] 8.00-9.00 sec 164 MBytes 1.37 Gbits/sec [ 5] 9.00-10.00 sec 106 MBytes 892 Mbits/sec [ 5] 10.00-10.00 sec 272 KBytes 838 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.00 sec 1.38 GBytes 1.18 Gbits/sec receiver ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- I think i have tx offloading disabled on both ends of this adapter. (Both on windows and on linux.) I haven't seen any actual instructions on how to disable it, and I'm running everything through NetworkManager. ❯ sudo route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default _gateway 0.0.0.0 UG 101 0 0 eth0 link-local 0.0.0.0 255.255.0.0 U 1000 0 0 eth1 192.167.0.0 0.0.0.0 255.255.0.0 U 100 0 0 eth1 192.168.1.0 0.0.0.0 255.255.255.0 U 101 0 0 eth0 ❯ sudo nmcli con show 8277ed12-04f7-4c82-bfeb-de24ec2df104 |grep tx ethtool.feature-tx: off Thanks for the assistance.
NicoD Posted November 23, 2020 Posted November 23, 2020 Hi. I'm having the problem that I don't know what your question is. I think others will have the same. Could you please formulate your question? And maybe also give the output of armbianmonitor -u
gprovost Posted November 24, 2020 Posted November 24, 2020 @Zageron Yeah please formulate a clear question. To check if tx offloading is on or off ethtool -k eth1 | grep tx-checksum Currently TX checksum offload for all network interfaces on rockchip64 family is disable in Armbian by default. 1
Zageron Posted November 24, 2020 Author Posted November 24, 2020 19 hours ago, gprovost said: @Zageron Yeah please formulate a clear question. To check if tx offloading is on or off ethtool -k eth1 | grep tx-checksum Currently TX checksum offload for all network interfaces on rockchip64 family is disable in Armbian by default. Yay 24 hour delay is over. This is regarding the degraded performance of the 2.5gbe on 5.8. I am unsure if my iperf results are aligning with what others are seeing. Given that tx offload is definitely off, I assume so. Formulated context and question: I have just put my helios64 together. I am seeing degraded performance of the 2.5gbe interface as warned. The notes I saw everywhere were "disable tx checksum offload". How do I check if tx offloading is on or off? I tested with ethtool, and yes it is off. ❯ sudo ethtool -k eth1 | grep tx-checksum tx-checksumming: off tx-checksum-ipv4: off tx-checksum-ip-generic: off [fixed] tx-checksum-ipv6: off tx-checksum-fcoe-crc: off [fixed] tx-checksum-sctp: off [fixed] I assume I have nothing else to do but wait for patches to improve the degraded performance at this point? Thanks for your patience and your answers! 2
gprovost Posted November 25, 2020 Posted November 25, 2020 You performance is not aligned with what we see on our side. Instead of getting 2.35 Gbit/s when TX offload works (e.g on LK4.4), with TX checksum offload disable, you should get around 1.8 Gbit/s You sure TX offload is off on both side ?
Zageron Posted November 25, 2020 Author Posted November 25, 2020 (edited) The other end looks like this: PS C:\Users\Zageron\Exercism\rust\proverb> NetAdapterChecksumOffload Name IpIPv4Enabled TcpIPv4Enabled TcpIPv6Enabled UdpIPv4Enabled UdpIPv6Enabled vEthernet (WSL) RxTxEnabled RxTxEnabled RxTxEnabled RxTxEnabled RxTxEnabled Helios Direct Disabled Disabled Disabled Disabled Disabled LAN WAN RxTxEnabled RxTxEnabled RxTxEnabled RxTxEnabled RxTxEnabled vEthernet (Default Switch) RxTxEnabled RxTxEnabled RxTxEnabled RxTxEnabled RxTxEnabled I managed to get performance up to 2.21 gbps by switching mtu to 9000 on both sides. PS C:\Users\Zageron\Exercism\rust\proverb> iperf3.exe -c helios64.local Connecting to host helios64.local, port 5201 [ 4] local 192.167.0.1 port 1504 connected to 192.167.0.2 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 261 MBytes 2.19 Gbits/sec [ 4] 1.00-2.00 sec 261 MBytes 2.19 Gbits/sec [ 4] 2.00-3.00 sec 260 MBytes 2.18 Gbits/sec [ 4] 3.00-4.00 sec 264 MBytes 2.22 Gbits/sec [ 4] 4.00-5.00 sec 264 MBytes 2.21 Gbits/sec [ 4] 5.00-6.00 sec 265 MBytes 2.22 Gbits/sec [ 4] 6.00-7.00 sec 266 MBytes 2.23 Gbits/sec [ 4] 7.00-8.00 sec 261 MBytes 2.19 Gbits/sec [ 4] 8.00-9.00 sec 263 MBytes 2.21 Gbits/sec [ 4] 9.00-10.00 sec 266 MBytes 2.23 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 2.57 GBytes 2.21 Gbits/sec sender [ 4] 0.00-10.00 sec 2.57 GBytes 2.21 Gbits/sec receiver However, resetting tx and rx offloading to default on on both ends results in the exact same performance. (2.21gbps) fyi mtu was set on linux with sudo nmcli con modify <interfaceuuid> ethernet.mtu 9000 Edited November 25, 2020 by Zageron Added instructoins for making mtu changes permenant.
gprovost Posted November 26, 2020 Posted November 26, 2020 Ok interesting. On my side I don't see any iperf difference increasing MTU beside seeing more retries. Here my perf with default MTU 1500. Helios64 Transmitting (TX checksum offload disabled) ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 10.10.10.254, port 59252 [ 5] local 10.10.10.2 port 5201 connected to 10.10.10.254 port 59254 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.01 sec 177 MBytes 1.48 Gbits/sec 0 4.29 MBytes [ 5] 1.01-2.01 sec 224 MBytes 1.88 Gbits/sec 0 4.29 MBytes [ 5] 2.01-3.01 sec 224 MBytes 1.88 Gbits/sec 0 4.29 MBytes [ 5] 3.01-4.01 sec 221 MBytes 1.85 Gbits/sec 0 4.29 MBytes [ 5] 4.01-5.01 sec 220 MBytes 1.85 Gbits/sec 0 4.29 MBytes [ 5] 5.01-6.01 sec 218 MBytes 1.82 Gbits/sec 0 4.29 MBytes [ 5] 6.01-7.01 sec 201 MBytes 1.69 Gbits/sec 0 4.29 MBytes [ 5] 7.01-8.01 sec 222 MBytes 1.87 Gbits/sec 0 4.29 MBytes [ 5] 8.01-9.01 sec 216 MBytes 1.81 Gbits/sec 0 4.29 MBytes [ 5] 9.01-10.00 sec 220 MBytes 1.86 Gbits/sec 0 4.29 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 2.09 GBytes 1.80 Gbits/sec 0 sender Helios64 Receiving ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 10.10.10.254, port 59256 [ 5] local 10.10.10.2 port 5201 connected to 10.10.10.254 port 59258 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 261 MBytes 2.19 Gbits/sec [ 5] 1.00-2.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 2.00-3.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 3.00-4.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 4.00-5.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 5.00-6.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 6.00-7.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 7.00-8.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 8.00-9.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 9.00-10.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 10.00-10.00 sec 601 KBytes 2.37 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.00 sec 2.72 GBytes 2.34 Gbits/sec receiver Just for the sake of clarification because iperf can be confusing. By default iperf client test upload speed. iperf -c <helios64-ip> = test RX speed of Helios64 iperd -c <helios64-ip> -R = test TX speed of Helios64 1
Zageron Posted November 26, 2020 Author Posted November 26, 2020 Default Offload Settings with 9000 MTU: PS L:\> iperf3.exe -c helios64.local Connecting to host helios64.local, port 5201 [ 4] local 192.167.0.1 port 59373 connected to 192.167.0.2 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 237 MBytes 1.98 Gbits/sec [ 4] 1.00-2.00 sec 255 MBytes 2.14 Gbits/sec [ 4] 2.00-3.00 sec 248 MBytes 2.08 Gbits/sec [ 4] 3.00-4.00 sec 241 MBytes 2.02 Gbits/sec [ 4] 4.00-5.00 sec 250 MBytes 2.10 Gbits/sec [ 4] 5.00-6.00 sec 244 MBytes 2.05 Gbits/sec [ 4] 6.00-7.00 sec 241 MBytes 2.02 Gbits/sec [ 4] 7.00-8.00 sec 254 MBytes 2.13 Gbits/sec [ 4] 8.00-9.00 sec 240 MBytes 2.01 Gbits/sec [ 4] 9.00-10.00 sec 221 MBytes 1.85 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 2.37 GBytes 2.04 Gbits/sec sender [ 4] 0.00-10.00 sec 2.37 GBytes 2.04 Gbits/sec receiver iperf Done. PS L:\> iperf3.exe -c helios64.local -R Connecting to host helios64.local, port 5201 Reverse mode, remote host helios64.local is sending [ 4] local 192.167.0.1 port 59414 connected to 192.167.0.2 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.01 sec 82.8 MBytes 687 Mbits/sec [ 4] 1.01-2.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 2.01-3.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 3.01-4.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 4.01-5.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 5.01-6.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 6.01-7.02 sec 0.00 Bytes 0.00 bits/sec [ 4] 7.02-8.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 8.01-9.01 sec 0.00 Bytes 0.00 bits/sec iperf3: error - unable to receive control message: Connection reset by peer Crashed the connection. Unable to use connection until rebooting Helios64 unit. TX Offloading disabled 1500 MTU: PS L:\> iperf3.exe -c helios64.local Connecting to host helios64.local, port 5201 [ 4] local 192.167.0.1 port 3691 connected to 192.167.0.2 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 156 MBytes 1.31 Gbits/sec [ 4] 1.00-2.00 sec 163 MBytes 1.37 Gbits/sec [ 4] 2.00-3.00 sec 124 MBytes 1.04 Gbits/sec [ 4] 3.00-4.00 sec 99.9 MBytes 839 Mbits/sec [ 4] 4.00-5.00 sec 157 MBytes 1.31 Gbits/sec [ 4] 5.00-6.01 sec 160 MBytes 1.32 Gbits/sec [ 4] 6.01-7.00 sec 98.4 MBytes 836 Mbits/sec [ 4] 7.00-8.00 sec 112 MBytes 941 Mbits/sec [ 4] 8.00-9.00 sec 176 MBytes 1.48 Gbits/sec [ 4] 9.00-10.00 sec 148 MBytes 1.25 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 1.36 GBytes 1.17 Gbits/sec sender [ 4] 0.00-10.00 sec 1.36 GBytes 1.17 Gbits/sec receiver iperf Done. PS L:\> iperf3.exe -c helios64.local -R Connecting to host helios64.local, port 5201 Reverse mode, remote host helios64.local is sending [ 4] local 192.167.0.1 port 3720 connected to 192.167.0.2 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 211 MBytes 1.77 Gbits/sec [ 4] 1.00-2.00 sec 248 MBytes 2.08 Gbits/sec [ 4] 2.00-3.00 sec 237 MBytes 1.98 Gbits/sec [ 4] 3.00-4.00 sec 211 MBytes 1.77 Gbits/sec [ 4] 4.00-5.00 sec 186 MBytes 1.56 Gbits/sec [ 4] 5.00-6.00 sec 205 MBytes 1.72 Gbits/sec [ 4] 6.00-7.00 sec 218 MBytes 1.83 Gbits/sec [ 4] 7.00-8.00 sec 192 MBytes 1.61 Gbits/sec [ 4] 8.00-9.00 sec 188 MBytes 1.58 Gbits/sec [ 4] 9.00-10.00 sec 220 MBytes 1.85 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 2.07 GBytes 1.78 Gbits/sec 2 sender [ 4] 0.00-10.00 sec 2.07 GBytes 1.77 Gbits/sec receiver Okay I understand a little more now. Receiving on helios is very slow, sending is slightly faster. Note that rx is on. ❯ sudo ethtool -k eth1 | grep rx-checksum rx-checksumming: on (same with windows, IP Offloading is set to rx only)
gprovost Posted November 26, 2020 Posted November 26, 2020 As you can see on my iperf, actually receiving on Helios64 is fast (2.3Gb/s which is the max for the 2.5GbE)... so my guess is that the low Helios64 receiving performance you see on your side is due to your client machine Ethernet interface. Maybe the windows driver are not performing well.
Zageron Posted November 26, 2020 Author Posted November 26, 2020 I see! Yes, modifying settings on the windows machine has improved both. However, I am still seeing consistent lock-up / crashing of the interface. Is there anything I can grab for you for details? PS L:\> iperf3.exe -c helios64.local -R -t 700 Connecting to host helios64.local, port 5201 Reverse mode, remote host helios64.local is sending [ 4] local 192.167.0.1 port 4362 connected to 192.167.0.2 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 205 MBytes 1.72 Gbits/sec [ 4] 1.00-2.00 sec 234 MBytes 1.96 Gbits/sec [ 4] 2.00-3.00 sec 233 MBytes 1.95 Gbits/sec [ 4] 3.00-4.00 sec 234 MBytes 1.97 Gbits/sec [ 4] 4.00-5.00 sec 235 MBytes 1.97 Gbits/sec [ 4] 5.00-6.00 sec 235 MBytes 1.97 Gbits/sec [ 4] 6.00-7.00 sec 235 MBytes 1.97 Gbits/sec [ 4] 7.00-8.00 sec 241 MBytes 2.02 Gbits/sec [ 4] 8.00-9.00 sec 243 MBytes 2.04 Gbits/sec [ 4] 9.00-10.00 sec 242 MBytes 2.03 Gbits/sec [ 4] 10.00-11.00 sec 243 MBytes 2.04 Gbits/sec [ 4] 11.00-12.00 sec 238 MBytes 2.00 Gbits/sec [ 4] 12.00-13.00 sec 231 MBytes 1.94 Gbits/sec [ 4] 13.00-14.00 sec 233 MBytes 1.96 Gbits/sec [ 4] 14.00-15.00 sec 232 MBytes 1.95 Gbits/sec [ 4] 15.00-16.00 sec 236 MBytes 1.98 Gbits/sec [ 4] 16.00-17.00 sec 241 MBytes 2.02 Gbits/sec [ 4] 17.00-18.00 sec 238 MBytes 2.00 Gbits/sec [ 4] 18.00-19.00 sec 243 MBytes 2.04 Gbits/sec [ 4] 19.00-20.00 sec 231 MBytes 1.94 Gbits/sec [ 4] 20.00-21.00 sec 233 MBytes 1.95 Gbits/sec [ 4] 21.00-22.00 sec 232 MBytes 1.95 Gbits/sec [ 4] 22.00-23.00 sec 226 MBytes 1.89 Gbits/sec [ 4] 23.00-24.00 sec 238 MBytes 2.00 Gbits/sec [ 4] 24.00-25.00 sec 241 MBytes 2.02 Gbits/sec [ 4] 25.00-26.00 sec 243 MBytes 2.04 Gbits/sec [ 4] 26.00-27.00 sec 236 MBytes 1.98 Gbits/sec [ 4] 27.00-28.00 sec 229 MBytes 1.92 Gbits/sec [ 4] 28.00-29.00 sec 233 MBytes 1.96 Gbits/sec [ 4] 29.00-30.00 sec 234 MBytes 1.96 Gbits/sec [ 4] 30.00-31.00 sec 233 MBytes 1.96 Gbits/sec [ 4] 31.00-32.00 sec 236 MBytes 1.98 Gbits/sec [ 4] 32.00-33.00 sec 238 MBytes 2.00 Gbits/sec [ 4] 33.00-34.00 sec 244 MBytes 2.05 Gbits/sec [ 4] 34.00-35.01 sec 222 MBytes 1.85 Gbits/sec [ 4] 35.01-36.00 sec 0.00 Bytes 0.00 bits/sec [ 4] 36.00-37.00 sec 0.00 Bytes 0.00 bits/sec [ 4] 37.00-38.00 sec 0.00 Bytes 0.00 bits/sec [ 4] 38.00-39.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 39.01-40.01 sec 0.00 Bytes 0.00 bits/sec ... Here's the Helios: Accepted connection from 192.167.0.1, port 4358 [ 5] local 192.167.0.2 port 5201 connected to 192.167.0.1 port 4362 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 207 MBytes 1.74 Gbits/sec 0 422 KBytes [ 5] 1.00-2.00 sec 234 MBytes 1.96 Gbits/sec 0 422 KBytes [ 5] 2.00-3.00 sec 232 MBytes 1.95 Gbits/sec 0 422 KBytes [ 5] 3.00-4.00 sec 235 MBytes 1.97 Gbits/sec 0 422 KBytes [ 5] 4.00-5.00 sec 235 MBytes 1.97 Gbits/sec 0 422 KBytes [ 5] 5.00-6.00 sec 234 MBytes 1.96 Gbits/sec 0 422 KBytes [ 5] 6.00-7.00 sec 235 MBytes 1.97 Gbits/sec 0 422 KBytes [ 5] 7.00-8.00 sec 240 MBytes 2.02 Gbits/sec 0 422 KBytes [ 5] 8.00-9.00 sec 243 MBytes 2.03 Gbits/sec 0 422 KBytes [ 5] 9.00-10.00 sec 243 MBytes 2.04 Gbits/sec 0 422 KBytes [ 5] 10.00-11.00 sec 243 MBytes 2.04 Gbits/sec 0 422 KBytes [ 5] 11.00-12.00 sec 238 MBytes 1.99 Gbits/sec 0 422 KBytes [ 5] 12.00-13.00 sec 233 MBytes 1.95 Gbits/sec 0 422 KBytes [ 5] 13.00-14.00 sec 232 MBytes 1.95 Gbits/sec 0 422 KBytes [ 5] 14.00-15.00 sec 233 MBytes 1.95 Gbits/sec 0 422 KBytes [ 5] 15.00-16.00 sec 236 MBytes 1.98 Gbits/sec 0 422 KBytes [ 5] 16.00-17.00 sec 240 MBytes 2.02 Gbits/sec 0 422 KBytes [ 5] 17.00-18.00 sec 239 MBytes 2.00 Gbits/sec 0 422 KBytes [ 5] 18.00-19.00 sec 243 MBytes 2.04 Gbits/sec 0 422 KBytes [ 5] 19.00-20.00 sec 231 MBytes 1.94 Gbits/sec 0 422 KBytes [ 5] 20.00-21.00 sec 233 MBytes 1.95 Gbits/sec 0 422 KBytes [ 5] 21.00-22.00 sec 232 MBytes 1.94 Gbits/sec 0 422 KBytes [ 5] 22.00-23.00 sec 226 MBytes 1.89 Gbits/sec 0 422 KBytes [ 5] 23.00-24.00 sec 239 MBytes 2.00 Gbits/sec 0 422 KBytes [ 5] 24.00-25.00 sec 240 MBytes 2.02 Gbits/sec 0 422 KBytes [ 5] 25.00-26.00 sec 243 MBytes 2.04 Gbits/sec 0 422 KBytes [ 5] 26.00-27.00 sec 237 MBytes 1.99 Gbits/sec 0 422 KBytes [ 5] 27.00-28.00 sec 230 MBytes 1.92 Gbits/sec 0 422 KBytes [ 5] 28.00-29.00 sec 233 MBytes 1.96 Gbits/sec 0 422 KBytes [ 5] 29.00-30.00 sec 234 MBytes 1.96 Gbits/sec 0 422 KBytes [ 5] 30.00-31.00 sec 233 MBytes 1.96 Gbits/sec 0 422 KBytes [ 5] 31.00-32.00 sec 235 MBytes 1.97 Gbits/sec 0 422 KBytes [ 5] 32.00-33.00 sec 238 MBytes 2.00 Gbits/sec 0 422 KBytes [ 5] 33.00-34.00 sec 244 MBytes 2.05 Gbits/sec 0 422 KBytes client_loop: send disconnect: Broken pipe ❯ ssh helios64.local ssh: connect to host helios64.local port 22: Connection refused ❯ ssh 192.168.1.236 _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 20.11 Buster with Linux 5.9.10-rockchip64 No end-user support: work in progress System load: 2% Up time: 10:02 Memory usage: 6% of 3.71G IP: 192.168.1.236 192.167.0.2 CPU temp: 48°C Usage of /: 14% of 15G [ General system configuration (beta): armbian-config ] Last login: Thu Nov 26 08:42:37 2020 from 192.167.0.1 ❯ sudo ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.236 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::31d5:231c:fc4f:efc3 prefixlen 64 scopeid 0x20<link> inet6 2001:569:7e49:4101:7221:5284:6898:f078 prefixlen 64 scopeid 0x0<global> ether 64:62:66:d0:06:18 txqueuelen 1000 (Ethernet) RX packets 47851 bytes 6758700 (6.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 26542 bytes 20436445 (19.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 27 eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.167.0.2 netmask 255.255.0.0 broadcast 192.167.255.255 inet6 fe80::d8eb:9112:1d81:8ae7 prefixlen 64 scopeid 0x20<link> ether 64:62:66:d0:06:19 txqueuelen 1000 (Ethernet) RX packets 21137514 bytes 29374154279 (27.3 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 11354240 bytes 16174541188 (15.0 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 1 bytes 145 (145.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1 bytes 145 (145.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ~ ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── zageron@helios64 08:50:24 ❯ From here, if I being the adapter down and then back up it hard locks the Helios. So I generally safely sudo reboot at this point.
gprovost Posted November 27, 2020 Posted November 27, 2020 you do armbianmonitor -u and share the link here
Zageron Posted November 27, 2020 Author Posted November 27, 2020 http://ix.io/2FHd This is the machine in the broken state. (Requiring reboot)
Recommended Posts