TheUnboundDeveloper/AM-Reaper v3.6.3-beta-RT-BE96U

Reaper v3.6.3-beta — RT-BE96U

on GitHub

v3.6.3 — Wireless Log names and network types, hardware QoS behind an ISP profile, unsaved-changes cue, the speed test on 3006.102.8

Everything in v3.6.2 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. Two are for the 3006.102.8 models only: the speed
test setup (the 3006.102.10 models have had it since v3.6.0) and the Wi-Fi start-up script.

• Wireless Log: your device names, and each network for what it is. Field report (GT-BE98, v3.6.2): names were
  missing and a main + guest + IoT router read as two guest networks. The page printed only the DHCP lease hostname
  (* when a device sends none); it now shows your name for the device first (Devices page, then the client list),
  the lease hostname after. Each box other than the main network carries its Guest Network Pro type (Guest, IoT,
  Kids, VPN ...). On a router whose main network is still on the primary interface (no MAINFH profile) the main
  network is found there instead of being filed under the AiMesh backhaul.
• Hardware QoS shapes the port under an ISP / IPTV profile. With switch_wantag and an STB port or a WAN VLAN
  tag, wan0_ifname is the profile's vlanNNN / brvNNN device, which the traffic manager refuses, so hardware QoS
  shaped nothing. hwqos_tm_ifname() now takes the physical port there (wan_if_eth(), as Asuswrt-Merlin's HW AQM
  does since Eric "Merlin" Sauvageau's f5334a33d23); a port that also carries the LAN is still refused.
  reaper_diag v1.3.52 section 10 names the same port. The QoS page's "LAN trunk" note shows only for the GT-BE98
  family's vlan4094 jack, not for every VLAN WAN.
• Internet Connection names the WAN port in use. Field report (RT-BE88U, v3.6.1): with the cable on the 2.5G port
  the page said "10G WAN/LAN"; it named the model's default port. It resolves the port the way WAN Ports does.
• WAN Ports tab in router mode. Same report: the tab was missing because wlc_band held -1; any value hid it. In
  router mode the dual-WAN flag alone decides; WISP, repeater, media bridge and AP keep the stock rule.
• System Info: an off radio reads "off". Field report (GT-BE98, v3.6.1): it showed the markup <i>off</i> as text.
• "Unsaved changes" on the pages that keep edits until Apply or Save. QoS, Policy Routing, WAN Ports, Wallguard and
  Dreadwatch show "Unsaved changes: N" and a Discard button, as the other Reaper pages do: a QoS rule's × had edited
  only the page with nothing saying Apply was still needed.
• DNS Director: pick the device from a list. A picker of connected devices sits beside the MAC box and fills it;
  typing a MAC still works. Offline devices and devices that already have a rule are left out.
• Dreadwatch names itself. Its apply message and how-it-works card said Warden; they now say Dreadwatch, in all 25
  languages.
• Speed test (3006.102.8 models): ASUS's 102_40585 setup. ASUS retired the Ookla key this line used on 2026-10-01.
  GT-BE98, GT-BE19000, BQ16 and BQ16 Pro get the files the 3006.102.10 models have had since v3.6.0 (Asuswrt-Merlin,
  Eric "Merlin" Sauvageau, 0c5d53820c7): the key chosen by platform, ASUS's quota (100 free tests, then 3 per 24
  hours, once setup is complete; the page says when it is used up) and the engine build 40585 pairs with it.
• Wi-Fi start-up script (3006.102.8 models): the defaults volume is mounted once. hndnvram.sh mounted it again on
  every call, stacking mounts. The models' platform trees predate the fix (Asuswrt-Merlin, Eric "Merlin" Sauvageau,
  d7c6a53e440, from GPL 102_40585); the build now swaps in that script, and only over the known older copy.
• Smaller fixes: VPN Director's client list gives each client a card with its tags on their own line; Wireless
  Settings' band dot is the radio's state, green on and grey off, as on the dashboard; Wallguard and Dreadwatch "Add
  a source" folds Request and the key header away for a plain list and styles the API key field; LAN > VLAN reads
  "In use by Ethernet WAN"; three images are recompressed losslessly (71 KB); the release workflow retries a failed
  artifact download and refuses to publish a partial one.

Images & checksums (RT-BE96U)

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 _BETA and 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.

Verify a download against the attached SHA256SUMS-RT-BE96U-Reaper_v3.6.3.txt.

Corresponding source & reproducibility

The RT-BE96U image for v3.6.3-beta is built from this repository at tag v3.6.3-beta-RT-BE96U: 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.md and docs/SOURCE-AVAILABILITY.md

The auto-attached Source code (zip/tar.gz) asset below is this repository at tag v3.6.3-beta-RT-BE96U (patches + docs).