Freenetic 0.4.4 — Oxidice

[0.4.4] — 2026-10-13

Fix dashboard updates from older Freenetic installations, including 0.2.5.
The installer in the source tag now downloads the generated release installer,
checks its tag, checksum and shell syntax, then runs it. This allows the old
updater to install the current release through the usual Update button.

Generated release installers still carry the package checksums and APK signing
key hash. Existing release tags remain unchanged.

Freenetic 0.4.3 — Oxidice

[0.4.3] — 2026-10-13

Hotfix for HTTPS failing after selecting a Wi-Fi Internet connection.

• When applying a Multi-WAN mode, remove mwan3's unchanged sample
  https → balanced rule so TCP/443 follows the selected default policy.
  Previously, this rule could keep HTTPS on an unavailable wired connection
  while HTTP used Wi-Fi. Modified HTTPS rules remain unchanged, and a failed
  apply restores the previous configuration.
• Add regression coverage for Wi-Fi selection, custom-rule preservation and
  rollback. Verify HTTP and HTTPS on a CMCC RAX3000M with mwan3 running.

After updating, apply the desired mode again on the Multi-WAN page to migrate
the sample rule. Installing the update alone does not change routing rules.

Freenetic 0.4.2 — Oxidice

[0.4.2] — 2026-10-09

This release fixes service cleanup and routing behavior in the 0.4.x
integrations and expands fnc diagnostics and recovery.

• Add read-only fnc show wan, show multiwan, show dns and
  show applications [package] commands backed by netifd, UCI and the
  existing Freenetic status helpers.
• Apply fnc interface and route changes through OpenWrt's timed UCI
  rollback. Add fnc pending, confirm and rollback; unconfirmed changes
  revert after 90 seconds, including when the CLI connection drops. Reject
  a second change or reboot while one is pending, and refuse Wi-Fi interface
  up/down because restoring the network option alone does not reattach STA.
• Make Applications distinguish exact package names, allow installs when
  repository lists are initially empty, refresh installed state after package
  changes, and reject overlapping package operations. Correct the USB printer
  server package name to p910nd.
• Fix fnc interface address changes so protocol and address are committed
  together; clear stale addresses when switching to DHCP. Reject routes with
  no matching gateway interface and malformed or extra arguments. Show the
  CLI build identifier with fnc --version.
• Restore Zapret2's previous running state if package removal fails.
• Preserve the shared HEV tunnel service state through Mixomo disconnects and
  rollbacks, and serialize Mixomo changes with other Freenetic network actions.
• Include available Freenetic-managed secondary WANs in Zapret2's compiled
  egress set; tolerate a temporarily unavailable configured WAN when another
  usable WAN remains.
• Remove Freenetic-managed mwan3 and HEV sections during explicit full
  uninstall, reload affected services, and restore their configuration if the
  package transaction fails.
• Restart PBR after the Ethernet port editor enables its first VPN policy.
• Reject WireGuard firewall marks that overlap bits reserved for Zapret2.
• Keep operator edits to https-dns-proxy when Freenetic releases Mihomo DNS
  ownership; update the owned proxy after raw YAML mixed-port changes, and
  detach it before removing the Mihomo runtime. Bootstrap Mihomo's direct DNS
  independently and roll back an apply if the DoH listener fails a live query.

Freenetic 0.4.1 — Oxidice

[0.4.1] — 2026-10-04

This release fixes problems found after fresh installs of 0.4.0.

• Zapret2 now opens on a Freenetic status and service-control page, with links
  to the versioned profile, list and log editors. Its entry remains visible
  before installation; installing a runtime refreshes LuCI's cached menu.
• The Wi-Fi Monitor's recommended-channel button now applies the selected
  channel after confirmation and reports any configuration error.
• Long dependency trees in the OpenWrt package details dialog scroll inside
  the dialog, keeping package actions reachable on narrow screens.
• The Mihomo page can merge parsed proxy links or subscriptions into a chosen
  select group in an existing YAML config, with a preview before applying.
  Existing third-party configs stay separately owned.
