bb-qq/r8152: a Synology DSM driver package for Realtek USB Ethernet adapters

What bb-qq/r8152 solves for Synology owners

Synology NAS units ship with fixed Ethernet ports, usually 1GbE on consumer and small business models. If you want 2.5GbE or faster without replacing the NAS, a USB Ethernet dongle is the cheap route, but DSM does not bundle the Realtek r8152 driver for every kernel it ships. The repository exists to close that gap: it builds the Realtek USB Ethernet driver as a Synology package (SPK) that installs into DSM's package system rather than requiring you to rebuild a kernel module by hand.

The scope is deliberately narrow. The readme lists RTL8152 and RTL8153 at 1.0Gbps, RTL8156 at 2.5Gbps, RTL8157 at 5Gbps and RTL8159 at 10Gbps. The audience is Synology owners on DSM 7.x or 6.2, with the readme claiming support for "almost all models released after 2017" and warning that older models "may also work, but you might not experience optimal performance." If you run Linux on a generic x86 box, this project is not aimed at you; the in-tree r8152 driver already covers that case.

How the driver package is built and loaded

The repository is a C source tree wrapped in Synology's package build conventions. The top level holds r8152.c, compatibility.h, spk_su.c, a Makefile, two udev rule files (50-usb-realtek-net.rules and 51-usb-r8152-net.rules), a SynoBuildConf/ directory and a conf/ directory. The Makefile builds two artifacts: the kernel object r8152.ko and a small helper binary called spk_su. The module target invokes the kernel build system with $(MAKE) -C $(KSRC) M=$(PWD) modules, which is the standard out-of-tree module pattern.

The interesting part is spk_su. Synology's package framework runs install scripts with restricted privileges, but loading a kernel module needs root. The readme's install steps create a setuid copy of spk_su at /opt/sbin/spk_su with mode 4755 and owner root, then retry the package install. That helper is what lets the package's scripts do privileged work. It also explains the readme's blunt warning that the driver "works with root privileges" and that builds obtained from other websites should not be used, since a repackaged setuid helper is an obvious place to hide something. The two udev rule files are the other moving part: they tell the system how to name and treat Realtek USB network devices when they are plugged in.

Installing the SPK and confirming the adapter comes up

The readme assumes you already have SSH enabled on the NAS. Installation happens through Package Center, not the shell. Download the SPK matching your NAS model and CPU from the release page, then use Manual Install.

The first attempt is expected to fail. That is documented behavior, not a bug in your download. After the failure, log in over SSH and run the two commands the readme gives:

sudo install -m 4755 -o root -D /var/packages/r8152/target/r8152/spk_su /opt/sbin/spk_su
sudo chmod a+rx /opt /opt/sbin

The first command copies the helper out of the package's staging directory and sets the setuid bit; the second makes /opt and /opt/sbin traversable. Then retry the install in Package Center. The readme notes you do not need to repeat these steps next time unless /opt/sbin/spk_su is deleted, for example when repairing the system partition.

After the package installs, plug the adapter in and check that DSM sees a new interface. The readme recommends the front USB ports, because "some users have reported stability issues when using rear ports." If the adapter does not appear, the readme points at the Troubleshooting wiki page and asks for the output of `lsusb` when filing an issue.

Where this driver package falls short

The 5Gbps RTL8157 support carries two documented defects. The readme states plainly that "link speeds are not reported correctly" for RTL8157-based devices, and that enabling Jumbo Frame requires the beta release driver 2.18.1-2 rather than the current stable package. If you need accurate link-speed reporting in DSM's UI or monitoring, that is a real reason to wait.

The 10Gbps RTL8159 entry comes with a platform caveat: USB 3.2 Gen2 support exists "only on a limited number of Synology platforms, so you may not be able to utilize it on most models." Buying a 10Gbps dongle does not mean you get 10Gbps.

Cabling is another constraint the readme is explicit about. Type-C adapters need a Type-A conversion, and the readme recommends a USB 3.2 Gen2 10Gbps cable even though a 5Gbps cable is sufficient for the driver to work. Physical port choice matters too, as noted above. None of these are software bugs, but they all sit between you and a working link, and none of them are handled by the package itself.

bb-qq/r8152 compared with the in-kernel r8152 driver

On mainstream Linux distributions, r8152 is already in the kernel tree, so a Realtek USB dongle usually works the moment you plug it in. That is the alternative, and the difference is packaging and kernel version, not driver logic. A Synology NAS runs a vendor kernel that may not have the module enabled, may be older than the adapter, or may not expose module loading to the user at all. The in-tree driver gives you nothing in that situation because you cannot easily rebuild the vendor kernel.

bb-qq/r8152 takes the opposite approach: it takes the Realtek source, compiles it against Synology's kernel headers through SynoBuildConf, and ships the result as a package DSM can install and uninstall. The cost is that the package is tied to specific DSM versions and CPU architectures, which is why the release page lists many packages per version. The benefit is that you do not touch the kernel. If your distribution's kernel already handles your adapter, this project adds nothing.

Maintenance cadence, licensing and upgrade cost

The last push was on 2026-08-11, and the most recent release is 2.22.1-1 from the same day. Before that, 2.21.4-1 landed on 2026-02-06 and 2.20.1-1 on 2025-06-21. That is roughly two to three releases a year, which fits a driver package that follows Realtek source drops and DSM kernel changes rather than a fast-moving application.

The licence is GPL-2.0, which is consistent with a Linux kernel module; if you redistribute a modified build, the GPL obligations attach to the source you ship. That is a statement about the licence file, not legal advice.

Upgrade cost is low but not zero. The readme says the DSM 7-specific setuid steps are a one-time operation unless /opt/sbin/spk_su disappears, for instance during a system partition repair. A DSM major upgrade can invalidate that, so treat the two SSH commands as something you may need to repeat. Because the package installs a kernel module, a DSM update that changes the kernel ABI is the main scenario where you would need a new SPK build rather than just reinstalling the old one.

Editorial conclusion

Adopt bb-qq/r8152 if you own a Synology NAS from roughly 2017 or later and a Realtek-based USB Ethernet adapter, and you are willing to install a package through Package Center plus two SSH commands. Do not adopt it on a model where the release page has no matching package, or if you expect the driver to appear as a normal DSM network interface without a reboot. Verify first that your exact adapter appears on the Compatibility wiki page, that your CPU architecture matches the package name, and that your /opt/sbin/spk_su exists after the first install attempt.

Frequently asked questions

Official sources

1. bb-qq/r8152 on GitHub
2. Issues
3. License: GPL-2.0
4. README
5. Releases