Skip to content

v0.6.0-alpha4-pre17

Choose a tag to compare

@github-actions github-actions released this 25 Sep 00:19
· 52 commits to master since this release
9d5413c

What's in this release

tollgate-wrt 0.6.0_alpha4_pre17 for OpenWrt, all arches, in both package formats.

This cut fixes a packaging defect found on hardware: through pre16 the feed's install recipe enumerated the module's etc/nftables.d/ files by hand, so 31-admin-board-not-guest-reachable.nft (the nftables half of the :8090 admin-board fix, module PR openwrt#566) was silently dropped from the published package. The recipe now stages the whole directory by wildcard, and a new both-directions parity guard compares the pinned module tarball's file set against what the recipe stages, failing on a missing or extra file.

Hardware compatibility

  • GL-MT3000 (MT7981, mediatek-filogic / aarch64_cortex-a53) — verified on OpenWrt 25.12.5 against this release's aarch64_cortex-a53 artifact.
  • Comfast AX3000 CF-WR632AX (MT7981B, same target/arch) — expected-compatible, not yet hardware-verified. Use the plain comfast_cf-wr632ax images; the -ubootmod variant needs preloader.bin + bl31-uboot.fip written through U-Boot/TFTP and is not a sysupgrade.
  • Other MT7981-family routers: untested. Same target/arch means the package will install, which is not the same as having been exercised.

Which file to use

  • OpenWrt 25.x (apk): tollgate-wrt_0.6.0_alpha4_pre17_<arch>.apk
  • OpenWrt 24.10 and earlier (opkg): tollgate-wrt_0.6.0_alpha4_pre17_<arch>.ipk
  • The .ipk and .apk of one release are built by different SDK lanes, so they are separate builds, not byte-identical. The .ipk is not installable on OpenWrt 25.x (apk-tools: v2 package format error) — use the .apk there.
  • Verify what you downloaded against the signed SHA256SUMS.

Verified a router yourself?

Open an issue on the module repo (OpenTollGate/tollgate-module-basic-go) with: router model and SoC, the exact OpenWrt version, which install path you used (package or installer), the artifact filename, tollgate version output, sha256sum /usr/bin/tollgate-wrt, and what worked or did not. A one-command evidence collector and a hardware matrix are being added; until they land, pasting those facts in an issue is enough for us to record the result.