Gluon 2025.1.1

Added hardware support

ath79-generic

  • Ubiquiti

    • Rocket M2/M5 (XM) [1]

ipq40xx-generic

  • ASUS

    • Lyra MAP-AC2200

mediatek-filogic

  • Cudy

    • RE3000 (v1)

    • M3000 (v1)

    • WR3000s

    • WR3000h (v1)

  • Mercusys

    • MR90X (v1)

ramips-mt7621

  • Totolink

    • X5000R

  • Xiaomi

    • Mi Router AC2100

    • Redmi Router AC2100

ramips-mt7622

  • Ubiquiti

    • UniFi 6 LR (v2, v3)

  • Xiaomi

    • AX3200 / Redmi AX6S [1]

qualcommax-ipq807x

  • Linksys

    • MX5300

New Features

Configuration of channel_width per band in site configuration (#3659)

The default channel width can be set in the site configuration. This uses the highest MCS (HT/VHT/HE/…) available and combines it with the selected channel width in MHz. The following example increases the width to 40MHz for all 5GHz radios.

wifi5 = {
  channel_width = 40,
  ...
}

Additional information on status page (#3654)

Add more information to the status page, including:

  • number of cores (nproc) of the device

  • base version

  • firmware target

  • currently active ssid

  • configured htmode

Bugfixes

  • Fix phy path migration timing on some devices (like WR3000), which led to a broken wifi configuration (#3735)

  • Improve migration for x86 Ethernet driver load order change to also cover typical USB drivers (#3576)

  • Fix hang at sysupgrade when using BATMAN_V (#3705)

Known issues

  • The integration of the BATMAN_V routing algorithm is incomplete.

    • Mesh neighbors don’t appear on the status page (#1726)

      Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput metric.

    • Throughput values are not correctly acquired for different interface types (#1728)

      This affects virtual interface types like bridges and VXLAN.

  • Default TX power on many Ubiquiti devices is too high, correct offsets are unknown (#94)

    Reducing the TX power in the Advanced Settings is recommended.

  • In configurations without VXLAN, the MAC address of the WAN interface is modified even when Mesh-on-WAN is disabled (#496)

    This may lead to issues in environments where a fixed MAC address is expected (like VMware when promiscuous mode is disallowed).