|
| 1 | +Gluon 2025.1.2 |
| 2 | +============== |
| 3 | + |
| 4 | +Important notes |
| 5 | +--------------- |
| 6 | + |
| 7 | +The OpenWrt Base of Gluon has been updated to the latest version of openwrt-24.10 |
| 8 | +introducing various security related bugfixes. |
| 9 | + |
| 10 | +Added hardware support |
| 11 | +---------------------- |
| 12 | + |
| 13 | +ipq806x-generic |
| 14 | +~~~~~~~~~~~~~~~ |
| 15 | + |
| 16 | +- Extreme Networks |
| 17 | + |
| 18 | + - WS-AP3935i |
| 19 | + |
| 20 | +Bugfixes |
| 21 | +-------- |
| 22 | + |
| 23 | +.. _#3797: https://github.com/freifunk-gluon/gluon/pull/3797 |
| 24 | +.. _#3802: https://github.com/freifunk-gluon/gluon/pull/3802 |
| 25 | + |
| 26 | +- Fix wireless htmode selection on devices with channel widths smaller than the site configuration (`#3797`_) |
| 27 | +- Fix wireless bandwidth selection logic sometimes prioritizing lower rates (`#3797`_) |
| 28 | +- Adapt sysctl parameters for 64M RAM devices to improve performance and stability (`#3802`_) |
| 29 | + |
| 30 | +Known issues |
| 31 | +------------ |
| 32 | + |
| 33 | +.. _#94: https://github.com/freifunk-gluon/gluon/issues/94 |
| 34 | +.. _#496: https://github.com/freifunk-gluon/gluon/issues/496 |
| 35 | +.. _#1726: https://github.com/freifunk-gluon/gluon/issues/1726 |
| 36 | +.. _#1728: https://github.com/freifunk-gluon/gluon/issues/1728 |
| 37 | + |
| 38 | +- The integration of the BATMAN_V routing algorithm is incomplete. |
| 39 | + |
| 40 | + - Mesh neighbors don't appear on the status page (`#1726`_) |
| 41 | + |
| 42 | + Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new |
| 43 | + throughput metric. |
| 44 | + - Throughput values are not correctly acquired for different interface types (`#1728`_) |
| 45 | + |
| 46 | + This affects virtual interface types like bridges and VXLAN. |
| 47 | + |
| 48 | +- Default TX power on many Ubiquiti devices is too high, correct offsets are unknown (`#94`_) |
| 49 | + |
| 50 | + Reducing the TX power in the Advanced Settings is recommended. |
| 51 | + |
| 52 | +- In configurations without VXLAN, the MAC address of the WAN interface is modified even when |
| 53 | + Mesh-on-WAN is disabled (`#496`_) |
| 54 | + |
| 55 | + This may lead to issues in environments where a fixed MAC address is expected (like VMware when |
| 56 | + promiscuous mode is disallowed). |
0 commit comments