Fixed compatibility problems with websites that use the new Compression Dictionaries technology, such as ChatGPT, by temporarily disabling the feature. (Bug 2010712)
Fixed an issue where an unnecessary empty directory was created on Linux systems. (Bug 2001887)
Fixed an issue where time formats could cause certain websites to display incorrectly. (Bug 2010411)
cli.c: Allow 'channel request hangup' to accept patterns.
The 'channel request hangup' CLI command now accepts
multiple channel names, POSIX Extended Regular Expressions, glob-like
patterns, or a combination of all of them. See the CLI command 'core
show help channel request hangup' for full details.
res_sorcery_memory_cache: Reduce cache lock time for sorcery memory cache populate command
The AMI command sorcery memory cache populate will now
return an error if there is an internal error performing the populate.
The CLI command will display an error in this case as well.
res_geolocation: Fix multiple issues with XML generation.
Geolocation: Two new optional profile parameters have been added.
pidf_element_id which sets the value of the id attribute on the top-level
PIDF-LO device, person or tuple elements.
device_id which sets the content of the <deviceID> element.
Both parameters can include channel variables.
res_pjsip_messaging: Add support for following 3xx redirects
A new pjsip endpoint option follow_redirect_methods was added.
This option is a comma-delimited, case-insensitive list of SIP methods
for which SIP 3XX redirect responses are followed. An alembic upgrade
script has been added for adding this new option to the Asterisk
database.
taskprocessors: Improve logging and add new cli options
New CLI command has been added -
core show taskprocessor name
ccss: Add option to ccss.conf to globally disable it.
A new "enabled" parameter has been added to ccss.conf. It defaults
to "yes" to preserve backwards compatibility but CCSS is rarely used so
setting "enabled = no" in the "general" section can save some unneeded channel
locking operations and log message spam. Disabling ccss will also prevent
the func_callcompletion and chan_dahdi modules from loading.
Makefile: Add module-list-* targets.
Try "make module-list-deprecated" to see what modules
are on their way out the door.
app_mixmonitor: Add 's' (skip) option to delay recording.
This change introduces a new 's()' (skip) option to the MixMonitor
application. Example:
MixMonitor(${UNIQUEID}.wav,s(3))
This skips recording for the first 3 seconds before writing audio to the file.
Existing MixMonitor behavior remains unchanged when the 's' option is not used.
app_queue.c: Only announce to head caller if announce_to_first_user
When announce_to_first_user is false, no announcements are played to the head caller
Upgrade Notes:
res_geolocation: Fix multiple issues with XML generation.
Geolocation: In order to correct bugs in both code and
documentation, the following changes to the parameters for GML geolocation
locations are now in effect:
The documented but unimplemented crs (coordinate reference system) element
has been added to the location_info parameter that indicates whether the 2d
or 3d reference system is to be used. If the crs isn't valid for the shape
specified, an error will be generated. The default depends on the shape
specified.
The Circle, Ellipse and ArcBand shapes MUST use a 2d crs. If crs isn't
specified, it will default to 2d for these shapes.
The Sphere, Ellipsoid and Prism shapes MUST use a 3d crs. If crs isn't
specified, it will default to 3d for these shapes.
The Point and Polygon shapes may use either crs. The default crs is 2d
however so if 3d positions are used, the crs must be explicitly set to 3d.
The geoloc show gml_shape_defs CLI command has been updated to show which
coordinate reference systems are valid for each shape.
The pos3d element has been removed in favor of allowing the pos element
to include altitude if the crs is 3d. The number of values in the pos
element MUST be 2 if the crs is 2d and 3 if the crs is 3d. An error
will be generated for any other combination.
The angle unit-of-measure for shapes that use angles should now be included
in the respective parameter. The default is degrees. There were some
inconsistent references to orientation_uom in some documentation but that
parameter never worked and is now removed. See examples below.
Examples...
The threadpool_* options in pjsip.conf have now
been deprecated though they continue to be read and used.
They have been replaced with taskpool options that give greater
control over the underlying taskpool used for PJSIP. An alembic
upgrade script has been added to add these options to realtime
as well.
app_directed_pickup.c: Change some log messages from NOTICE to VERBOSE.
In an effort to reduce log spam, two normal progress
"pickup attempted" log messages from app_directed_pickup have been changed
from NOTICE to VERBOSE(3). This puts them on par with other normal
dialplan progress messages.
Developer Notes:
ccss: Add option to ccss.conf to globally disable it.
A new API ast_is_cc_enabled() has been added. It should be
used to ensure that CCSS is enabled before making any other ast_cc_* calls.
chan_websocket: Add ability to place a MARK in the media stream.
Apps can now send a MARK_MEDIA command with an optional correlation_id parameter to chan_websocket which will be placed in the
media frame queue. When that frame is dequeued after all intervening media
has been played to the core, chan_websocket will send a MEDIA_MARK_PROCESSED event to the app with the same correlation_id
(if any).
chan_websocket: Add capability for JSON control messages and events.
The chan_websocket plain-text control and event messages are now
deprecated (but remain the default) in favor of JSON formatted messages.
See https://docs.asterisk.org/Configuration/Channel-Drivers/WebSocket for
more information.
A "transport_data" parameter has been added to the
cli.c: Allow 'channel request hangup' to accept patterns.
The 'channel request hangup' CLI command now accepts
multiple channel names, POSIX Extended Regular Expressions, glob-like
patterns, or a combination of all of them. See the CLI command 'core
show help channel request hangup' for full details.
res_sorcery_memory_cache: Reduce cache lock time for sorcery memory cache populate command
The AMI command sorcery memory cache populate will now
return an error if there is an internal error performing the populate.
The CLI command will display an error in this case as well.
res_geolocation: Fix multiple issues with XML generation.
Geolocation: Two new optional profile parameters have been added.
pidf_element_id which sets the value of the id attribute on the top-level
PIDF-LO device, person or tuple elements.
device_id which sets the content of the <deviceID> element.
Both parameters can include channel variables.
res_pjsip_messaging: Add support for following 3xx redirects
A new pjsip endpoint option follow_redirect_methods was added.
This option is a comma-delimited, case-insensitive list of SIP methods
for which SIP 3XX redirect responses are followed. An alembic upgrade
script has been added for adding this new option to the Asterisk
database.
taskprocessors: Improve logging and add new cli options
New CLI command has been added -
core show taskprocessor name
ccss: Add option to ccss.conf to globally disable it.
A new "enabled" parameter has been added to ccss.conf. It defaults
to "yes" to preserve backwards compatibility but CCSS is rarely used so
setting "enabled = no" in the "general" section can save some unneeded channel
locking operations and log message spam. Disabling ccss will also prevent
the func_callcompletion and chan_dahdi modules from loading.
Makefile: Add module-list-* targets.
Try "make module-list-deprecated" to see what modules
are on their way out the door.
app_mixmonitor: Add 's' (skip) option to delay recording.
This change introduces a new 's()' (skip) option to the MixMonitor
application. Example:
MixMonitor(${UNIQUEID}.wav,s(3))
This skips recording for the first 3 seconds before writing audio to the file.
Existing MixMonitor behavior remains unchanged when the 's' option is not used.
app_queue.c: Only announce to head caller if announce_to_first_user
When announce_to_first_user is false, no announcements are played to the head caller
Upgrade Notes:
res_geolocation: Fix multiple issues with XML generation.
Geolocation: In order to correct bugs in both code and
documentation, the following changes to the parameters for GML geolocation
locations are now in effect:
The documented but unimplemented crs (coordinate reference system) element
has been added to the location_info parameter that indicates whether the 2d
or 3d reference system is to be used. If the crs isn't valid for the shape
specified, an error will be generated. The default depends on the shape
specified.
The Circle, Ellipse and ArcBand shapes MUST use a 2d crs. If crs isn't
specified, it will default to 2d for these shapes.
The Sphere, Ellipsoid and Prism shapes MUST use a 3d crs. If crs isn't
specified, it will default to 3d for these shapes.
The Point and Polygon shapes may use either crs. The default crs is 2d
however so if 3d positions are used, the crs must be explicitly set to 3d.
The geoloc show gml_shape_defs CLI command has been updated to show which
coordinate reference systems are valid for each shape.
The pos3d element has been removed in favor of allowing the pos element
to include altitude if the crs is 3d. The number of values in the pos
element MUST be 2 if the crs is 2d and 3 if the crs is 3d. An error
will be generated for any other combination.
The angle unit-of-measure for shapes that use angles should now be included
in the respective parameter. The default is degrees. There were some
inconsistent references to orientation_uom in some documentation but that
parameter never worked and is now removed. See examples below.
Examples...
The threadpool_* options in pjsip.conf have now
been deprecated though they continue to be read and used.
They have been replaced with taskpool options that give greater
control over the underlying taskpool used for PJSIP. An alembic
upgrade script has been added to add these options to realtime
as well.
app_directed_pickup.c: Change some log messages from NOTICE to VERBOSE.
In an effort to reduce log spam, two normal progress
"pickup attempted" log messages from app_directed_pickup have been changed
from NOTICE to VERBOSE(3). This puts them on par with other normal
dialplan progress messages.
Developer Notes:
ccss: Add option to ccss.conf to globally disable it.
A new API ast_is_cc_enabled() has been added. It should be
used to ensure that CCSS is enabled before making any other ast_cc_* calls.
chan_websocket: Add ability to place a MARK in the media stream.
Apps can now send a MARK_MEDIA command with an optional correlation_id parameter to chan_websocket which will be placed in the
media frame queue. When that frame is dequeued after all intervening media
has been played to the core, chan_websocket will send a MEDIA_MARK_PROCESSED event to the app with the same correlation_id
(if any).
chan_websocket: Add capability for JSON control messages and events.
The chan_websocket plain-text control and event messages are now
deprecated (but remain the default) in favor of JSON formatted messages.
See https://docs.asterisk.org/Configuration/Channel-Drivers/WebSocket for
more information.
A "transport_data" parameter has been added to the
cli.c: Allow 'channel request hangup' to accept patterns.
The 'channel request hangup' CLI command now accepts
multiple channel names, POSIX Extended Regular Expressions, glob-like
patterns, or a combination of all of them. See the CLI command 'core
show help channel request hangup' for full details.
res_sorcery_memory_cache: Reduce cache lock time for sorcery memory cache populate command
The AMI command sorcery memory cache populate will now
return an error if there is an internal error performing the populate.
The CLI command will display an error in this case as well.
res_geolocation: Fix multiple issues with XML generation.
Geolocation: Two new optional profile parameters have been added.
pidf_element_id which sets the value of the id attribute on the top-level
PIDF-LO device, person or tuple elements.
device_id which sets the content of the <deviceID> element.
Both parameters can include channel variables.
res_pjsip_messaging: Add support for following 3xx redirects
A new pjsip endpoint option follow_redirect_methods was added.
This option is a comma-delimited, case-insensitive list of SIP methods
for which SIP 3XX redirect responses are followed. An alembic upgrade
script has been added for adding this new option to the Asterisk
database.
taskprocessors: Improve logging and add new cli options
New CLI command has been added -
core show taskprocessor name
ccss: Add option to ccss.conf to globally disable it.
A new "enabled" parameter has been added to ccss.conf. It defaults
to "yes" to preserve backwards compatibility but CCSS is rarely used so
setting "enabled = no" in the "general" section can save some unneeded channel
locking operations and log message spam. Disabling ccss will also prevent
the func_callcompletion and chan_dahdi modules from loading.
Makefile: Add module-list-* targets.
Try "make module-list-deprecated" to see what modules
are on their way out the door.
app_mixmonitor: Add 's' (skip) option to delay recording.
This change introduces a new 's()' (skip) option to the MixMonitor
application. Example:
MixMonitor(${UNIQUEID}.wav,s(3))
This skips recording for the first 3 seconds before writing audio to the file.
Existing MixMonitor behavior remains unchanged when the 's' option is not used.
app_queue.c: Only announce to head caller if announce_to_first_user
When announce_to_first_user is false, no announcements are played to the head caller
Upgrade Notes:
res_geolocation: Fix multiple issues with XML generation.
Geolocation: In order to correct bugs in both code and
documentation, the following changes to the parameters for GML geolocation
locations are now in effect:
The documented but unimplemented crs (coordinate reference system) element
has been added to the location_info parameter that indicates whether the 2d
or 3d reference system is to be used. If the crs isn't valid for the shape
specified, an error will be generated. The default depends on the shape
specified.
The Circle, Ellipse and ArcBand shapes MUST use a 2d crs. If crs isn't
specified, it will default to 2d for these shapes.
The Sphere, Ellipsoid and Prism shapes MUST use a 3d crs. If crs isn't
specified, it will default to 3d for these shapes.
The Point and Polygon shapes may use either crs. The default crs is 2d
however so if 3d positions are used, the crs must be explicitly set to 3d.
The geoloc show gml_shape_defs CLI command has been updated to show which
coordinate reference systems are valid for each shape.
The pos3d element has been removed in favor of allowing the pos element
to include altitude if the crs is 3d. The number of values in the pos
element MUST be 2 if the crs is 2d and 3 if the crs is 3d. An error
will be generated for any other combination.
The angle unit-of-measure for shapes that use angles should now be included
in the respective parameter. The default is degrees. There were some
inconsistent references to orientation_uom in some documentation but that
parameter never worked and is now removed. See examples below.
Examples...
The threadpool_* options in pjsip.conf have now
been deprecated though they continue to be read and used.
They have been replaced with taskpool options that give greater
control over the underlying taskpool used for PJSIP. An alembic
upgrade script has been added to add these options to realtime
as well.
app_directed_pickup.c: Change some log messages from NOTICE to VERBOSE.
In an effort to reduce log spam, two normal progress
"pickup attempted" log messages from app_directed_pickup have been changed
from NOTICE to VERBOSE(3). This puts them on par with other normal
dialplan progress messages.
Developer Notes:
ccss: Add option to ccss.conf to globally disable it.
A new API ast_is_cc_enabled() has been added. It should be
used to ensure that CCSS is enabled before making any other ast_cc_* calls.
chan_websocket: Add ability to place a MARK in the media stream.
Apps can now send a MARK_MEDIA command with an optional correlation_id parameter to chan_websocket which will be placed in the
media frame queue. When that frame is dequeued after all intervening media
has been played to the core, chan_websocket will send a MEDIA_MARK_PROCESSED event to the app with the same correlation_id
(if any).
chan_websocket: Add capability for JSON control messages and events.
The chan_websocket plain-text control and event messages are now
deprecated (but remain the default) in favor of JSON formatted messages.
See https://docs.asterisk.org/Configuration/Channel-Drivers/WebSocket for
more information.
A "transport_data" parameter has been added to the
Added multi-domain support for OAuth/OpenID (#26312)
SSO callback URL generation and redirect validation now includes port matching to ensure redirects target the correct server.
Fixed getAsset returning all file fields instead of only those allowed by the users permissions (#25905) getAsset / GET /assets/:id now respects directus_files permissions when returning file based fields.
@directus/app
Removed the deprecated /webhooks functionality across the stack. This includes the API route and its related tests, (#26311 by @mobml)
controller, and mocks, as well as the corresponding SDK commands and schema types, types and services, system fields and
collections, OpenAPI specifications, and App UI routes and components. This endpoint has been unused for over a year and
has now been fully removed.
Removed the deprecated /webhooks functionality across the stack. This includes the API route and its related tests, (#26311 by @mobml)
controller, and mocks, as well as the corresponding SDK commands and schema types, types and services, system fields and
collections, OpenAPI specifications, and App UI routes and components. This endpoint has been unused for over a year and
has now been fully removed.
Fixed getAsset returning all file fields instead of only those allowed by the users permissions (#25905 by @gaetansenn)
Added a new AI_ENABLED environment variable to allow opting out of our AI chat feature (#26458 by @bryantgillespie)
@directus/system-data
Removed the deprecated /webhooks functionality across the stack. This includes the API route and its related tests, (#26311 by @mobml)
controller, and mocks, as well as the corresponding SDK commands and schema types, types and services, system fields and
collections, OpenAPI specifications, and App UI routes and components. This endpoint has been unused for over a year and
has now been fully removed.
@directus/specs
Removed the deprecated /webhooks functionality across the stack. This includes the API route and its related tests, (#26311 by @mobml)
controller, and mocks, as well as the corresponding SDK commands and schema types, types and services, system fields and
collections, OpenAPI specifications, and App UI routes and components. This endpoint has been unused for over a year and
has now been fully removed.
@directus/types
Removed the deprecated /webhooks functionality across the stack. This includes the API route and its related tests, (#26311 by @mobml)
controller, and mocks, as well as the corresponding SDK commands and schema types, types and services, system fields and
collections, OpenAPI specifications, and App UI routes and components. This endpoint has been unused for over a year and
has now been fully removed.
@directus/sdk
Removed the deprecated /webhooks functionality across the stack. This includes the API route and its related tests, (#26311 by @mobml)
controller, and mocks, as well as the corresponding SDK commands and schema types, types and services, system fields and
collections, OpenAPI specifications, and App UI routes and components. This endpoint has been unused for over a year and
has now been fully removed.
✨ New Features & Improvements
@directus/app
Added a new AI_ENABLED environment variable to allow opting out of our AI chat feature (#26458 by @bryantgillespie)
Added concurrency control for file uploads via a new FILES_MAX_UPLOAD_CONCURRENCY env variable (#26424 by @thomas-svrts)
Added nested validation rules to validation error notice (#26389 by @robluton)
Added Comparison modal wysiwyg diff highlighting (#26301 by @robluton)
Fixed an issue that would cause some drawer header icons from being displayed too large (#26442 by @kekekuli)
@directus/api
Added concurrency control for file uploads via a new FILES_MAX_UPLOAD_CONCURRENCY env variable (#26424 by @thomas-svrts)
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker.
Highlights in OpenWrt 25.12
OpenWrt 25.12.0-rc2 incorporates over 4300 commits since branching the previous OpenWrt 24.10 release and has been under development for over one year.
Only the main changes are listed below. See changelog-25.12.0-rc2 for the full changelog.
General changes
The hardware requirements did not change significantly, most devices supported by OpenWrt 24.10 should also work with OpenWrt 25.12.
Switch package manager from opkg to apk
OpenWrt has transitioned from the traditional opkg package manager to apk (Alpine Package Keeper).
This change brings several advantages:
apk is still maintained, the OpenWrt opkg fork was not maintained any more.
apk supports most features of opkg. Only very few package names changed. The command line arguments of apk are different from the command line arguments of opkg.
For users migrating existing systems, an official opkg to apk cheatsheet is available to ease the transition and map common workflows.
Automatically rebuild firmware images with all currently installed packages
Preserve system configuration during upgrades
This dramatically simplifies upgrades: with just a few clicks in LuCI and a short wait, a custom firmware image is built and installed without manual intervention.
Shell history is preserved
Shell command history is now preserved across sessions by storing it in a RAM-backed filesystem.
Benefits:
Command history is no longer lost between logins
No unnecessary writes to flash storage by default
For users who prefer persistent history storage, this behavior can be changed by editing: /etc/profile.d/busybox-history-file.sh
⚠️ Note: Storing history on flash will increase write cycles and may impact flash endurance over time.
Integration of video feed
The OpenWrt video feed with Qt5 and UI applications is integrated by default.
Wi-Fi scripts in ucode
The wifi scripts were rewritten in ucode.
Target changes
Extend realtek target with support for more switch SoCs like 10G Ethernet switches.
Extend qualcommax target with support for ipq50xx and ipq60xx SoCs.
Added siflower target for Siflower SF21A6826/SF21H8898 SoCs
Added sunxi/arm926ejs subtarget for Allwinner F1C100/200s SoCs
Many new devices added
OpenWrt 25.12 supports over 2180 devices. Support for over 160 new devices was added in addition to the device support by OpenWrt 24.10.
Core components update
Core components have the following versions in 25.12.0-rc1:
Updated toolchain:
musl libc 1.2.5
glibc 2.41
gcc 14.3.0
binutils 2.44
Updated Linux kernel
6.12.63 for all targets
main packages:
cfg80211/mac80211 from kernel 6.18.0
hostapd master snapshot from August 2025
dnsmasq 2.91
dropbear 2025.89
busybox 1.37.0
In addition to the listed applications, many others were also updated.
Upgrading to 25.12
Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts.
Sysupgrade from 23.05 to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed.
Bananapi BPI-R4: Interfaces eth1 was renamed to sfp-lan or lan4 and the interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration.
Scratch installs/upgrades
If you wish to start from scratch (always the safest, but also the most work), simply download the pre-built image from the downloads site or from the Firmware Selector to your device. Make sure to create and save a backup, then install the image using sysupgrade -n /tmp/firmware.bin or the LuCI Backup/Flash Firmware, being sure to set "Keep settings and retain the current configuration" to its off position. Restore or reconstruct your configuration using the contents of the backup as a template.
Attended Sysupgrade options
Attended Sysupgrade (ASU) allows you to build a custom image that retains all of your installed packages and their configuration transparently. You need to use one of the three ASU clients that interface with the ASU server to produce this custom image:
Firmware Selector - an online builder that requires you to manually supply it with the packages you wish to have installed. This package list is sent to the ASU server, and a new custom device image is created containing those packages. You may then download and install the image in LuCI Backup/Flash Firmware, but for this you would enable "Keep settings..."
Luci Attended Sysupgrade - the web interface to the ASU server. This tool allows you to choose a new OpenWrt version, then collects the names of the packages on your device and sends them up to the ASU server. LuCI ASU then downloads the created image directly to your device and allows you to install it, without having to do any of the bookkeeping tasks involved with using the Firmware Selector.
owut - a command line package that does the same job as LuCI ASU, but provides more diagnostics and better visibility into what's happening at the various steps before and during the build process.
Both the LuCI ASU app and owut are optional packages in 24.10, so if you have not installed them, they won't be there by default. Use either the LuCI Package Manager to install them, or you can do it from the command line with opkg:
Note that you can install one or the other, or both together, they are completely independent packages.
Upgrades with Firmware Selector
The Firmware Selector does an excellent job of searching through the thousands of available device configurations and getting you to the right place. But, some devices have several variants and possibly different image formats, so if you're unsure about which one you need or which device you're dealing with or anything else, go to the |Firmware Selector support thread and ask away.
Upgrades with LuCI Attended Sysupgrade
The LuCI web interface should be fairly self explanatory. Since you have fairly limited options there that should be pretty obvious, but if anything is unclear or you're unsure about something, go to the LuCI Attended Sysupgrade support thread and ask.
Upgrades with owut
If you choose to use owut, the fact that it's a command line program means you'll need a little more explanation regarding best practices. In any situation, it's always safe to do a check to see what's going on.
$ owut check --verbose --version-to 25.12
... a lot of output ...
This check should show you all the details of what this upgrade entails with regards to the packages available, and will point out any issues with package versions and so on.
Assuming the results of the check look good, you can simply do an upgrade next.
$ owut upgrade --verbose --version-to 25.12
... even more output ...
If you are unsure of anything you see in the check, during the upgrade, or simply have questions, jump on over to the owut support thread on the forum and ask.
Known issues
Users of Zyxel EX5601-T0 devices need to check their WAN interfaces as port was renamed from eth1 to wan.
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker.
Highlights in OpenWrt 25.12
OpenWrt 25.12.0-rc1 incorporates over 4300 commits since branching the previous OpenWrt 24.10 release and has been under development for over one year.
Only the main changes are listed below. See changelog-25.12.0-rc1 for the full changelog.
General changes
Switch package manager from opkg to apk
Integration of attended Sysupgrade into default LuCI installation
The shell history is stored in RAM till the next reboot
Integration of video feed
Wi-Fi scripts converted to ucode
Target changes
Extend realtek target with support for more switch SoCs like 10G Ethernet switches.
Extend qualcommax target with support for ipq50xx and ipq60xx SoCs.
Added siflower target for Siflower SF21A6826/SF21H8898 SoCs
Added sunxi/arm926ejs subtarget for Allwinner F1C100/200s SoCs
Many new devices added
OpenWrt 25.12 supports over 2180 devices. Support for over 160 new devices was added in addition to the device support by OpenWrt 24.10.
Core components update
Core components have the following versions in 23.05.0-rc1:
Updated toolchain:
musl libc 1.2.5
glibc 2.41
gcc 14.3.0
binutils 2.44
Updated Linux kernel
6.12.62 for all targets
main packages:
cfg80211/mac80211 from kernel 6.18.0
hostapd master snapshot from August 2025
dnsmasq 2.91
dropbear 2025.89
busybox 1.37.0
In addition to the listed applications, many others were also updated.
Upgrading to 25.12
Sysupgrade can be used to upgrade a device from 24.10 to 25.12, and configuration will be preserved in most cases.
:!: Sysupgrade from 23.05 to 25.12 is not officially supported.
ipq806x: migrate wifi configuration when downgrading from
kernel 6.12
mediatek: Cudy AP3000 v1: fix IPv4 address missing on interface
in failsafe mode
mediatek: Cudy WR3000H: fix Ethernet port order
mediatek: Zbtlink ZBT Z8102AX V2: fix ubi size
mpc85xx: p1010: Sophos RED 15w : Fix NAND partitions
mpc85xx: p1010: Watchguard Firebox T10: fix boot
mvebu: GL.iNet GL-MV1000: fix sdhci1 controller
ramips: Improve eMMC and SD Card support
Various fixes and improvements
ath11k: fix transmit queue flushing
dropbear: backport security fixes
dropbear: enable configurable port forwarding options
imagebuilder: fix image generation for some devices
kernel: add support for ESMT F50L1G41LC flash chip (found on recent Cudy boards)
kernel: add support for Fudan Micro FM25S01BI3 flash chip
mwl8k: improve stability of AP mode
odhcpd: fix memory leaks
ppp: add reqprefix, norelease and ac_mac options
Core components update
Linux kernel: update from 6.6.110 to 6.6.119
mac80211: update from 6.12.52 to 6.12.61
mt76: update from 2025-09-15 to 2025-11-06
wireless-regdb: update from 2025.07.10 to 2025.10.07
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This issue will be addressed in an upcoming OpenWrt SNAPSHOT and the OpenWrt 24.10 minor release.
5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the Phicomm K2T, TP-Link Archer C60 v3 and possibly others. For details, see issue #14541.
ramips: Hongdian H7920: Fix pin configuration and MAC addresses
Various fixes and improvements
mac80211: ath10k: improve "failed to flush transmit queue" errors
rockchip: rk3399: Fix PCIe
kernel: ksmbd: Fix SMB access from Linux clients
bcm53xx: Fix bootup of devices
Core components update
Linux kernel: update from 6.6.104 to 6.6.110
mac80211: update from 6.12.44 to 6.12.52
odhcpd: update from 2024-05-08 to 2025-10-02
ubus: update from 2025-07-02 to 2025-10-17
mbedtls: update from 3.6.4 to 3.6.5
openssl: update from 3.0.17 to 3.0.18
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This issue will be addressed in an upcoming OpenWrt SNAPSHOT and the OpenWrt 24.10 minor release.
5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the Phicomm K2T, TP-Link Archer C60 v2, TP-Link Archer C60 v3 and possibly others. For details, see issue #14541.
The OpenWrt community is proud to announce the newest stable release of
the OpenWrt 23.05 stable series. It improves device support and brings a
few bug fixes including security fixes.
Download firmware images using the OpenWrt Firmware Selector:
iptables: backport "nft: track each register individually" from 1.9
wifi-scripts: Fix parsing of Capabilities
Core components update
Update Linux from 5.15.167 to 5.15.189
Update mac80211 from 6.1.110-1 to 6.1.145-1
Update wireless-regdb from 2024.07.04 to 2025.07.10
Update openssl from 3.0.15 to 3.0.16
Update mbedtls from 2.28.9 to 2.28.10
Update wolfssl from 5.7.2 to 5.7.6
Update ca-certificates from 20230311 to 20241223
Update jsonfilter from 2024-01-23 to 2025-04-18
Update libxml from 2.12.5 to 2.14.5
Upgrading to 23.05.6
Sysupgrade can be used to upgrade a device from 22.03 to 23.05, and
configuration will be preserved in most cases.
Sysupgrade from 21.02 to 23.05 is not officially supported.
ipq40xx EA6350v3, EA8300, MR8300 and WHW01 require tweak to the
U-Boot environment on update from 22.03 to 23.05. Refer to the Device
wiki or the instruction on sysupgrade on how to do this change.
Config needs to be reset on sysupgrade.
Known issues
lantiq/xrx200 target shows error messages in DSA switch
configuration of the integrated GSWIP switch. (see: #13200)
OpenWrt 23.05.6 was signed with the wrong signing keys. The keys from
OpenWrt snapshot were used for OpenWrt 23.05.6, OpenWrt 23.05.5,
OpenWrt 23.05.4, OpenWrt 23.05.3, OpenWrt 23.05.2, OpenWrt 23.05.0 and
the release candidates. A later OpenWrt 23.05 service release will use
a different key.
realtek: Avoid interrupt storm on mass packet receive
realtek: Fix stall after restart of otto timer
rockchip: Fix for MSI/MSI-X bug: no MSI/MSI-X, Back to INTx.
rockchip: NanoPC-T6 with A3A444 chips: Fix eMMC corruption
rockchip: rk35xx: Increase the number of serial ports
tegra: Bring back workaround for spurious interrupts
x86: Fix boot problems by activating CONFIG_PCI_MMCONFIG
Various fixes and improvements
busybox: Fix login applet on selinux
hostapd: Reduce debug logging
kernel: Add support for FudanMicro FM25S01A SPI-NAND
kernel: Fix netdev trigger for PHY LEDs
mac80211: Improve WiFi-7 TX performance
mt76: Improve system recovery routine for MT7915
wifi-scripts: Correctly set basic-rates with wpa_supplicant
Core components update
Linux kernel: update from 6.6.93 to 6.6.104
mac80211: update from 6.12.6 to 6.12.44
mt76: update from 2025-02-14 to 2025-09-15
kmod-r8125: update from 9.016.00 to 9.016.01
kmod-r8126: update from 10.015.00 to 10.016.00
kmod-r8127: update from 11.014.00 to 11.015.00
libubox: update from 2024-12-19 to 2025-07-23
udebug: update from 2023-12-06 to 2025-08-24
ucode: update from 2025-05-11 to 2025-07-18
uhttpd: update from 2023-06-25 to 2025-07-06
uqmi: update from 2024-08-25 to 2025-07-30
rpcd: update from 2024-09-17 to 2025-09-01
ubus: update from 2025-05-16 to 2025-07-02
libxml2: update from 2.13.6 to 2.14.5
mbedtls: update from 3.6.3 to 3.6.4
openssl: update from 3.0.16 to 3.0.17
ca-certificates: update from 20241223 to 20250419
wireless-regdb: update from 2025.02.20 to 2025.07.10
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This issue will be addressed in an upcoming OpenWrt SNAPSHOT and the OpenWrt 24.10 minor release.
5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the TP-Link Archer C60 v1, and possibly others. For details, see issue #14541.
kmod-r8125: load module at boot time, disable ASPM
kmod-r8125-rss: enable ENABLE_MULTIPLE_TX_QUEUE
kmod-r8126: load module at boot time
kmod-r8126-rss: enable ENABLE_MULTIPLE_TX_QUEUE
kmod-r8127: load module at boot time
kmod-r8127-rss: enable ENABLE_MULTIPLE_TX_QUEUE
kmod-r8168: load module at boot time
kmod-r8168-rss: add variant
lldpd: enable hardware inventory information (TLV) management
mac80211: add patch to suppress PREP when mesh forwarding is disabled
mac80211: ath11k: fix broadcast failures during GTK rekeying
qmi: increase SIM power-cycle timeouts
Core components update
Linux kernel: update from 6.6.86 to 6.6.93
ucode: update from 2025-02-10 to 2025-05-11
netifd: update from 2024-12-17 to 2025-05-23
bcm27xx-gpu-fw: update to v1.20250430
kmod-phy-realtek: backport upstream v6.15 patches
kmod-phy-realtek: backport upstream v6.16 patches
kmod-r8125: update to v9.016.00
kmod-r8169: backport upstream v6.15 patches
kmod-r8169: backport upstream v6.16 patches
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This issue will be addressed in an upcoming OpenWrt SNAPSHOT and the OpenWrt 24.10 minor release.
5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the TP-Link Archer C60 v1, and possibly others. For details, see issue #14541.
Main changes between OpenWrt 24.10.0 and OpenWrt 24.10.1
Only the main changes are listed below. See changelog-24.10.1 for the full changelog.
Device support
Added new devices:
bmips: Actiontec T1200H
mediatek: CMCC A10
mediatek: Huasifei WH3000
mediatek: Keenetic KN-3811
mediatek: Keenetic KN-3911
mediatek: netis NX31
qualcommax: Linksys MX4300 (LN1301)
ramips: Cudy M1200 v1
ramips: Cudy M1300 v2
ramips: Genexis / Inteno Pulse EX400
ramips: Hongdian H8922 v30
ath79: mikrotik Routerboard 911G: Fix clock speed
ath79: NEC Aterm: Fix initramfs execution
bcm27xx: Raspberry Pi: Fixes for r8169 Ethernet driver
bcm27xx: Raspberry Pi: Update GPU firmware and drivers
imx: Gateworks boards: Misc fixes
mediatek: ASUS: RT-AX59U/TUF-AX4200/TUF-AX6000: Fix boot problems with recent bootloader
mediatek: Xiaomi AX3000t: Fix NMBM handling for devices with Winbond W25N01KVZEIR flash
mediatek: Zyxel EX5601-T0: Fix eth1 wan configuration
ramips: Dovado Tiny AC: Fix wifi MAC addresses
ramips: hiwifi hc5962: Fix reading MAC address
ramips: LAVA LR-25G001: Fix wifi MAC address
ramips: MT7621: Improve MT7621S core detection
ramips: TP-Link Deco M4R v4: Fix port name conflict
realtek: Add new auxiliary MDIO driver and switch devices to it
realtek: HPE 1920: Fix FAN configuration
realtek: Zyxel GS1900-8: Split into v1 and v2
Various fixes and improvements
ath10k-ct: Silence some harmless noisy logs
build: build LLVM toolchain for BPF when packet selects it
dnsmasq: Fix handlers for options filter_rr and cache_rr
kernel: Fix IPv6 TCP GSO segmentation with NAT
kernel: Globally enable CONFIG_PCPU_DEV_REFCNT
kernel: usbnet: Restore usb%d naming for cdc-ethernet devices with local MAC
mac80211: rt2x00: Fix loading EEPROM from card
odhcpd: Fix missed packets in relay mode
umdns: Automatically configure firewall for umdns when needed
Core components update
Update Linux from 6.6.73 to 6.6.86
Update mt76 from 2025-01-14 to 2025-02-14
Update mwlwifi from 2024-04-19 to 2025-02-06
Update wireless-regdb from 2024.10.07 to 2025.02.20
Update ucode from 2024-07-22 to 2025-02-10
Update unetd from 2024-12-17 to 2025-03-09
Update umdns from 2024-09-17 to 2025-02-10
Update omcproxy from 2021-11-04 to 2025-02-27
Update libnl-tiny from 2023-12-05 to 2025-03-19
Update ethtool from 6.10 to 6.11
Update openssl from 3.0.15 to 3.0.16
Update mbedtls from 3.6.2 to 3.6.3
Update ca-certificates from 20240203 to 20241223
Update bcm27xx-gpu-fw from 2024.11.26 to 2025.03.05
Update bcm27xx-utils from 2024.12.19 to 2025.03.14
Update r8125 from 9.014.01 to 9.015.00
Update r8126 from 10.014.01 to 10.015.00
Update r8168 from 8.054.00 to 8.055.00
Update bcm63xx-cfe from 2024-06-25 to 2025-04-02
Update intel-microcode from 20240531 to 20250211
Update firmware-utils from 2024-10-20 to 2025-02-16
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This issue will be addressed in an upcoming OpenWrt SNAPSHOT and the OpenWrt 24.10 minor release.
5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the TP-Link Archer C60 v1, TP-Link Archer C6 v2, and possibly others. For details, see issue #14541.
Ethernet link instability on some MT7530 switches. Users experiencing unstable Ethernet connections should disable Energy-Efficient Ethernet (EEE) as a workaround. See issue #17351 for more information.
The OpenWrt community is proud to announce the first stable release of the OpenWrt 24.10 stable series.
OpenWrt 24.10.0 incorporates over 5400 commits since branching the previous OpenWrt 23.05 release and has been under development for over one year.
Download firmware images using the OpenWrt Firmware Selector:
Upgrades of many components to new versions like the Linux kernel from version 5.15 to 6.6
TLS 1.3 support in default images
mbedtls was updated to version 3.6 which includes support for TLS 1.3
Activate POSIX Access Control Lists and file system security attributes for all file systems on devices with big flash sizes. This is needed by docker nowadays.
This is activated for all targets which do not have the small_flash feature flag. small_flash is set for the ath79/tiny, bcm47xx/legacy, lantiq/ase, lantiq/xrx200_legacy, lantiq/xway_legacy, ramips/mt76x8, ramips/rt288x, ramips/rt305x and ramips/rt3883 targets.
Activate kernel support for Multipath TCP on devices with big flash sizes.
Improved support for WiFi6 (802.11ax) and initial support for WiFi7 (802.11be)
Not many Wifi7 devices are supported by OpenWrt yet
Improved Link Layer Discovery Protocol (LLDP) support
OpenWrt 24.10 uses OPKG only, APK packages are not supported. Only main branch was changed to APK.
Many new devices added
OpenWrt 24.10 supports over 1970 devices. Support for over 100 new devices was added in addition to the device support by OpenWrt 23.05.
Added loongarch64 target for SoCs with Loongson LoongArch CPUs.
Added starfive target for StarFive JH71x0 (7100/7110) SoCs.
Added stm32 target for STMicroelectronics STM32 SoCs.
Renamed ipq807x target to qualcommax.
Removed ath25 target. It supported Atheros ieee80211g devices with maximum 16MB RAM
Removed bcm63xx target. It supported some Broadcom DSL MIPS SoCs and was replaced by the bmips target. The Broadcom DSL itself was never supported.
Removed octeontx target. It supported the Octeon-TX CN80XX/CN81XX based boards
Removed oxnas target. It supported the PLXTECH/Oxford NAS782x/OX8xx
The qoriq target for the NXP QorIQ (PowerPC) SoCs is built
The ipq806x target for Qualcomm Atheros IPQ806X SoCs was converted to DSA
Added support for Airoha AN8855 DSA Switch (Xiaomi AX3000T ship both Mediatek and Airoha Switch in the same revision)
Added bcm2712 subtarget for Raspberry Pi 5.
Core components update
Core components have the following versions in 24.10.0:
Updated toolchain:
musl libc 1.2.5
glibc 2.38
gcc 13.3.0
binutils 2.42
Updated Linux kernel
6.6.73 for all targets
Network:
hostapd master snapshot from September 2024, dnsmasq 2.90, dropbear 2024.86
cfg80211/mac80211 from kernel 6.12.6
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This issue will be addressed in an upcoming OpenWrt SNAPSHOT and the OpenWrt 24.10 minor release.
5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the TP-Link Archer C60 v1, TP-Link Archer C6 v2, and possibly others. For details, see issue #14541.
Ethernet link instability on some MT7530 switches. Users experiencing unstable Ethernet connections should disable Energy-Efficient Ethernet (EEE) as a workaround. See issue #17351 for more information.
Kernel warning in ath10k-ct driver at startup. The warning WARNING: CPU: 3 PID: 1695 at backports-6.9.9/net/mac80211/main.c:270 ieee80211_do_open+0x4e8/0x5e0 [mac80211] appears during boot but is harmless and can be ignored. See issue #15959 for details.
The OpenWrt community is proud to announce the seventh release candidate of the upcoming OpenWrt 24.10 stable series.
OpenWrt 24.10.0-rc7 incorporates over 5300 commits since branching the previous OpenWrt 23.05 release and has been under development for over one year.
This is just a release candidate and not the final release yet.
Download firmware images using the OpenWrt Firmware Selector:
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker. https://github.com/openwrt/openwrt/issues
If there is already an existing ticket feel free to comment that the problem also occurs with OpenWrt 24.10.0-rc7.
Changes between OpenWrt 24.10.0-rc6 and 24.10.0-rc7
Target changes:
airoha: multiple fixes
apm821xx: NETGEAR WNDR4700: fix compat version
ath79: make kmod-usb-chipidea select kmod-phy-ath79-usb
octeon: ubnt-usg: add board name to supported devices
qualcommax: Spectrum SAX1V1K: add missing WAN LED support
ramips: USW-Flex: restore full switch performance
realtek: HPE 1920-8G PoE: fix old compatible
stm32: enable CONFIG_SMSC_PHY
Generic changes:
dnsmasq: add fix related to DNSSEC verification from upstream
generic: fix probe issues with RealTek RTL8221B PHYs
unetd: fix interface teardown
wolfssl: update to version 5.7.6
For a detailed list of changes since OpenWrt 24.10.0-rc7 see the 24.10.0-rc7 changelog.
Highlights in OpenWrt 24.10:
General changes
TLS 1.3 support in default images
mbedtls was updated to version 3.6 which includes support for TLS 1.3
Activate POSIX Access Control Lists and file system security attributes for all file systems on devices with big flash sizes. This is needed by docker nowadays.
This is activated for all targets which do not have the small_flash feature flag. small_flash is set for the ath79/tiny, bcm47xx/legacy, lantiq/ase, lantiq/xrx200_legacy, lantiq/xway_legacy, ramips/mt76x8, ramips/rt288x, ramips/rt305x and ramips/rt3883 targets.
Activate kernel support for Multipath TCP on devices with big flash sizes.
Improved support for WiFi6 (802.11ax) and initial support for WiFi7 (802.11be)
Not many Wifi7 devices are supported by OpenWrt yet
Improved Link Layer Discovery Protocol (LLDP) support
OpenWrt 24.10 uses OPKG only, APK packages are not supported. Only main branch was changed to APK.
Many new devices added
OpenWrt 24.10 supports over 1950 devices. Support for over 100 new devices was added in addition to the device support by OpenWrt 23.05.
Added loongarch64 target for SoCs with Loongson LoongArch CPUs.
Added starfive target for StarFive JH71x0 (7100/7110) SoCs.
Added stm32 target for STMicroelectronics STM32 SoCs.
Renamed ipq807x target to qualcommax.
Removed ath25 target. It supported Atheros ieee80211g devices with maximum 16MB RAM
Removed bcm63xx target. It supported some Broadcom DSL MIPS SoCs and was replaced by the bmips target. The Broadcom DSL itself was never supported.
Removed octeontx target. It supported the Octeon-TX CN80XX/CN81XX based boards
Removed oxnas target. It supported the PLXTECH/Oxford NAS782x/OX8xx
The qoriq target for the NXP QorIQ (PowerPC) SoCs is built
The ipq806x target for Qualcomm Atheros IPQ806X SoCs was converted to DSA
Added support for Airoha AN8855 DSA Switch (Xiaomi AX3000T ship both Mediatek and Airoha Switch in the same revision)
Core components update
Core components have the following versions in 24.10.0-rc7:
Updated toolchain:
musl libc 1.2.5
glibc 2.38
gcc 13.3.0
binutils 2.42
Updated Linux kernel
6.6.73 for all targets
Network:
hostapd master snapshot from September 2024, dnsmasq 2.90, dropbear 2024.86
cfg80211/mac80211 from kernel 6.12.6
Upgrading to 24.10
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible.
Known issues
LEDs handling for Airoha AN8855 is currently not supported. Xiaomi AX3000T with Airoha Switch mounted will have Switch LEDs powered OFF. (problem will be addressed in later OpenWrt SNAPSHOT and later Openwrt 24.10 minor release)
5GHz Wifi on TP-Link Archer C60 v1, TP-Link Archer C6 v2 and probably more devices with ath10k Wifi chip does not work, see #14541
Ethernet link unstable on some mt7530 switches. Deactivate EEE (Energy-Efficient Ethernet) as a workaround, see: #17351
The Chrome team is delighted to announce the promotion of Chrome 144 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks.
Chrome 144.0.7559.59 (Linux) 144.0.7559.59/60 Windows/Mac contains a number of fixes and improvements -- a list of changes is available in the log. Watch out for upcomingChromeand Chromium blog posts about new features and big efforts delivered in 144.
Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.
This update includes 10 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
[$8000][458914193] High CVE-2026-0899: Out of bounds memory access in V8. Reported by @p1nky4745 on 2025-11-08
[TBD][465730465] High CVE-2026-0900: Inappropriate implementation in V8. Reported by Google on 2025-12-03
[TBD][40057499] High CVE-2026-0901: Inappropriate implementation in Blink. Reported by Irvan Kurniawan (sourc7) on 2021-10-04
[$4000][469143679] Medium CVE-2026-0902: Inappropriate implementation in V8. Reported by 303f06e3 on 2025-12-16
[$3000][444803530] Medium CVE-2026-0903: Insufficient validation of untrusted input in Downloads. Reported by Azur on 2025-09-13
[$1000][452209495] Medium CVE-2026-0904: Incorrect security UI in Digital Credentials. Reported by Hafiizh on 2025-10-15
[TBD][465466773] Medium CVE-2026-0905: Insufficient policy enforcement in Network. Reported by Google on 2025-12-02
[$2000][467448811] Low CVE-2026-0906: Incorrect security UI. Reported by Khalil Zhani on 2025-12-10
[$500][444653104] Low CVE-2026-0907: Incorrect security UI in Split View. Reported by Hafiizh on 2025-09-12
[TBD][452209503] Low CVE-2026-0908: Use after free in ANGLE. Reported by Glitchers BoB 14th. on 2025-10-15
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.
Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.
Log in
