v3.8.0 — VPN-routed guest networks reach the internet; the portal passcode on every subnet; DHCP leases kept across a restart; one rule for device names; Wallguard finds the culprit
Everything in v3.7.9 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.
- Guest networks routed into a VPN. A guest network that VPN Director (or an OpenVPN client set to redirect all
traffic) sent into a VPN tunnel had no internet: guest isolation only allowed the WAN or the network's own bound
client. It now follows those rules. Not on a Guest Portal network, and not with the network's Kill Switch on.
Changing VPN Director's rules re-applies it straight away. - Guest Portal passcode on a short subnet. On some portal subnets the router checked the passcode against the
wrong key, so a correct passcode and the terms page were refused. The portal network is now matched properly. - Apple devices on an isolated guest network keep DNS. An isolated guest network was offered the router's
encrypted DNS, which it cannot reach; iPhones take that offer by themselves and then lost DNS. The offer is now
made only where it works. - Login name. The first-setup page no longer forces the login name to lower case; it follows the stock rule.
- Network page. Editing the Default IoT Network no longer resets its LAN ports to All (Default).
- Warden custom feeds with an API key. A feed address may contain
$APIkey. The key goes in its own box, stays
private on the router (not in the list, the page or a settings export) and is used only when the feed is fetched. - DHCP leases survive a restart. The router keeps its lease lists in flash and puts them back when it starts, so
every device that still holds a lease is listed (and named) right after a reboot, not only once it renews. - Device names. One rule on every page: Name is the name you gave the device on the Devices page; Hostname is
what the device sends, else the maker of its network card, elsePrivate-Addressfor a randomized address. A
page with one label shows Name, else Hostname. DHCP Leases shows both columns and lists devices whose address is
set on the device; its Refresh button shows it was pressed. A DHCP reservation's name is the device's DNS name and
is labelled so. - Wallguard finds the culprit. A streaming app that broke under Wallguard (a Paramount+ report) showed nothing
useful on the page. Every block now records the device it came from, so Unbreak finds a device by name; it keeps
an hour of history and leaves out names you have allowed. A name hidden behind a CNAME alias is shown as
"asked name (blocked via listed name)", and allowing the asked name now lifts the block. Lists kept on a USB
store are kept current (they were rejected after a reboot), and a skipped list rebuild is reported on the page. - Wallguard page in tabs. Overview (Fix a device, Pause with a 10-minute choice, Why?), Lists, Rules, Devices
(one row per device with its profile, blocked lookups in the last 15 minutes, Fix and Pause) and Activity. - QoS defaults. On a new or factory-reset router QoS is off (as before), and the HW QoS Classful profile now
starts Web/VoIP at a 90% ceiling instead of 100%. Routers that already have QoS rates keep their own.
Images & checksums (GT-BE98)
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 a beta release. Its filename carries
_BETAand the router reports the same string on the dashboard and the About page, so you can always tell which channel a flashed image came from. Stable releases carry no marker.
| Variant | File | SHA-256 |
|---|---|---|
| + AI Advisor | GT-BE98_3006_102.8_Reaper_v3.8.0_BETA_nand_squashfs.pkgtb
| d8c8fe765de3eef141820be9cbf83f49dda7f81fe826a488af70ff560e582908
|
| Standard | GT-BE98_3006_102.8_Reaper_v3.8.0_BETA_noMCP_nand_squashfs.pkgtb
| 164ad6df3c382fe3ae0ad18c7f9cde304c9c6becdb10fb805cfc911521436f2e
|
Verify a download against the attached SHA256SUMS-GT-BE98-Reaper_v3.8.0.txt.
Corresponding source & reproducibility
The GT-BE98 image for v3.8.0-beta is built from this repository at tag v3.8.0-beta-GT-BE98: the pinned Asuswrt-Merlin base (3006.102.8-beta2, a7ebfa133a) 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.0-beta-GT-BE98 (patches + docs).