I assume you mean the R5S is $20 extra and you assume it has extra performance, in which case I would say not necessarily.
The R4S has two ARM A72 cores (in addition to four slower A53 cores) that are appreciably faster than the R5S A55 cores. For CPU performance (especially applications that can only use a single core like OpenVPN and CAKE SQM), the R4S may be a better option. For 2.5G LAN and/or HDMI port for a monitor, the R5S is a better option. It really depends on what is more important for you.
That's interesting because I actually meant the R4S as the more expensive one, which means the R5S should be good for my needs? Or would i miss the faster cores and 2GB of extra ram on the R4S, maybe for other use cases of the device? (though i don't think I'm an expert enough to try them)
I would get the R4S 4GB for your needs (gigabit routing with sqm cake, along with some simple vpn and adblock), not the R5S. Get the metal case either way.
The RK3399 in the R4S is ~2X faster for single core tasks, and ~1.4x faster for multi-core than the RK3568 in the R5S. The faster CPU in the R4S will be better for SQM CAKE and VPN.
If your asking for the R5S M.2 PCIe x1, yes works , I have tried with NVMe sdd and a m.2 to pcie adapter, connected to an intel i350 t4 NIC that make a total 7 ports, 5 x 1G and 2 x 2.5G, impressive device.
Simplest way of managing is stay with customized firmware from manufacturer and attach & wait for their updates and config process. In the other hand, better way of doing things IMO is the official OpenWRTish community supported way, which from I was reading here in forums is better recommended in order to use extended partitions space without dealing with resize2fs monkeyBuisness: For the Rxxs scenario, this is to boot read-only build images from a quality sdcard and configure the emmc as an ext4/F2FS formatted read-write extroot overlay space.
So far it is running very well and quite stable. I really appreciate and thank you for your work in supporting this device from an official OpenWrt fork (FriendlyWrt build is very cumbersome).
One question: is there any technical aspect that is preventing adding R5S to the official OpenWrt builds?
I'm interested in using the nanoPI r5s for some OpenWRT tinkering and possibly as a travel router.
The travel router setup requires WIFI obviously and the fact that the case has an antenna mount hole already is curious and convenient!
Can anyone recommend a good way to use the M.2 slot for this?
I guess that an M.2 key adapter might be required (from M to A/E).
Or an adapter to be able to use a mini PCIe card might allow for a more suitable AP-capable card. The latter would probably require some case modifications.
For posterity, and in case of broken links, this is an example of an M.2 M to M.2 A+E adapter along with a new base cover for the r5s with a cutout for the card and two antennas + mounts.
It then begs the question of suitable AP-capable cards. I see this is an OpenWRT FAQ but if anyone has r5s specific advice on this, that would be great too.
On the r5s with a m.2 to m.2 key e+a adapter, I had tested these cards: mt7922 and mt7921k with ax and Wi-Fi 6E support and Atheros QCNFA364A , only support ac Wi-Fi.
Did you observe any performance issues or driver problems worth noting?
Ideally I'd be able to use something with DBDC for best AP functionality. There seem to be a few options but not sure of driver quality / support.
e.g.
QCA6391 via ath11k driver
mt7615d or mt7915d
I'll follow the various threads and report back here if I try something with the r5s.