Skip to content

Reaper v3.8.3-alpha — RT-BE88U

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Nov 06:46
· 71 commits to main since this release

v3.8.3 — Guest networks can reach chosen main-network devices; AP Isolation keeps wired devices reachable; guest VPN routing after a WAN reconnect

Everything in v3.8.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. Most of this rung answers field reports about
guest networks and about devices that could no longer reach each other on the main network.

  • Guest networks: paths you open on purpose. Guest isolation stays the default; three new controls, all off at
    factory, open narrow paths to the main network. None of them ever opens the router's own pages, SSH or services,
    another guest network, or the WAN while a network's VPN is down, and none is offered on a Guest Portal network.
    • Reach these main-network devices (Network page, a network's General settings): tick up to 16 main-network
      devices that have a DHCP reservation; devices on the guest network can open connections to them, and those
      devices can only answer. AiMesh nodes and the router are never listed. A changed reservation is followed at once.
    • Device discovery with the main network: casting, AirPlay, printer and HomeKit discovery between the main
      network and that network only, never between two guest networks, limited to the service types you pick
      (Printing, AirPlay, Google Cast, HomeKit / Matter, Spotify / Sonos, or your own). The router's own name is not
      announced there, and a guest device cannot take over the name of a main-network device or hide its services.
    • Firewall > Zones: Zone policies may open one-way paths from the main network into isolated guest networks:
      an Accept zone policy from the main network (or a network linked to it) into a guest network now opens that
      path; the guest network only answers. Never guest to guest.
  • AP Isolation: Wi-Fi only, or Wi-Fi and LAN ports. On the 3006.102.10 line, turning AP Isolation on for the main
    network also kept its wired devices apart, so a TV could no longer find a NAS on another port. AP Isolation is now a
    choice on every network: Wi-Fi only (the default; Wi-Fi devices cannot reach each other, wired devices stay
    reachable) or Wi-Fi and LAN ports (the router's LAN ports are kept apart too). The WAN ports, VLAN trunk ports and
    a port with an AiMesh node behind it are never isolated; a network whose VLAN profile sets port isolation keeps it.
    Both lines behave the same. On an AiMesh node the node keeps the firmware's own behaviour.
  • Guest networks bound to a VPN client keep their routing through a WAN reconnect: the router puts the network's VPN
    routing rules back as soon as the WAN routes are rebuilt (before, the network left by the WAN until the VPN client
    restarted, unless its Kill Switch held it). Unbinding a network removes its IPv6 rule into the tunnel.
  • IPv6 for guest and VLAN networks: a delegated prefix of /57 to /63 is now divided too (a /60 has room for 15
    networks; before, anything smaller than /56 left them without public IPv6). New or reset routers ask the provider
    for a /56; an upgraded router keeps its setting. With Static IPv6 the page fills in 64 on such a router.
  • Rule Status 1.16: a zone policy that guest isolation holds back reads Held (amber) with a note naming the
    network, not a failure; new rows check the devices you picked, discovery, and that an opened path stays one way.
  • Guest Portal web server: its unused file-sharing library is replaced by a 5 KB stand-in; about 0.9 MB of flash
    comes back.
  • AiMesh tab: devices connected with MLO show the MLO icon, on the router and on nodes; a node's MLO backhaul list
    reads 2.4 GHz.
  • Phones: a menu's tab bar keeps its size when a page is wider than the screen (Administration > System on an
    iPhone); long values on that page wrap.
  • Test line (alpha) only. The same changes as above on the unify tree. The AP Isolation change matters most for
    the GT-BE98 here: from v3.8.1 its newer components kept wired devices apart while AP Isolation was on (a TV could
    not find a NAS behind the 10G port); with Wi-Fi only, the default, they reach each other again. Reports from
    GT-BE98 and BQ16 Pro owners are still wanted.

Images & checksums (RT-BE88U)

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-Uni branch: every model built from one source tree (3006.102.10). Its filename carries _ALPHA and 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 RT-BE88U_3006_102.10_Reaper_v3.8.3_ALPHA_nand_squashfs.pkgtb 9917abcde52d5468babd013b438adffb8caeaea9a4b0947ae1b06c44b09d3b27
Standard RT-BE88U_3006_102.10_Reaper_v3.8.3_ALPHA_noMCP_nand_squashfs.pkgtb e7f6e92d7ea1ef2d87825988e71015cda76b61b0996c12ce62fbff7079a9b163

Verify a download against the attached SHA256SUMS-RT-BE88U-Reaper_v3.8.3.txt.


Corresponding source & reproducibility

The RT-BE88U image for v3.8.3-alpha is built from this repository at tag v3.8.3-alpha-RT-BE88U: the pinned Asuswrt-Merlin base (3006.102.10, ca72a61f8bc) 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.8.3-alpha-RT-BE88U (patches + docs).