• MagiTrickle can connect to Mihomo through a dedicated hev-socks5-tunnel
  instance. The connection is optional; Freenetic changes only its marked
  network and firewall sections, checks for pending edits, and restores the
  previous configuration if setup fails. The Internet Helper list is offered
  after the tunnel is connected. Users with another VPN can still select its
  interface in MagiTrickle. Removing MagiTrickle disconnects the managed
  tunnel without deleting the Mihomo configuration.
• The MagiTrickle list chooser now offers Internet Helper #1 and #2, and
  restores the previous rules if the new list fails to start.
• System settings now let users choose whether to preserve the Freenetic UI
  across an OpenWrt sysupgrade. If its files are absent afterward, a small
  fallback returns LuCI to Bootstrap instead of leaving an unusable theme.
• Mihomo removal now respects external ownership, and runtime installation
  checks available overlay space before replacing the binary.

Freenetic does not run the upstream Mixomo installer automatically. Its tunnel
layout was tested on a reset BT-RB300; Freenetic detects that installation as
externally managed and leaves its configuration alone. On the tested OpenWrt
snapshot, matching kernel modules and access to the packages feed were needed
before the upstream installer could finish.

Known limitations: if Mihomo's mixed port is changed in raw YAML after the
MagiTrickle tunnel is connected, reconnect the tunnel to update its SOCKS port.
The protected-DNS proxy setting does not yet follow raw YAML port changes.
Removing https-dns-proxy outside Freenetic may leave stale dnsmasq entries;
check DNS settings after uninstalling it. A failed Zapret2 package removal can
leave its service stopped until it is started again.

Introducing Freenetic 0.4.0 Oxidice

[0.4.0] — 2026-09-26

Introducing Oxidice

Freenetic 0.4.0 Oxidice is a release about choice: more than one way to reach
the Internet, more control over where traffic goes, and a much richer set of
network tools—all managed from the router’s own interface.

The surface remains familiar. Beneath it, packets can split, reorder, and take
a different route.

Connectivity and routing

• Added a guided Multi-WAN workspace with single-connection, automatic
  failover, and flow-balancing modes.
• Added setup for secondary Ethernet and nearby Wi-Fi connections, with clear
  connection health and active/standby state in both the dashboard and traffic
  diagram.
• Expanded the managed-uplink model to seven connections across Ethernet,
  Wi-Fi, and modem-backed interfaces.
• Made Multi-WAN changes transactional: Freenetic scopes its UCI changes to
  owned sections, snapshots state, verifies the result, and rolls back failed
  changes without taking over unrelated mwan3 policies.
• Added route-metric isolation for managed uplinks and checks for DHCP,
  conflicting subnets, and Internet reachability before accepting a Wi-Fi
  backup link.

Network tools and services

• Added the official Zapret2 runtime and a native LuCI workspace for DPI
  strategies, service settings, scripts, lists, Blockcheck2, and debug logs.
  The service is installed inactive; enabling it and selecting strategies
  remain explicit actions.
• Added router-side Mihomo configuration and management: convert proxy links
  and subscriptions locally, edit the YAML directly, inspect and export the
  effective configuration, and control the service and its logs.
• Added optional Mihomo blocks for protected DNS through https-dns-proxy and
  transparent TUN routing. Existing config-only installations can be adopted
  by the managed application without discarding their configuration.
• Added MagiTrickle as an optional application, including its LuCI entry point
  and a post-install offer for an Internet Helper domain list. The list is
  offered separately and is never enabled without the user’s choice.
• Added x86/64 architecture support across installation checks, self-update,
  fnc, Zapret2 and Mihomo packaging, and release assets.

Interface and day-to-day use

• Added a responsive reboot page with an explicit confirmation and a reminder
  to save configuration before restarting the router.
• Added administrator-password changes under System management, with
  confirmation and clear result feedback.
• Improved system and kernel logs, package-manager actions, service screens,
  mobile layouts, and in-place navigation across Freenetic views.
• Moved Mihomo into Services and clarified the distinction between managed
  applications and software configured outside Freenetic.
• Fixed theme persistence and restored the LuCI menu after switching themes.
• Added the bundled Carter One display face for the Oxidice codename.
• Refreshed the English product screenshots used by the project’s README.

