Joined in 2023 
82 
63 About this deal
As I can see there is the same problem with speed as in OpenWRT when it's doesn't use IRQ to correct CPU Core pinning (cpu affinity). An ethernet repeater with firewall functionality: the topology is limited with only 1 output port and why use such a powerful multimedia chip for this? So I got rid of the vendor stuff but that left me with a few unanswered questions: How would they properly update their boot loader and kernel package? As you can see the processor usage is ~60% which the double compared to the Nanopi-R4S, but again the docker daemon uses ~30% of the CPU. By the way I strongly suggest to follow Thomas around wherever he leaves comments like on cnx-software.
This happened because I’ve added the heatsink in the middle of the test, but that was eventually a good thing because I’ve seen the difference that it does.Finally, I’ve also added a 2x parallel socket test for TCP and for UDP I’ve tested both directions (server/client).
On mine, I had to enable both "enable root login" and "enable password login" on the GUI to be able to log in. FriendlyELEC's Buildroot is based on Rockchip's version which is made with linux-sdk and maintained with git. Based on the table in the previous section, select the appropriate version of the compiler and add the compiler's path to PATH.As you can see from the above benchmarks the Nanopi-R4S WAN interface is fully capable of GbE speed, which is really cool. We strongly think that the NanoPi R4S could have been more successful as a personal router device with additional 2-3 LAN ports. For traffic shaping at 1 Gbps one does not need that high performance an x86 CPU a number of atom based SoCs are also up to that task.
In the tables I’ll be adding the commands that I’m using on each server/client and then I’ll add the result that iperf outputs. sd-fuse" is a collection of scripts that can be used to create bootable SD card images for FriendlyElec boards. If you want stability in a production environment or low headaches as a novice user, skip rolling releases. For a reference point, my RPi4 does cake/piece_of_cake on an asymmetric 900000 kbit/s down/300000 kbit/s with no buffer bloat (waveform test). is supposed to be the next LTS series which means that OpenWRT and other distros will pick it up as their next major kernel version to support.
I put the sd card on the r4s and turn it on, the red led will light up and after some moments the lan and wan led will light up together for like 1-2 seconds then they will turn off to never turn on again and the system led will never turn on. Especially the really low power (1,5-1,8W), while running the red net (via the RTL NIC) with 100Mbps.
The Nanopi-R4S’s case is very compact and it’s only a bit bigger than its predecessor Nanopi-R2S, but also includes more horse power under the hood.
This explains also a lot wrt poor Samba performance (where UAS blacklisting of the Seagate disk is missing too). As you can see the CPU usage is ~35%, but most of the load is because of the docker daemon that is running in the background. To assemble the board inside the case, you will first put the thermal pad on top of the CPU and position it carefully inside the case. I did not get any problems to get an IP address this time, and the WAN and LED are working as expected (green ON) on the board.
Great Deal 
New Comment