Repository navigation
Reaper v3.8.1-alpha — BQ16
Pre-releasev3.8.1 — Device names reach every page; names keep their spaces; Wi-Fi restarts no longer stall the 5 and 6 GHz radios; guest network links, SNMP and VPN fixes
Everything in v3.8.0 is included. Both lines carry the same changes: RT-BE96U, RT-BE86U, RT-BE88U and GT-BE98 Pro on
3006.102.10; GT-BE98, GT-BE19000, BQ16 and BQ16 Pro on 3006.102.8.
- Device names on every page. The Name / Hostname list introduced in v3.8.0 never reached the pages: the request
for it was cut short by the web server. Pages showed only the names set on the Devices page, and the dashboard
Clients card showed MAC addresses. The request is fixed, and the dashboard card uses the same name helper as every
other page. - Names with spaces. A setting saved from some pages was stored with a plus sign for each space: a network name
set as MLO Fronthaul becameMy+Wifi+Network. Spaces are kept now. A name already stored with plus signs is not
rewritten: enter it again. - Wi-Fi restarts and the 5 / 6 GHz radios. Several Network-page saves in quick succession could leave the 5 GHz
and 6 GHz radios down until a reboot. The pause the router takes before a Wi-Fi restart could end early; it now
always runs its full time. - Guest networks linked by Access Intranet. Two guest networks linked to each other were also let onto the main
network: the router's pages, the main network's device names and mDNS. A link between two guest networks now joins
only those two; only a link with the main network gives main-network access. What changes for you: guest
networks you linked to each other lose the router's pages and main-network names, and a Guest Portal linked only to
another guest network loses main-network access. - SNMP. The SNMP user could change everything the agent exposes. It can now set only the contact, name and
location, and nothing at all while Allow access from WAN is on. That switch now works (the agent did not listen
on the WAN address before). SNMP and its WAN access stay off unless you turn them on. - OpenVPN Killswitch. With Redirect Internet traffic set to No, or on a TAP client, a Killswitch stored
earlier still closed the traffic of Policy Routing devices, although the page hides the switch there. It now applies
only when the client carries all traffic or is in VPN Director mode. VPN Director and Policy Routing show the real
state of a client (off, not in VPN Director mode, pushed routes only, TAP), and the warnings no longer say that a
switched-off client blocks traffic: that traffic uses the WAN. - WireGuard server. A new peer gets an address in both families, and an IPv6 default route only when it has an
IPv6 address. A port that another VPN server on the router already uses is refused. A server that could not start
is logged. - OpenVPN server page. The live status of both servers updates again (only the first value was being read).
- Wake on LAN. The wake packet was sent on the main network only; a device on a guest or VLAN network is now
woken on its own network. - IPv6. The WAN Prefix Length for Native with prefix delegation is checked (empty, 0 or 48 to 64), and the page
says that guest networks need a /56 or larger from the provider. - Access Restrictions. The page says that IPv6 access to the web interface and SSH is blocked while the list is
on, and asks first when you are connected over IPv6. - MLO. Switching MLO off keeps every band of the main network.
- Auto refresh. The Auto refresh switches on Firewall Status and Rule Status, and the box on the System Log, keep
your choice per browser. - Tweaks. The connection limit help says that its default is the maximum.
- GT-BE98, this test line only. The GT-BE98's Wi-Fi driver, data-plane and router components are now the ASUS
GPL 102_40585 set, the level this tree is built on (thanks to gnuton, whose Asuswrt-Merlin tree published them),
so the model no longer needs the compatibility layer for older components. Its boot loader is unchanged: flash
the normal image, not the loader one. Reports from GT-BE98 owners are wanted: WAN on the 10G and the 2.5G port,
AiMesh nodes, 6 GHz and MLO clients.
Images & checksums (BQ16)
Two flashable images: + AI Advisor (default) and Standard (noMCP, all AI components compiled out entirely). Flash the *_nand_squashfs.pkgtb via Administration > Firmware Upgrade.
This is an ALPHA test build from the
Dev-Unibranch: every model built from one source tree (3006.102.10). Its filename carries_ALPHAand the router reports the same string on the dashboard and the About page. It is not listed in the update manifest, no router is offered it, and a router running it does not look for updates: install the next test build by hand from this page. To leave the test, flash a beta or stable release for your model.
| Variant | File | SHA-256 |
|---|---|---|
| + AI Advisor | BQ16_3006_102.10_Reaper_v3.8.1_ALPHA_nand_squashfs.pkgtb |
61c6084174b2a8f975028dfe6d888cb8c8c5d1246b2f3476efd0c7a841774ecc |
| Standard | BQ16_3006_102.10_Reaper_v3.8.1_ALPHA_noMCP_nand_squashfs.pkgtb |
d6293f622c023446f5b4ffbf3d006b94b553134500997e1c249ee4b296561874 |
Verify a download against the attached SHA256SUMS-BQ16-Reaper_v3.8.1.txt.
Corresponding source & reproducibility
The BQ16 image for v3.8.1-alpha is built from this repository at tag v3.8.1-alpha-BQ16: the pinned Asuswrt-Merlin base (3006.102.10, ca72a61f8bc) plus the complete patch series. The tag freezes the exact source that produced it.
- Patches:
patches/ - Provenance record:
provenance/manifest.json - How to verify:
docs/REPRODUCIBILITY.mdanddocs/SOURCE-AVAILABILITY.md
The auto-attached Source code (zip/tar.gz) asset below is this repository at tag v3.8.1-alpha-BQ16 (patches + docs).