PuppyIP Resource Center
Network & Connection Troubleshooting 10 min Published 2026-11-17

KWRT sing-box Version Check Times Out on Xiaomi R2100: Check Core Compatibility and Routing

After a sing-box version check times out on an R2100, separate a failed version lookup from core incompatibility and routing failure.

Xiaomi R2100 KWRT PassWall Xray MIPS VLESS REALITY

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • Confirm the exact model and board revision; results for the R2100/MT7621 do not apply automatically to other Xiaomi routers or hardware revisions.
  • A version-check timeout only shows that the check did not finish as expected. It does not by itself prove that sing-box is incompatible or that the router lacks capacity.
  • If you choose Xray for VLESS/REALITY on this R2100/MT7621 target, verify that the MIPS soft-float build matches the exact KWRT firmware ABI; a matching name alone does not prove compatibility.
  • Test wired TCP and UDP, 2.4 GHz and 5 GHz TCP routing, and reboot recovery separately; a running core or working explicit SOCKS proxy does not prove transparent routing.

Confirm the model and the failing layer

Confirm the full model, board revision and installed firmware from the device label and system page. This guide targets the Xiaomi R2100 with MT7621 and 128 MiB of memory. Similar-looking devices from the same vendor can use different CPU architectures, flash layouts and wireless chips, so do not copy a core binary or upgrade method based only on the brand.

A sing-box version-check timeout can occur while requesting version information, downloading a file or checking core startup. Record the interface message, core logs and most recent configuration change. Then check device connectivity, DNS, system time, the download source response and local file state separately. One timeout message does not identify the cause.

Read the device architecture, memory and storage

Check the architecture reported by the system and the package target, then inspect available memory and overlay space. These readings describe only the sampled state. A router still needs resources for the system, DNS, firewall and wireless services after the proxy core starts. Do not guess the required build from a binary name used on another router.

The commands below only read system information; they do not install software or change settings. BusyBox and OpenWrt versions may format the output differently. If opkg is unavailable, check the package architecture in the firmware system information. Remove device names and custom firmware labels before sharing output.

Read the architecture, memory, storage and system time

sh
uname -m
opkg print-architecture
free -m
df -h /overlay
date -R
Run in a shell on the target router. These commands only read information. Use the firmware's system information and supported package architecture as the reference; this output does not prove flash compatibility.

Separate a version-check timeout from core compatibility

Determine whether the timeout occurred during the version request or while checking the core file. Check that the system clock is reasonable, the router can resolve the download host, HTTPS to the trusted release source connects and the failure log explicitly reports a file-format or execution-architecture error. If the log only reports a request timeout, it does not establish that the built-in sing-box core is incompatible with the CPU.

Use the failure layer and logs to guide the next check. If the request or download still times out, investigate name resolution and the router's connection to the release source. Investigate the core ABI only when logs explicitly report a file-format, instruction-set or execution-architecture error. Do not change the core, DNS, MTU and download source together; test one boundary at a time and keep the previous settings. A network request failure and a binary startup failure are different problems.

Choose a proxy core that matches the firmware architecture

The core must be built for the device's actual CPU architecture, byte order and floating-point ABI, and obtained from a verifiable trusted release. For VLESS/REALITY on an R2100/MT7621 target, MIPS soft-float is the Xray build type to evaluate. Use it only if the exact KWRT version, board revision and package ABI match. A filename containing MIPS is not enough to establish that a binary will run.

Before enabling a core, check the selected PassWall core, generated configuration, dependencies, listeners and ports. VLESS/REALITY client, server and transport parameters must match. Never paste a node address, UUID, private key, short ID, subscription URL or real configuration into a public log or example. If the binary reports an architecture error, restore the prior core selection and find a release that matches the current firmware ABI.

Verify transparent routing separately from explicit proxying

From a test device on the same LAN, send a request without an application proxy setting and a TCP request that should be proxied. Correlate the result with the PassWall rule, connection tracking and actual egress. An explicit SOCKS5 test checks only the SOCKS listener and proxy chain; it does not prove LAN transparent forwarding or per-device routing.

Test UDP separately with an authorized UDP echo service or application protocol. A TCP web page loading does not establish that UDP passes. If the router provides dual-band Wi-Fi, repeat the TCP routing check from clients on both 2.4 GHz and 5 GHz; a wired result does not establish wireless acceptance.

Include reboot recovery in acceptance

After saving the configuration, reboot the target router once and confirm that management access, WAN/DNS, wireless, the proxy core and routing rules return as expected. A pre-reboot check does not replace post-reboot client requests; a device that boots is not necessarily connected to its node or using the correct egress.

Do not infer sustained load, peak throughput, IPv6 transparent proxying or power-loss recovery from a core starting or a few successful requests. If those capabilities matter, measure them separately on an exactly matching device and firmware and record the conditions. Before relying on OEM recovery, locate the official instructions for the exact model and confirm the required physical access. Do not promise that every flash failure can be recovered by a generic method. If the core fails to start or management access is lost, follow the official recovery information for that model and restore a known-good configuration before making another change.

Sources

Frequently Asked Questions

Does a sing-box version-check timeout mean the R2100 does not support sing-box?

No. First determine whether the version request, download or core startup check failed. A network timeout is not proof of binary architecture incompatibility.

Does using Xray MIPS soft-float on one R2100 mean another MIPS core will work?

No. Byte order, floating-point ABI, firmware dependencies and hardware revision must also match, and the release source must be verified.

Does explicit SOCKS5 access prove that PassWall transparent proxying works?

No. It checks the SOCKS listener and that proxy chain. Verify transparent TCP/UDP routing and the actual rules from a LAN client separately.

Does a working web page prove UDP forwarding works?

No. Test UDP separately with an authorized echo service or a real UDP application protocol.