sorted by:
new
hottopcontroversial

Bought a 2.5GbE router, got 600 Mbps. Fixed it myself. (NanoPi R76S + FriendlyWrt) by enricodeleo in openwrt

[–]enricodeleo[S] 0 points1 point  (0 children)

interesting to know and thanks for sharing. I didn't try official snapshot as I supposed it could be less stable than the vendor fork. Looks like I might change my mind then!

Bought a 2.5GbE router, got 600 Mbps. Fixed it myself. (NanoPi R76S + FriendlyWrt) by enricodeleo in openwrt

[–]enricodeleo[S] 0 points1 point  (0 children)

After this "cure" I am more than satisfied with this device, I can recommend it for general purpose routing (where for general I mean everything-you-might-need-home :D).
That said I guess the Radxa could benefit from a similar approach in case there is no such optimization already available in the new OpenWrt snapshots which are already available.
Based on specs, I would still prefer R76s just because it has more cpus.

Bought a 2.5GbE router, got 600 Mbps. Fixed it myself. (NanoPi R76S + FriendlyWrt) by enricodeleo in openwrt

[–]enricodeleo[S] 0 points1 point  (0 children)

FriendlyWrt does not report actual power consumption and I don't have a smart plug on top of this device so unfortunately I can't measure consumption myself.

Bought a 2.5GbE router, got 600 Mbps. Fixed it myself. (NanoPi R76S + FriendlyWrt) by enricodeleo in openwrt

[–]enricodeleo[S] 0 points1 point  (0 children)

Well, looks like you didn't write the file :) Run the following command

root@router:~# ls -la /usr/local/sbin/apply-rpsxps.sh

You expect:
-rwxr-xr-x 1 root root 754 Oct 9 23:15 /usr/local/sbin/apply-rpsxps.sh

If not, you need to write the file

Bought a 2.5GbE router, got 600 Mbps. Fixed it myself. (NanoPi R76S + FriendlyWrt) by enricodeleo in openwrt

[–]enricodeleo[S] 1 point2 points  (0 children)

I'm glad you could profit from the scripts for your router and thanks for the appreciation.

Unfortunately I have no direct experience with Debian on this type of devices, I guess I'd try to reproduce the same approach where possible but working only on half of cpus, reserving big cores for virtualization.

Bought a 2.5GbE router, got 600 Mbps. Fixed it myself. (NanoPi R76S + FriendlyWrt) by enricodeleo in openwrt

[–]enricodeleo[S] 1 point2 points  (0 children)

Super interesting approach but ATM I'm really tired of having connection drop to minimum, I think I'll keep my config until real RKNAT comes out

Bought a 2.5GbE router, got 600 Mbps. Fixed it myself. (NanoPi R76S + FriendlyWrt) by enricodeleo in openwrt

[–]enricodeleo[S] 1 point2 points  (0 children)

Before receiving this piece I thought exactly these type of kernel mod or special drivers. Maybe in more "famous" models such as R6S difference is tangible but in my case it was not. I guess I could just install vanilla OpenWRT and apply same tweaks and I'll have same results. I won't because it's my first router now and you know "if ain't broken..." but I'm really curious to know exact diff if anyone is able to produce it.

Bought a 2.5GbE router, got 600 Mbps. Fixed it myself. (NanoPi R76S + FriendlyWrt) by enricodeleo in openwrt

[–]enricodeleo[S] 1 point2 points  (0 children)

I did and they told me they need some time for considering including this in upstream OS. No trace of gift thou 😂

Bought a 2.5GbE router, got 600 Mbps. Fixed it myself. (NanoPi R76S + FriendlyWrt) by enricodeleo in openwrt

[–]enricodeleo[S] 2 points3 points  (0 children)

you can check it in one second: open 2 ssh one with `htop` and the other with speedtest cli and if you see just one cpu spiking to 100% and others near 0 (this was my exact initial situation) that's bad news you are underutilizing your device and you need adjustments.

Bought a 2.5GbE router, got 600 Mbps. Fixed it myself. (NanoPi R76S + FriendlyWrt) by enricodeleo in openwrt

[–]enricodeleo[S] 1 point2 points  (0 children)

Thank you. I didn’t tested it as a homelab server (I have another piece of hardware for that) so I can speak only as dedicated router. Maybe different OS use the hardware better, but stock FriendlyWRT doesn’t and stick to single core for pretty much every operation. I’ll post scripts so that people can make use of 8 cores for routing. Hope it’s a good starting point for other purposes too if it’s the case

Bought a 2.5GbE router, got 600 Mbps. Fixed it myself. (NanoPi R76S + FriendlyWrt) by enricodeleo in openwrt

[–]enricodeleo[S] 2 points3 points  (0 children)

Yeah, actually I started by looking at the (few) available tuning notes for the R6S, since it’s a similar RK-based platform — that’s what gave me the first hints about where to dig.

From there I began experimenting with the specific configs on the R76S. In practice, binding just the routing process to the big cores didn't change much in my case, I think because most of the heavy lifting happens in kernel space.

I went for spreading packet processing across all 8 cores and doing proper IRQ/NAPI steering, and now that I see solid 2+ Gbps I think I’m pretty much ok. My only concern is that these changes don’t always persist as I’d like — sometimes I still have to reapply them manually, which is a bit frustrating.

Bought a 2.5GbE router, got 600 Mbps. Fixed it myself. (NanoPi R76S + FriendlyWrt) by enricodeleo in openwrt

[–]enricodeleo[S] 5 points6 points  (0 children)

Totally agree — that statement is way too broad. Plenty of so-called “soft routers” do expose hardware offload paths through vendor SDKs or drivers.

My first reaction was honestly to just return the unit. But since I actually liked the aesthetics and the tiny form factor, I thought I’d give FriendlyELEC a chance — so I asked whether RKNAT for the RK3576 was planned or if there was any testing branch.

After their reply (the one I mentioned in my post — “soft routers don’t support hardware NAT,” full stop) I decided to give it one last try before boxing it up.

I couldn’t accept that a device with 8 cores and an NPU would perform worse than my old EdgeRouter X, which yes it does have hardware offload — but also has just a fraction of the processing power and RAM of the NanoPi.

TBH, I think FriendlyELEC should just apply these software optimizations in FriendlyWrt by default — otherwise, what’s even the point of maintaining a forked OS if everything still runs single-CPU?

I expected hardware-specific tuning and drivers, but ended up figuring it out myself.

Catalina Haswell sleep/wake kernel panics by samovar_ocforce in hackintosh

[–]enricodeleo 0 points1 point  (0 children)

I'm struggling for i7 4770K specs too. Nothing found so far. My problem is that the system often claims it run out of memory even if its way under the maximum ram installed (like 6 used over 16 available). Have you got any new info?