v3.2.2 — one Wireless Settings tab replaces General and Professional, Warden's counters add up
- One Wireless › Settings tab replaces the General and Professional tabs. Every radio setting a
user can change is on one page, a column per band, applied once with one wireless restart. Network
name, security, Wi-Fi 6 and 7 mode and Smart Connect stay on the Network menu, where the SDN
profile owns them. The channel and bandwidth rows offer what the driver reports for each band (new
httpd hookwlpro_chanspecs) and fold intowl<unit>_chanspecexactly as the General tab did;
the wireless scheduler edits a 7×24 grid and writes the V2 off-time rules the watchdog reads on
this build. The stock General and Professional pages and the retired Reaper page redirect here. A
value a rule forces (WMM on outside Legacy, MU-MIMO from OFDMA, TX bursting off under pre-emptive
Bluetooth, beamforming under MU-MIMO, scheduler off under MLO) is written at apply as a derived
heal when nvram disagrees, as the Wi-Fi 6 heal already was. Long option lists no longer close when
their scrollbar is used. The v3.2.1 Wireless Mode row and its Wi-Fi 6 coupling carry over
unchanged. - The seven rows removed in v3.2.0 are back, locked only where stock locks them. WMM, MU-MIMO,
explicit and universal beamforming, modulation scheme, AMPDU aggregation and Bluetooth coexistence
are on the Settings tab per band; Legacy mode parks what stock parks, WMM is a choice in Legacy
only, MU-MIMO follows the OFDMA choice, Fragmentation Threshold is editable in Legacy only. Greyed
is the only signal. Behaviour change: this supersedes the v3.2.0 removal note. - The radio toggle is linked to the tabs that also drive it. A radio cannot be switched off
while MLO is enabled, and the scheduler is greyed while MLO holds every radio on; the MLO tab
forces every radio on, and stock refuses the same way. Applying a radio-off in router or AP mode
confirms first, because the setting reaches AiMesh nodes. AMPDU RTS set to Disable greys and parks
that radio's RTS threshold. - Warden's counters add up. The checkpoint and statistics scripts read the total and the
country, threat and manual buckets from separateiptableslistings, so a packet arriving between
the reads was banked in a bucket but not in the total and then zeroed: the durable store drifted a
few packets per 15-minute checkpoint, forever, with Unclassified clamped at zero. Both now take
one whole-table listing per stack and parse every figure from it. The stat reads Blocked
packets, and a card under "How Warden works" says what the number is: packets, not attempts, and
never equal to the 400-line log view, which is gated on logging. - Traffic, QoS and QoS Diag say Download and Upload in every language. The three pages reused
the stock file-upload button token as a legend label, and in Russian that verb is the same word as
the stock "Download" label, so the legend read one word twice (field report). New noun tokens,
seeded from the speed-test labels, with the Russian corrected. - Dictionaries. 35 tokens added and two retired in all 25 packs (lockstep 7019); 33 of the new
ones (the Settings row texts and the Warden card) are English-seeded in the 24 non-English packs,
owed to the next translation pass.
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
_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-BE19000_3006_102.8_Reaper_v3.2.2_BETA_nand_squashfs.pkgtb
| 4a9458bd3f53f9515ef9a3af796523bc962e9867197d702bbe51c95f02e062a3
|
| Standard | GT-BE19000_3006_102.8_Reaper_v3.2.2_BETA_noMCP_nand_squashfs.pkgtb
| 77c527b6c1ab3f5913b590bb165fa1f85deaa2b5649eff7898bd99c685536265
|
Verify a download against the attached SHA256SUMS-GT-BE19000-Reaper_v3.2.2.txt.
Corresponding source & reproducibility
The GT-BE19000 image for v3.2.2-beta is built from this repository at tag v3.2.2-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.
- 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.2.2-beta-GT-BE19000 (patches + docs).