FriendlyElec Nanopi R4S Mini Portable Travel Router OpenWRT with Dual-Gbps Ethernet Ports 4GB LPDDR4 Based in RK3399 Soc for IOT NAS Smart Home Gateway

Product Information

To change the setting of "eth1" you can add a new file similar to eth0's configuration file under the /etc/network/interfaces. Rockchip RK3399 powered NanoPi R4S router SBC launched at the beginning of the month, and FriendlyELEC kindly sent a review sample to CNX Software. The grep command prints the line from /proc/interrupts, awk prints the first column which is the IRQ number, and xargs trims the whitespace.

I think that way the results will reflect the most common case scenarios, which is use the board in a home or small office environment. NanoPi R4S is a high-end Friendly Elec mini-router with edge-computing and dual Gbps Ethernet ports. The NanoPi R4S (as "R4S") is a FriendlyElec mini-router with edge-computing and dual Gbps Ethernet ports. Compared to its predecessor NanoPi R2s FriendlyElec offers 1 GByte or 4 GByte DDR3 RAM configurations on a small PCB measuring 66 x 66 mm, so the board is very compact and can be placed almost in every environment without occupying too much space.The R4S Enterprise version has a built-in EEPROM chip (Model: 24AA025E48T) which has a globally unique MAC address. I found it out today, when I tried again with a completely separate supply for the NanoPi rather than the USB hub from yesterday, where I had both, the AT34 and the serial adapter, plugged in. One thought for making this board really useful is to add OpenMediaVault – and that means Debian 10 for OMV 5.

Because ipfire web GUI is straighter on by far, and ipfire does not draw that peak currents on boot, that friendlyWRT draws, and which may let an .Of course I had to mount it very properly and totally safe with fitting spacer adapter nuts and Kapton tape like every high-grade engineer would do. FriendlyCore has some issues, and limited information in NanoPi R2S Wiki, so instead let’s try FriendlyWrt, and I flashed rk3399-sd-friendlywrt-5. While not visible in the pictures I created models from the heat sinks from scratch and picked up a generic 30x30mm fan model from GrabCAD. The noticeable difference between competitor boards, especially cheaper ones, is that the second interface is connected internally via PCIe and not via USB.

I even refuse to waste my time reading network tests reports if the report suggests that nobody knows how affinity was done nor which modules were loaded.I then configured a SAMBA share in LuCi and the command line, to transfer files from my laptop to the USB drive connected to NanoPi R4S. It is (apparently) a good hardware platform for developing IoT applications, NAS applications, smart home gateways etc. The balanced (high) speeds of the Pi 4 cores make a difference, but at the expense of slightly higher WAN latency when using a USB NIC and less convenient sysupgrades (due to missing kernel modules). but there some issues which we’ll detail in this preview, so I then switch to FriendlyWrt built upon OpenWrt 19.

Enter the "Services" -> "Terminal", enter the "poweroff" command and hit enter, wait until the led light is off, and then unplug the power supply. This explains also a lot wrt poor Samba performance (where UAS blacklisting of the Seagate disk is missing too). You may need to prise it out gently from the USB ports side if the heatsink pad sticks the board to the case. As you can see from the above diagram the workstation is connected on the GbE switch as also the WAN interface of the Nanopi-RxS (I mean both R2S and R4S).Especially the really low power (1,5-1,8W), while running the red net (via the RTL NIC) with 100Mbps. I believe that network variation is a big factor as my results early morning are far more consistent and don't show a big drop.