github TheUnboundDeveloper/AM-Reaper v3.2.0-beta-GT-BE19000
Reaper v3.2.0-beta — GT-BE19000

pre-release8 hours ago

v3.2.0 — the Professional page keeps to its own settings, and a bridging box says why Traffic is empty

  • WiFi Professional drops the WiFi 7 Mode and Wireless Mode rows. Both wrote a per-radio key
    (wl<unit>_11be, wl<unit>_nmode_x) through the page's generic apply with none of the SAE and
    Smart Connect coupling the stock surfaces enforce, so 11be could be raised on a band whose crypto
    cannot advertise EHT, and "N only" set 11ax=0 at bringup, which drops HE and with it EHT. A
    GT-BE98 report on 2026-09-18 was exactly that: 2.4 GHz beaconing HT only, so the phone correctly
    showed no Wi-Fi 6 or 7 badge on that band. Wi-Fi 7 is chosen per network on the Network menu.
    Behaviour change: Wireless Mode is no longer exposed anywhere in the Reaper interface. A band
    left on "N only" recovers with nvram set wl<unit>_nmode_x=0; nvram commit; service restart_wireless, where the 2.4 GHz unit is wl0 on every model except the quad-band GT-BE98
    and GT-BE98 Pro, where it is wl3 (nvram get wl<unit>_nband answers 2 for 2.4 GHz). Four
    dictionary tokens retired from all 25 packs.
  • Traffic Analyzer says why it is empty in a bridging mode. rtrafd accounts from the
    connection tracking table, which an Access Point, repeater or media bridge never populates, so the
    collector is deliberately idle there and the page was blank. It now shows a note naming the
    operation mode; routing mode is unchanged.
  • Two help buttons reach the guide again. The Storage and Analytics ? buttons linked a guide
    heading renamed on 2026-08-29, and the Failover button on v3.1.1 images links one renamed in
    v3.1.2; GitHub opens the top of the page for an unknown anchor. The two page links now name the
    live heading, and the guide carries anchors for both old slugs so images already in the field
    resolve too.
  • Reminder from v3.1.9: Policy Routing is first-match-wins. The first rule to match a packet
    decides and nothing below it can overturn that. A list tuned to the old last-match order routes
    differently; put specific rules above broad ones.

Images & checksums (GT-BE19000)

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.

Variant File SHA-256
+ AI Advisor GT-BE19000_3006_102.8_Reaper_v3.2.0_BETA_nand_squashfs.pkgtb e6b790455a7d94fac46ae6bcaca5d33a691dc130fb9f176611a59d1195845a78
Standard GT-BE19000_3006_102.8_Reaper_v3.2.0_BETA_noMCP_nand_squashfs.pkgtb 0a43f38dd9bc1790f6038d51c0481e6eb7681ebbd3de68abc7d5e617e7d66551

Verify a download against the attached SHA256SUMS-GT-BE19000-Reaper_v3.2.0.txt.


Corresponding source & reproducibility

The GT-BE19000 image for v3.2.0-beta is built from this repository at tag v3.2.0-beta-GT-BE19000: the pinned Asuswrt-Merlin base (3006.102.8-beta2, a7ebfa133a) plus the complete patch series. The tag freezes the exact source that produced it.

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

Don't miss a new AM-Reaper release

NewReleases is sending notifications on new releases.