Installation and compatibility

• Reduced the required free overlay space to 16 MiB on MT7981/Filogic and
  8 MiB on MT7621, consistently across installer preflight, package guards,
  self-update, and documentation.
• Fixed self-update downloads for networks with broken IPv6 routes or blocked
  GitHub asset redirects by preferring IPv4 and resolving pinned assets via
  the GitHub Releases API.
• Improved OpenWrt SDK dependency setup and package-content checks for both
  IPK and APK package formats.
• Verified the OpenWrt 24.10.8 and 25.12.5 release matrix on Filogic, MT7621,
  and x86/64, including package checks for both supported package formats.

Release notes

• Prerelease names remain concealed in alpha and beta release titles; the
  Oxidice codename is revealed with this stable release.
• The 0.4.0 release includes four LuCI packages and the matching fnc binary
  in each compatible release set, so self-update can reject incomplete asset
  uploads instead of installing a mixed revision.

Freenetic 0.4.0b-2

[0.4.0-beta.2] — 2026-09-26

Fixed

• Corrected the generated release installer’s overlay preflight: it now uses
  the 16 MiB Filogic/MT7981 and 8 MiB MT7621 limits. Beta.1 could reject a
  Filogic router with 29 MiB free even though the supported threshold is 16 MiB.

Verification

• Added installer and release-generation contracts to keep these thresholds
  aligned in future release assets.

Freenetic 0.4.0b-1

[0.4.0-beta.1] — 2026-09-26

Improved

• Refined the responsive system interface, including the reboot page,
  system and kernel logs, package actions, and settings navigation. Router
  password changes now live under System management.
• Moved Mihomo into Services and improved handling of existing
  configuration-only installations.
• Reduced minimum free overlay requirements to 16 MiB for MT7981 and 8 MiB
  for MT7621.

Verification

• Passed the OpenWrt 24.10.8 and 25.12.5 package matrix for filogic, mt7621,
  and x86/64, including IPK/APK package checks.

Freenetic 0.4.0a-6

[0.4.0-alpha.6] — 2026-09-23

Added

• Added router-side Mihomo installation and management, including proxy-link
  and subscription conversion, a manual YAML editor, effective-configuration
  export, and optional protected-DNS and TUN blocks.
• Added MagiTrickle as an optional application with its native web interface
  embedded in LuCI and a post-install offer for the Internet Helper domain
  list.
• Added OpenWrt x86/64 support to installer preflight, self-update, dashboard
  release selection, fnc, and Zapret2/Mihomo architecture handling.
• Added x86/64 APK and IPK builds to the release matrix, with mirrored noarch
  LuCI packages and pinned OpenWrt SDK checksums.

Improved

• Applications now offer MagiTrickle after Mihomo or a supported VPN client
  is installed.
• MagiTrickle package setup verifies the repository key, handles the current
  OpenWrt NAT dependency layout, and can retry downloads through the WAN DNS
  resolver when a local encrypted resolver is unavailable.
• The optional Internet Helper list is checked before installation, and an
  existing MagiTrickle configuration is backed up first.

Verification

• Added x86/64 release-asset, installer-hash and dashboard compatibility
  contracts while retaining the existing ARM64 and MIPSLE release paths.
• Added package, LuCI menu, ACL and post-install list-offer contracts for
  MagiTrickle and expanded Mihomo and release-workflow checks.

Alpha scope

• The Internet Helper list remains optional and is downloaded only after the
  user accepts the offer. Mihomo and MagiTrickle are installed separately
  from their upstream sources.

Freenetic 0.4.0a-5

[0.4.0-alpha.5] — 2026-09-20

Fixed

• Fixed the self-update downloader on routers with a broken or incomplete
  IPv6 route, or networks that block GitHub's release redirect, by preferring
  IPv4 and resolving the pinned installer through the GitHub Releases API.

Freenetic 0.4.0a-4

[0.4.0-alpha.4] — 2026-09-20

Fixed

• Fixed the self-update downloader on routers with a broken or incomplete
  IPv6 route by preferring IPv4 for pinned GitHub release assets, while
  retaining a fallback for IPv6-only and older wget environments.