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

The main NanoPi difference from the linked example will be that it has only a single non-wan port, that being eth1, to send the untagged lan vlan 1 and tagged vlans 10, 20 and 30 for IOT1, IOT2 and GST, respectively, to in the linked example. If your main network is IPv4, and NanoPi-R4S works in IPv6, the computer may not be able to connect to the Internet. It is recommended to turn off IPv6 (the method is described later in this WiKi), or switch the main route to IPv6;

Nice. I overlooked NanoPi R4S first. I remember there was a board with almost the same name, "NanoPi R4something", which had 2nd ethernet port through a usb controller to cpu. Ie. almost as RPi 4 with a USB-dongle, but one can't change the dongle. The R4S seems to have both real (quote from the above OpenWrt Developer thread): The reason why we would want to do this is so we can stop bufferbloat at higher bandwidths with SQM (Smart Queue Management). Currently consumer routers usually can't push past 350 Mbps with luci-app-sqm on because the SQM algorithm cake, uses a lot of CPU processing power. The only way we can get close to 1 Gbits with SQM is by building our own router or using hardware like the NanoPi R4S. Maintainers and community have deep understanding how HW work. We are seniors with 30+ years of experience in Linux + embedded Linux. Open Kernel command line: console=ttyS2,1500000 earlycon=uart8250,mmio32,0xff1a0000 root=PARTUUID=5452574f-02 rw rootwaitWell, that is a valid choice, but whenever your link gets saturated, be it transiently only or continuously, the default FIFO with too deep buffers is going to introduce additional variable latency to your flows. If you can either guarantee that you will never fully saturate your link or that you never use latency-sensible flows (like even interactive web-browsing to some degree) then it is a no brainer to not waste CPU cycles on traffic shaping. If you are not 100% sure traffic shaping might be worth trying out. My measured bandwidth without SQM from my ISP is 920Mbps DL and 35Mbps UL. My NanoPi R4S running FriendlyWrt can do SQM with fq_codel (simplest.qos) ranged up to 800 Mbps without issue. With cake (piece_of_cake.qos) the best speeds I could get with SQM rup to 700 Mbps.

BASH or ZSH shell, standard Debian/Ubuntu utilities. Features can be adjusted with menu-driven utility. Login is possible via serial, HDMI or SSH. Universal Official Link: https://store.ui.com/collections/unifi-network-access-points/products/unifi-ap-6-lite Use a USB A-to-A cable, connect NanoPi-R4SE to a PC as follows. Note: please pay attention to the USB port the USB cable is connected to in the screenshot. So i still think that changing this file is the best way of doing things, cause then you dont have anything extra doing anything or needing to be executed or hogging any resources even if its minimal!My current connection is 600Mbps. On the SEEED ODYSSEY - X86J4105 which has a CPU Mark Score of ~3000 and it handles 600Mbps DL with ease. The htop screenshot below tells me it uses at most 37% of my CPU under full load. In theory, we can guess that a CPU mark of 3000 should be able to work for 1000 Mbps connections, if 600 Mbps only uses 37% CPU at most. wget https: //raw.githubusercontent.com /friendlyarm /sd-fuse_rk3399 /kernel- 6.1.y /prebuilt /boot /logo_kernel.bmp

Improved stability on first boot (previous version, bpfilter error occurred in some cases on first boot) wget https: //raw.githubusercontent.com /friendlyarm /sd-fuse_rk3399 /kernel- 6.1.y /tools /mkkrnlimg && chmod 755 mkkrnlimg If you plan on only having one Ubiquti AP I recommend installing via the phone so you don't have to bother with more complicated things like AP Controllers. They are setting up the irq of each eth on cores 4 and 5 with hex 10 and 20 respectively and are not setting up the queues with anything, which makes openwrt use hex 00 by default for the queues of both eth after booting and the result is that openwrt will throw the queues also on cores 4 and 5 together with the IRQ. To quote the docs, by default, cake will use triple-isolate: “which will first make sure that no internal or internal host will hog too much bandwidth and then will still guarantee for fairness for each host. In that mode, Cake mostly does the right thing. It would ensure that no single stream and no single host could hog all the capacity of the WAN link. However, it can’t prevent a BitTorrent client – with multiple connections – from monopolizing most of the capacity.” You can enable per host isolation, which will identify all source/destination information.As for the power supply I'd recommend the CanaKit Raspberry Pi power supply over the one FriendlyElec provides: https://amzn.to/3T5XzuP 1.1 Introduction and Why? If you restart Smart Queue Management or change SQM settings, it will reset the CPU affinity and you will need to reset your settings or re-apply them.