Expose UDP TPROXY nft chain counters to diagnostics and show them in the UI; rpcd ucode now collects lines from homeproxy UDP-related nft chains and returns them as udp_tproxy, and diagnostics.js renders that output. Update Zapret help text to note QUIC support (shorten previous comparison to ByeDPI) and update the Russian translation accordingly. Fix zapret preset picker in node.js by keeping a reference to the select element so applyPreset updates the UI selection when a preset is applied.
Introduce support for Zapret (nfqws2) across UI, RPC and core generation: add Zapret entries to client selector UI and AntiDPI status card, implement install/remove/status RPC hooks in the status view, and show kmod warnings. Diagnostics now resolve aggregate tags to configured nodes and can query a focused tag (used to show the active UDP node). generate_client.uc now treats Zapret like ByeDPI for secure-DNS detours and handles Zapret as a synthetic direct outbound with routing marks for main and UDP nodes. core_mgmt.uc avoids auto-selecting UPX-compressed builds on certain MIPS targets (UPX causes crashes) and produces clearer errors when space is constrained. Updated Russian translations for new strings.
Replace references to bol-van/zapret with bol-van/zapret2 in the UI and translations. Updates htdocs/luci-static/resources/view/homeproxy/node.js and po/ru/homeproxy.po so the frontend text and Russian translation point to the new zapret2 repository.
Integrate Zapret (nfqws2) packet-level DPI-bypass: add UI options and warnings, diagnostics, backend detection, and documentation. Changes include frontend guards when NFQUEUE kernel module (kmod-nft-queue) is missing, diagnostics card entries and NFQUEUE counter listing, translated strings, and strategy attribution. The rpcd backend now detects zapret installation/running state, exposes zapret queue contents and a kmod_ok check, and includes Zapret info in the text report. README and wiki pages updated (docs, getting-started, DNS & Diagnostics) and Russian translations adjusted.
Introduce Zapret (nfqws2) integration across UI, init, firewall and RPC. Adds UI controls to enable/install Zapret, a strategy preset picker, strategy tester, and a Discord-voice opt-in; plumbing in client.js and node.js to install/manage and test strategies. Add zapret_test.sh to run isolated strategy tests against several sites. Enable runtime nfqws2 instance via init script (procd) and ensure HomeProxy runs its own nfqws2 with admin-specified strategy. Update nft rules and firewall_post.ut to mark and queue zapret flows (including both TCP and UDP/QUIC handling) and to respect zapret marks; generate_client.uc emits zapret outbound, optional voice-port routing, adds sniff action for QUIC routing, and tweaks default uTLS fingerprint to 'edge'. Add RPC handlers (zapret_status, zapret_prepare_install, zapret_install_pkg, zapret_remove, zapret_strategy_test) to support detection, installation and testing from the web UI. Minor: register 'zapret-out' as a routing option and wire it into rule generation.
Apply a consistent 4-colour scheme for active-node latency across views and remove duplicate code in the status view. Client and diagnostics now treat the 65535 sentinel as a confirmed timeout (red/"timeout"), >=3000 ms as slow (orange/diag-warn), <3000 ms as good (green/diag-ok) and no/zero delay as unmeasured (gray/diag-gray). The client view sets inline colors; diagnostics uses diag-* classes. Also remove the redundant getActiveNode implementation from status.js to avoid duplication.
Add a note to the URLTest help text suggesting removal of nodes that remain orange/grey for a long time. Revise status display logic to color nodes based on the core-reported delay: 65535 = red (timeout), >=3000 ms = orange, <3000 ms = green, and no/0 delay = gray (unconfirmed); show a 'timeout' label instead of raw 65535. Update Russian translations for the modified help text and add a translation for the new 'timeout' string.
Several small but important updates:
- UI (htdocs/luci-static/resources/view/homeproxy/client.js): add Cloudflare (1.1.1.1) and Google (8.8.8.8) DNS presets; restrict the "Same as main node" (main-out) option to non-custom routing modes and only when a main_node exists; always expose ByeDPI outbound when enabled; rename "Proxy filter mode" to "Proxy mode for devices" and add explanatory hints for gaming/global proxy IP options.
- Node UI (htdocs/luci-static/resources/view/homeproxy/node.js): fix closure variable (i -> k) to avoid iteration bug and shorten the probe hint text.
- Generator (root/etc/homeproxy/scripts/generate_client.uc): add xhttp_padding() to coerce disabled xhttp padding values ('0', '0-0' or empty) to the safe default '100-1000' and apply it when emitting sing-box/hiddify xhttp fields to prevent fatal core errors.
- Init script (root/etc/init.d/homeproxy): restore subscription auto-update cron entry on start when enabled (adds daily run at configured hour and restarts cron), reintroducing behavior lost during a prior init rewrite.
- Translations (po/ru/homeproxy.po): add and update Russian translations for the new/changed UI strings.
These changes prevent runtime failures for certain provider configs, restore missing auto-update behavior, improve UI clarity, and fix a node probing bug.
Introduce XHTTP packet-up controls and split-download support across UI, parsers and generators.
- htdocs/luci-static/resources/view/homeproxy/node.js: parse additional xhttp fields from links (scMaxEachPostBytes / sc_min_each_post_bytes and scMinPostsIntervalMs / sc_min_posts_interval_ms), add UI inputs for padding, packet-up limits and detailed split-download settings (host/path/server/port/SNI/ALPN/insecure).
- po/ru/homeproxy.po: add Russian translations for all new UI labels and help texts.
- root/etc/homeproxy/scripts/generate_client.uc: add xhttp_download() helper to build a per-core download transport, emit both camelCase (hiddify) and snake_case (sing-box) xhttp options, and attach the download section under the appropriate core-specific key.
- root/etc/homeproxy/scripts/update_subscriptions.uc: accept both dialects when parsing xhttp options (camelCase and snake_case) and handle both downloadSettings (hiddify) and download (sing-box), normalizing host/server/port and TLS/alpn/utls fields.
These changes ensure compatibility with both hiddify-core and sing-box dialects and expose finer-grained xhttp controls in the UI.
Introduce a Connectivity diagnostics section (connection checks, exit IP / active node info) with new RPCs and live polling; move connection-check UI out of status into diagnostics and add translations. Add active URLTest node display and several routing/DNS UI tweaks for 'proxy_banned_ru' mode (russia-dns, secure-dns, main-out, byedpi-out). Rework ByeDPI presets: group presets by letter, add community presets, improve "Test all" flow with ordered execution, a Stop button, clearer progress/messages and updated translations. Fix template/comment text (replace crude QUIC comment), and harden client config generation by recognizing built-in DNS tags and skipping empty/dangling routing node outbounds to avoid crashes. Minor README_ru wording update and assorted i18n strings added.
Several related fixes and improvements:
- htdocs/luci-static/.../client.js: Reworded the Russia Inside/Re-filter description to clarify contents and routing behavior shown in the UI.
- root/etc/homeproxy/scripts/generate_client.uc: Tightened UDP-over-TCP generation so it is only emitted for hiddify when node.udp_over_tcp is enabled; treat an empty cfg.node as equivalent to 'main-out' when selecting effective_outbound and avoid creating redundant outbounds. These changes make outbound selection more robust and prevent unnecessary outbound creation.
- root/usr/share/homeproxy/scripts/core_mgmt.uc: Made download_pkg tolerant of an optional leading core argument (accepts both (url, tmp_path) and (core, url, tmp_path)); improved install_kmods by defaulting to a detected package manager and returning a proper success/failure result with an error message when kmod installation fails. This improves compatibility with different callers and surfaces installation errors.
Rename project and packages to Re:HomeProxy (luci-app-re-homeproxy), update package metadata and build scripts, and adjust UI labels and menus accordingly. Improve core install flow: add RAM detection, overlay-compression heuristics, automatic selection between full and compact (UPX) builds, stricter storage/RAM checks, and a variant argument for prepare_install; fetch sing-box-extended releases more robustly. Fix runtime behavior: init.d restores a default config when missing, add packaged homeproxy.default, prefer user-preferred core in ucode, and suppress top-level TLS for Shadowsocks in generated client configs. UI tweaks include better install/remove UX, gating "Same as main node" for custom routing, and updated diagnostics/status strings. Update translations (po files) and rpcd/menu/acl renames to match the rebrand.
Improve the ByeDPI strategy tester UI and backend and adjust routing logic for special nodes.
- UI (htdocs/luci-static/.../node.js): probe 4 sites (YouTube, Telegram, Discord, Speedtest) to reveal destination-sensitive strategies, display per-site pass/fail dots and aggregate full/partial results, update 'Test all' flow and messages, and require curl for full testing.
- RPC (root/usr/share/rpcd/ucode/luci.homeproxy): byedpi_strategy_test now starts one ciadpi instance and runs parallel curl probes, returns detailed per-host results and reasons (dns/tls/timeout/etc.), preserves/restores nft redirect rules and ByeDPI skgid, and handles cases without curl by returning a startup-only result.
- Generator (root/etc/homeproxy/scripts/generate_client.uc): route secure-dns via direct-out when main node is byedpi-out, and force ruleset downloads via direct-out when main path uses WireGuard/AmneziaWG or is byedpi-out; add clarifying comments about why these exceptions are required.
Improve core detection and generation logic, avoid sing-box strict errors, and update UI copy/translations.
- generate_client.uc: Add preferred_core handling and explicit detection for hiddify-core vs sing-box to mirror init.d precedence; fall back to UCI custom path when neither standard binary is present. This ensures the generated dialect matches the core the system actually runs.
- generate_client.uc: Suppress the stray 'tls' field on Shadowsocks outbounds when using sing-box (sing-box rejects unknown fields while hiddify-core is lenient). This prevents generation errors for ShadowTLS-wrapped Shadowsocks.
- client.js and po/*.po: Update the UI description to include approximate list sizes for "Russia Inside" and "Re-filter" and propagate those changes to Persian and Russian translations.
Move ByeDPI configuration and testing UI from the Client tab to the Node Settings page and add an integrated installer/prepare flow. client.js: add fs/ui requires, new RPC declarations and core_mgmt download helper, change ByeDPI flag to auto-install on first enable with a modal-driven install flow and requirement checks; remove the large in-page ByeDPI settings block (now on Node page). node.js: add a full ByeDPI tab (presets, command options, strategy tester, test-all runner, UDP-over-TCP and QUIC-block flags) with RPC-based testing and curl detection. status.js: disable package removal when ByeDPI is selected as the main node and pass a flag to the card builder. Update po and pot translation strings and adjust several UI texts and warnings. Also update init/scripts/ucode files related to ByeDPI packaging and management.
Expose ByeDPI controls in the Client UI: add an enable flag, port / options fields, grouped preset selector, and a command-options field. Implement an interactive "Test current strategy" button and a "Test all strategies" runner (requires curl) that exercises ciadpi and shows which presets work. Add Status page UI to show/install/remove curl and wire new RPC methods (byedpi_strategy_test enhanced to actually start ciadpi and optionally perform an HTTP test via curl, plus curl_status/curl_install/curl_remove). Adjust package install helpers (apk handling and signing key copy) in core_mgmt and rpcd ucode. Update POT/PO translation templates for the new strings.
Introduce local ByeDPI (ciadpi) integration: add a ByeDPI tab in Client settings (presets, cmd options, tester, UDP-over-TCP and QUIC-blocking), a ByeDPI card on the Status page with install/remove/update actions and live status, and route support (byedpi-out) in generated client configs. Add RPC handlers for byedpi status, prepare/install/remove, strategy test and custom core detection; update ucode to detect custom core paths and expose core info. Init script now launches ciadpi when enabled and can add an nft rule to block QUIC; generate_client handles byedpi outbound fallback. Also update menu ordering and add translation strings for new core descriptions.
Clarify supported protocols in the import modal, reword the latency-switch description, and fix the Comss.one DNS IP. Updated corresponding .po translation files and the POT template to reflect the new strings and translations.
Introduce a URLTest info field and UI options in the client view (adds a DummyValue info block and main_urltest_nodes list, shown when main_node=urltest). Ensure imported WireGuard/AmneziaWG nodes get unique labels by appending -N if a label collision is detected. Update source list descriptions (Re-filter and Russia Inside) and add corresponding translation strings in POT and fa_IR/ru/zh_Hans PO files.
Add a new HomeProxy diagnostics page (htdocs/.../diagnostics.js) for core/config/DNS/nftables checks and report generation. Introduce ShadowTLS options (flag + password) in node settings and wire dependencies for Shadowsocks. Refactor core installation flow in status.js into prepare/download/install_pkg/install_kmods steps with new RPC calls, improving download/install error handling and progress messages. Update UI copy in client.js, and refresh localization strings and backend ucode/scripts to match the new features.
Add a new /usr/share/homeproxy/scripts/core_mgmt.uc to handle core info, remote checks, install and remove operations (apk/opkg, GitHub API, package downloads). Update LuCI frontend to call the new script (fs.exec_direct) instead of in-process rpc methods, adjust core descriptions and translations, and conditionally hide China/GFW list version fields when routing_mode is proxy_banned_ru. In generate_client.uc prefer direct-out for ruleset downloads if the main node (or urltest nodes) use WireGuard/AmneziaWG. Also ensure RUN_DIR exists earlier in the init script and remove the old core_* rpc handlers from luci.homeproxy.
Introduce core management features for hiddify and sing-box: add client-side UI in htdocs/luci-static/resources/view/homeproxy/status.js (new RPC declarations, buildCoreCard, core info display, install/check/remove buttons, and load/render changes) and server-side RPC handlers in root/usr/share/rpcd/ucode/luci.homeproxy (core_info, core_check_remote, core_install, core_remove).
The server side detects package manager (apk/opkg), architecture, free /tmp and overlay space, inspects installed versions, queries GitHub releases for latest versions, and performs installs/removals via wget + apk/opkg with basic validation and error reporting. The UI shows package manager, arch, free space, install status/version, remote update check, and interactive install/update/remove flows.
Allow 'main-out' as a valid node value and expose it in the client UI (luci) so users can select "Same as main node". Improve WireGuard endpoint generation by normalizing local addresses: add a helper to append /32 or /128 as needed and support arrays of addresses. Recognize 'main-out' in outbound resolution and change ruleset download detour logic to use 'direct-out' when the main node is WireGuard/AmneziaWG (endpoints may not be ready at startup), otherwise use 'main-out'. Changes affect htdocs/luci-static/resources/homeproxy.js, htdocs/luci-static/resources/view/homeproxy/client.js and root/etc/homeproxy/scripts/generate_client.uc.
Add small UI enhancements and adjust DNS/routing defaults for the Russia (proxy_banned_ru) mode. Changes include:
- UI: add icons and clearer labels in htdocs/.../client.js (main node, secure/russia DNS labels, flags, source/node labels, Separate URLTest). Reorder and rename some DNS options.
- DNS: switch default secure DNS to Cloudflare DoH (https://cloudflare-dns.com/dns-query) and update DoH/DoT option entries and default.
- Routing: change default config (root/etc/config/homeproxy) to routing_mode=proxy_banned_ru, routing_port=all, disable ipv6_support, enable proxy_calls and no_proxy_torrents by default.
- generate_client.uc: use new secure DNS default, add comment about Cloudflare DoH via proxy, add early resolve rule, and reorder/modify torrent and VoIP proxy rules so torrent bypass has priority and port/protocol mappings are corrected.
- init script: include proxy_banned_ru in dnsmasq configuration branch.
- Localization: update template and translations (fa_IR, ru, zh_Hans) to reflect new strings.
These changes aim to improve UX, prefer Cloudflare DoH for encrypted DNS by default, prevent DNS leaks, and refine routing behavior for the RU-specific proxy mode.
Introduce a new 'proxy_banned_ru' routing mode with optional advanced custom rules and nodes. UI changes: add 'Advanced custom rules' flag, 'Same as main node' option, update routing_mode defaults based on installed languages, increase URLTest tolerance placeholders (50 -> 150), rename Yandex label, and update several localized strings. Client logic (generate_client.uc): honor show_advanced_rules, add has_outbound helper, generate advanced routing_node outbounds and rules (including 'main-out' handling), avoid duplicate outbounds, and switch several local rule sets to remote downloads with update detours. Status/UI: remove direct display of refilter/itdoginfo versions. Scripts: stop automatic refilter/itdoginfo updates from crond and remove SRS GitHub download logic from update_resources.sh. Also add validation to prevent duplicate routing sources. Translation templates and PO files updated to reflect string changes.
Introduce a new routing mode 'proxy_banned_ru' and related UI, logic and resource handling. UI: client.js gains a new routing_mode value, DNS options (russia_dns_server, secure_dns_server), proxy_calls flag, validation tweaks, and a new 'RU Proxy Rules' section for per-source rules and URLTest node groups. Status: status.js shows versions for refilter and itdoginfo when RU mode is active. Backend: generate_client.uc updated to read new settings, create russia-dns/secure-dns servers, route proxy lists via secure DNS, change default routing/resolver behavior, generate per-rule outbounds and rule sets for RU rules and handle proxy_calls. Scheduling/resources: update_crond.sh now triggers refilter/itdoginfo updates when RU mode is active; update_resources.sh adds check_srs_update to fetch .srs files from GitHub releases and handles 'refilter' and 'itdoginfo' lists. Localization: updated POT and added translations (fa_IR, ru, zh_Hans) for new strings. These changes enable targeted handling of Russian domains and proxying of blocked content with automated resource updates.
Expose and persist a preferred core option across UI and runtime. UI: show a 'Preferred core' dropdown in routing when multiple cores are available and populate it with auto/hiddify/singbox (htdocs/luci-static/.../client.js). Translations: add msgid for 'Preferred core' to POT and update fa_IR, ru, zh_Hans PO files. Init script: read config preferred_core, try the preferred core first and fall back to any installed core, keeping previous error behavior if none found (root/etc/init.d/homeproxy). Backend: rpcd ucode now reports available_cores by checking /usr/bin/hiddify-core and /usr/bin/sing-box (root/usr/share/rpcd/ucode/luci.homeproxy).
Refactor UI and backend to show clearer node labels and richer IP metadata. Add a shared resolveTag() in the status view to map sing-box outbound tags to human-readable UCI labels and remove duplicated logic; show IP country/org and delay alongside the IP. Update generate_client.uc to make default_domain_resolver compatible with both sing-box variants (object action for extended sing-box, plain tag/string for standard). Update luci.homeproxy RPC logic to follow GLOBAL.now to the active leaf node (including Selector), pick the first suitable fallback group if needed, and return richer direct/proxy entries (ip, country, org, delay, node) via a toEntry helper.
Add full Farsi (fa_IR) translation and CI/build support: - Add po/fa_IR/homeproxy.po (Persian translations). - Extend .github/build-ipk.sh to build a luci-i18n-homeproxy-fa package for both apk and ipk formats. - Update .github/workflows/build-ipk.yml to watch po/**, expose FA artifact names to the environment, and upload fa APK/IPK artifacts.
UI/runtime changes: - Update htdocs/luci-static/resources/view/homeproxy/node.js to rename TLS fingerprint field tls_fingerprint -> tls_utls in parsed link objects. - Add active node polling and display (getActiveNode) in htdocs/luci-static/resources/view/homeproxy/status.js and show the Active Node dummy field when core_type === 'singbox'.
Other: - Update RPC/uCode (root/usr/share/rpcd/ucode/luci.homeproxy) and translation templates/other locale files to support the new UI/RPC changes and translation strings.
Detect and expose core type/version reliably and add MTProxy inbound
- LuCI: fall back to /var/run/homeproxy/core.info when RPC lacks core info; load features before rendering status view.
- init: write core_type and version to /var/run/homeproxy/core.info on start.
- rpcd ucode: improve kernel module detection (use /sys/module), normalize access checks and parse core version/tags more robustly.
- UI: remove ip-full from Tun prerequisite message; only show direct/proxy IP checks for hiddify cores.
- Server view: add MTProxy server options (secrets, domain fronting, timeouts, concurrency) and expose MTProxy type when using singbox core.
- Client generator: emit MTProxy fields (secrets -> users, domain fronting, timeouts, concurrency) and propagate xhttp x_padding_bytes when using singbox.
- Node parsing: handle amnezia last_config JSON, fix labels and host/port resolution, and extract xhttp fields (path/host/mode/padding).
Detect active core (hiddify-core vs sing-box) and update UI and runtime generation to handle both.
- htdocs/*: Update client/server status rendering to show detected core name/version or a "no core installed" message; adjust UI descriptions to "multi-core" wording; rename runtime log label to "core client".
- root/etc/homeproxy/scripts/generate_client.uc: Detect active core and set is_hiddify/is_singbox flags; make sniff/sniff_override/set_system_proxy fields conditional for hiddify; add sing-box-specific sniff route entry while keeping other route entries intact.
- root/etc/init.d/homeproxy: Select appropriate run command (srun for hiddify, run for sing-box) and use it when launching the core.
These changes enable support for both hiddify-core and sing-box, avoiding inappropriate configuration options for the inactive core and providing clearer UI feedback about which core is installed.
Support for AmneziaWG (vpn://) links and sing-box core was added across UI, backend and init scripts. UI: parseVpnLink() handles AmneziaVPN vpn:// payloads; node editor adds amneziawg type and numerous Amnezia-specific fields; share import now accepts vpn:// links, deduplicates inputs and imports vpn + URI configs. View changes: renderStatus shows detected core name (hiddify-core or sing-box). Backend: generate_client treats amneziawg as a wireguard endpoint with extra amnezia parameters and includes amneziawg nodes in endpoint/outbound selection. Init script: start logic now prefers hiddify-core or sing-box and logs the actual binary started. RPCD: feature detection updated to probe for sing-box and parse its version/tags.
New Features
Outbound Interface Binding
Added Binded interface field to every outbound node — allows pinning a proxy node to a specific network interface. using SO_BINDTODEVICE
The bind_interface value is preserved across subscription updates and not overwritten when nodes are refreshed
Status Page — IP Check
Added Direct IP button: shows the current exit IP and latency of the direct outbound
Added Proxy IP button: shows the exit IP, latency, and active node name of the currently selected proxy in the URLTest/Fallback group
Status Page — YouTube Check
Added YouTube connectivity check alongside the existing Google, Yandex, Baidu, Speedtest checks
Clash API
sing-box Clash API now enabled on 127.0.0.1:9090 for all routing modes
Build
Added luci-i18n-homeproxy-zh-cn package to the build pipeline — Chinese Simplified translation is now distributed as a standalone installable package, for both main and legacy (OpenWRT 23.05) releases
Translations
Added Russian and Chinese Simplified translations for all new UI strings
Fixed missing Russian translation for unchecked
Changelog
Link Import (Import share links)
Added support for importing Mieru, SSH, WireGuard, and NaïveProxy share links — these were parsed by the subscription backend but silently ignored by the UI importer
Added VLESS xhttp transport support, including Hiddify extensions: TLS fragment, allowInsecure, custom headers, and download settings (xhttp/reality/TLS)
Added Trojan xhttp transport support with the same Hiddify fragment and allowInsecure extensions
Fixed Hysteria2 insecure detection — the old check treated insecure=0 as insecure (any non-empty string is truthy in JS)
Fixed TUIC missing with_quic feature guard, added tls_insecure, zero_rtt_handshake, and heartbeat fields
Mieru Node UI
Added Mieru as a selectable node type (requires with_quic build, same as Hysteria/TUIC)
Added Mieru-specific fields: Protocol (TCP / UDP / TCP and UDP), Port range, Multiplexing level, and Handshake mode
The generic Port field is now hidden for Mieru nodes since Mieru uses a port range instead of a single port
Added Russian and Chinese translations for all new Mieru UI strings
Stability Fix
Fixed a hiddify-core crash (nil pointer dereference in OutboundMonitoring.Start) that occurred when a node was deleted but still referenced in a URLTest group — the config generator now silently skips non-existent nodes instead of emitting a broken outbound
Client Routing
Added inbound matching to routing rules — rules can now be scoped to specific inbound tags (dns-in, mixed-in, tproxy-in, tun-in, or any server-defined inbound)
Build & Versioning
Package versions now use YYYY.MM.DD-rN format (e.g. 2025.05.19-r83) — date-based CalVer with APK-native revision suffix, replacing the opaque unix epoch + git hash format
Release tag and package version are now consistent with each other (previously they were two different values)
Makefile and build-ipk.yml updated to comply with OpenWRT CONTRIBUTING.md
Introduce an 'inbound' field in the client UI to allow matching inbound tags (dns-in, mixed-in, redirect-in, tproxy-in, tun-in and server-based cfg-<name>-in entries). The UI option is populated from server sections and marked modal-only. Also update the client generator to include cfg.inbound into route rules so selected inbound matches are emitted into the generated configuration.
Pass the fallback object into L.resolveDefault and normalize the loaded value for domain lists. Previously the default was incorrectly provided as the second argument to then(), and res.content could be undefined. This change supplies {} as the resolveDefault fallback and returns res.content ?? null for both proxy_list and direct_list
Replace the RPC-based subscription update and polling flow with a direct fs.exec_direct call to /etc/homeproxy/scripts/update_subscriptions.uc from the UI. Remove client-side rpc usage and the async polling logic, and update error handling to reload on success and reset the map on failure (use this.map.reset()). Remove the corresponding server-side rpcd ucode methods (subscription_update and subscription_update_status) and the now-unused translation string.
Introduce a legacy build mode for OpenWRT 23.05 and make subscription updates asynchronous with status polling. Changes: add LEGACY arg to .github/build-ipk.sh (produce -legacy IPKs and patch update_subscriptions.uc to avoid ucode-mod-digest by injecting an md5 shim), adjust control Depends and artifact names; update .github/workflows/build-ipk.yml to build/publish legacy IPKs and tweak asset matching; implement non-blocking subscription_update + new subscription_update_status RPC in root/usr/share/rpcd/ucode/luci.homeproxy; update frontend (htdocs/...) to poll update status with timeout and use translated timeout message (po/ru/...). This enables compatibility with systems missing ucode-mod-digest and avoids blocking UI during long subscription updates.
Display a modal while subscriptions are being updated and improve handling of update results: hide the modal on completion or error, only reload the page when the update exit code is 0, show a notification on non-zero exit codes, and reset the map on failure. Also add corresponding Russian translations for the new UI strings. Changes in htdocs/luci-static/resources/view/homeproxy/node.js and po/ru/homeproxy.po.
Replace references to the deprecated 'sing-box-s' instance with 'hiddify-c', remove the separate generate_server.uc script, and consolidate server inbound generation into generate_client.uc. UI code (server.js, status.js) now checks/logs only for 'hiddify-c'. ACL (luci-app-homeproxy-hiddify.json) no longer exposes sing-box-s.log. RPC ucode (luci.homeproxy) restricts log_clean types to 'homeproxy' and 'hiddify-c'. Overall cleanup unifies server generation and removes obsolete sing-box-s artifacts.
Client and server views now build a version string (v<version> or 'unknown') and use it in the status render template to avoid duplicating the 'v' prefix and to show a fallback when version is missing. The rpcd ucode for luci.homeproxy now reads the full hiddify-core output, extracts the version and Tags using regexes, closes the process earlier, and trims/splits tags into feature flags for more robust parsing.
Update homeproxy client and server views to use the new branding and backend reference: replace "HomeProxy" with "HomeProxy-hiddify", change status captions, replace "sing-box v%s" with "hiddify-core v%s", and update section descriptions to mention "based on hiddify-core".
