YAOF dropped Docker, points its download link at another repository, and documents a reset command
OpenWrt for Nanopi R2C/R2S/R4S/X86
At a glance
- What is it?
- A Chinese-language OpenWrt 25.12 firmware build for the Nanopi R2C, R2S and R4S plus x86, bundled with proxy, ad blocking and traffic plugins. It is licensed GPL-3.0 while asking not to be used commercially, and its own troubleshooting instruction is to ssh in and reset the box.
- Who is it for?
- YAOF suits someone who has one of the four named boards, wants a router image with a proxy stack and ad filtering already configured, and is comfortable with a Chinese-language feature list and an ssh-based support path. It does not suit someone who needs Docker in the current build, since the project points those users at the older 23.05 series instead, and it does not suit a commercial deployment given the non-commercial statement sitting next to a GPL-3.0 licence.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly Shell, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- QiuSimons/YAOF2,783 ★ · +9
| Repository | 2026-10-04 | 2026-11-15 |
|---|---|---|
| QiuSimons/YAOF | 2.8k | 2.8k |
9 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
A Chinese-language OpenWrt 25.12 build for four named boards
The documentation is written in Chinese, and it is short, which means the feature list is effectively the whole specification. The base is native OpenWrt 25.12, and the default management address is `192.168.1.1`. Four targets are named in the project description: the Nanopi R2C, the R2S, the R4S, and generic x86 hardware.
Two build choices are stated outright. The image is compiled with O2 optimisation and tuned CFLAG settings, which is a deliberate departure from a size-first build and explains why the project lists it as a feature rather than a default. And two things that are often missing from community images are called out as working here: the built-in upgrade function and the physical reset button on the device.
The licence situation needs reading twice. The repository is licensed GPL-3.0, and the headline of the documentation, in large type above the feature list, says the software must not be used for commercial purposes. Those are two different grants. GPL-3.0 permits commercial use, so the notice is a restriction the licence itself does not impose, and anyone planning to ship this in a product should resolve it with the author rather than pick whichever reading is convenient.
Docker was removed, and Docker users are told to stay on 23.05
This is the most consequential line in the feature list. The current build no longer integrates Docker, and users who genuinely need it are told to stay on the 23.05 series instead. That is a different OpenWrt release line from the 25.12 this branch is built on, so the advice is effectively to run an older image rather than to enable something.
The same bullet then tells you what to do if you want Docker anyway: first switch on the auto-start option under the Docker configuration panel and save the application settings. So the feature is described as removed, and the next sentence is an instruction for turning it on. A separate bullet adds a one-click plugin that formats and mounts the remaining space on the device, which exists specifically for Docker users.
The reasonable reading is that the image still carries the container stack but no longer starts it for you, and that the maintainer would rather you did not use it on this branch. Either way, the practical question for anyone evaluating the firmware is whether the removal is about the image size, about the flash and memory budget on these boards, or about support, and the documentation does not say.
The default branch is named `25.12`, matching the OpenWrt series it tracks.
MosDNS does double duty as ad filtering and as DNS routing
One plugin gets an explicit warning rather than a bullet. MosDNS is configured to act as both the ad filtering mechanism and the DNS split routing mechanism at the same time, which is an unusual pairing to have on by default and worth understanding before you change it.
The rest of the bundled list is long and falls into recognisable groups. Proxy clients: SSRP, PassWall, OpenClash, Mihomo, and DAED. Network services: SQM, DNSProxy, wake on LAN, DDNS, UPnP, FullCone NAT, which is noted as enabled by default in the firewall, traffic offloading, an interrupt affinity optimisation, Zerotier, and both FRPC and FRPS. Consumer extras: WeChat push notifications, NetEase Cloud Music unlocking, a JD.com daily check-in, a download accelerator, wireless printing, traffic monitoring, an ad filtering ruleset, and an OLED driver for the R2S.
The project also states that package installation is frictionless, in the sense that opkg and kernel module packages install without extra steps. Combined with the preconfigured plugin set, the image is aimed at people who want a working router quickly rather than people assembling one from a base build.
The first thing to try when something breaks is an ssh reset
The last bullet of the feature list is a support instruction, and it is the most quotable thing in the documentation. If you have any problem, it says, first try to ssh into the device, type `fuck`, press enter, wait for the machine to reboot, and then check whether the problem has been resolved.
That is a factory reset reachable over ssh, offered as step one. It is an honest thing for a router image to offer, since most configuration damage on these devices is unrecoverable without it, and the alternative is a user debugging a wedged LuCI session by hand. It is also destructive without a warning label, and it is written in the same tone as the rest of a feature list.
The line is worth reading as a design signal rather than a joke. It implies the maintainers expect a class of problem that configuration edits cannot recover from, and that they would rather you reset than diagnose. If you rely on this image for anything you cannot rebuild quickly, that expectation is worth planning around.
AES acceleration on armv8, but only for AEAD connections
One bullet is a performance note with a constraint attached. The ss protocol has AES hardware acceleration implemented on armv8, and the documentation asks, in bold, that you use only connections with AEAD encryption. The two halves belong together: hardware acceleration for the older cipher modes is either unavailable or not what the implementation covers, so a configuration that relies on a non-AEAD cipher will not get the acceleration even though the hardware is there.
That matters on the boards this image targets, since the R2C and R2S are armv8 parts and a router is a device where throughput on the tunnel is the difference between a usable link and a saturated one.
Two other system-level defaults are enabled rather than offered as options: BBRv3 congestion control and LRNG, the kernel entropy source. Both are on by default in this build. Congestion control on a residential uplink is a choice with real consequences for a long tunnel, and having it fixed rather than configurable means changing it means leaving this image.
The clock advice blames the power supply, not the firmware
The performance guidance is unusually specific and unusually blunt. The R2C and R2S run at a core frequency of 1.6, and on those two boards the LAN and WAN ports are swapped relative to what you would expect. The R4S runs at 2.2 or 1.8 depending on configuration.
For the R4S the documentation recommends a power supply with wire loss compensation, and then states that most crashes are caused by the power supply being poor. It offers an alternative in the bundled app, which can cap the maximum frequency.
Both halves are useful. A board that reboots under load because of voltage droop is a hardware problem that no firmware change fixes, and the author saying so plainly saves a lot of time. The frequency cap is the software-side mitigation, and shipping it in the image rather than leaving it to a manual sysfs write is the kind of convenience that makes a community build usable.
The swapped ports on the R2C and R2S are the other thing to check before first boot, since a wrong assumption there looks like a dead cable.
The download link points at a different repository
The documentation's download section tells you to pick the firmware for your device and then links to the releases of a different repository under the same owner, not to this one. So the artifacts are published somewhere else from the source you are reading, and anyone automating a build or a mirror has to know that.
This repository's own releases are named after the OpenWrt point release they carry, for example a release titled for 25.12.5, and the three most recent are 25.12.3 in May 2026, 25.12.4 in the same month, and 25.12.5 in July. The branch was last pushed on 2026-09-04.
The tree explains what kind of repository this is. There are eight top-level entries: a GitHub directory, the licence, the readme, and four directories named in capitals, `PATCH`, `SEED`, `SWITCH`, and `SCRIPTS`. One of those is misspelled, with the scripts directory spelled SCRIPTS. There is no build script, no makefile, and no configuration at the root, so what you are looking at is a set of overlay fragments rather than a firmware build tree.
The acknowledgements table at the end credits around twenty upstream projects and individuals, and several of its rows are empty, which suggests the table was assembled by hand rather than generated.
Editorial conclusion
YAOF suits someone who has one of the four named boards, wants a router image with a proxy stack and ad filtering already configured, and is comfortable with a Chinese-language feature list and an ssh-based support path. It does not suit someone who needs Docker in the current build, since the project points those users at the older 23.05 series instead, and it does not suit a commercial deployment given the non-commercial statement sitting next to a GPL-3.0 licence. Before you flash it, settle three things: whether your board is one of the four targets, whether you have written authorization for the DNS and traffic routing the bundled plugins perform, and what you intend to do about the licence conflict, because GPL-3.0 and a non-commercial notice are not the same grant.
Frequently asked questions
What is QiuSimons/YAOF?
An OpenWrt based router firmware built for the Nanopi R2C, R2S and R4S boards and for x86 hardware, compiled from native OpenWrt 25.12 with O2 optimisation and a default management address of 192.168.1.1. It bundles proxy clients, ad filtering, DNS routing and traffic tools, is licensed GPL-3.0, and its documentation is written in Chinese and asks that it not be used for commercial purposes.
Does the YAOF firmware still include Docker?
Not by default. The documentation says the current build no longer integrates Docker and that anyone who needs it should stay on the 23.05 series. It also says that to use Docker you must first enable the auto-start option in the Docker configuration panel and save the application settings, and that a bundled one-click plugin formats and mounts the remaining space on the device for Docker users.
Where do I download the YAOF firmware image?
From the releases of a different repository under the same owner, R2S-R4S-OpenWrt, which is where the documentation's download link points. This repository's own releases are titled after the OpenWrt point release they carry, with 25.12.5 being the most recent, dated 2026-07-10. Pick the image that matches your board rather than a generic build.
What should I try first when the YAOF firmware misbehaves?
The project's own first suggestion is to ssh into the device, type fuck, press enter, wait for it to reboot, and then check whether the problem is resolved. That is a factory reset offered as step one, so treat it as destructive and back up any configuration you cannot rebuild before trying it.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/qiusimons-yaof)Star history chart for your README
[](https://hysenlabs.com/projects/qiusimons-yaof)Was this useful?