Hi all,
I’m looking for an experienced OpenWrt developer for a paid contract to build a production-grade OpenWrt firmware for the NanoPi R5S (RK3568).
Scope (high level):
Latest stable OpenWrt (no snapshots)
fw4 + nftables (iptables-nft only)
MWAN3 failover (no CONNMARK errors, LB/bonding ready)
MPTCP + bonding support
Docker (nft-compatible)
LTE (EG25): QMI default, MBIM/ECM available, ModemManager disabled by default
NVMe mounted at /mnt/nvme
RK3568 HW H.265 → ffmpeg → RTSP (mediamtx),
Full USB-serial + ST-LINK support
Reproducible build (ImageBuilder or full source) + matching SDK
This is not a hobby build — deliverables, validation, and reproducibility are required.
If you have real experience with Rockchip/RK3568 and MWAN3/nft, please reply or PM.
No this is not AI advice, I am using the original FriendElec FriendlyWrt and MWAN3 is giving me the CONNMARK errors and it does not support Bonding - I dont want FriendlyWrt anymore I want a real OpenWrt , hence I am looking for professional help.
as far as I know to do bonding I need the kernel to support mctcp, I know what to do on top of and I also know that I need an external proxy server to support bonding. But OpenWrt must be able to join two interfaces (two WANs) and send the information with “tags” whatever that is called.
Hello brada4, thank you so much! let me know if you have bandwidth to help me at least for some support and questions. I have never built my own OpenWrt but the person who used to do it for me is unavailable and I need to solve the problem this week. Cheers.
I want two WAN ports to start as failover using mwan3 while I am building a Bonding server on the cloud. At that point, I want to enable bonding on the router configure it to work with the server and the magic should happen.