mirror of
https://github.com/EasyTier/EasyTier.git
synced 2026-10-27 00:00:15 +00:00
79dd97dd7f
* fix(wasi): advertise the compiled smoltcp stack and keep ring out of the guest A WASI guest has no OS TUN device, so the TCP subnet proxy can only forward through the user-space stack. The capability probe in the WASI runtime only set smoltcp_available under wasm-host-tunnel-outbound, so a plain core build left force_smoltcp false and the proxy fell back to the kernel-listener path, which rewrites the SYN onto a device that does not exist and lets every entry expire as "syn nat entry expired". - Add CoreInstanceHostConfig::set_smoltcp_stack and call it from the WASI runtime whenever the stack is compiled in. The setter only raises the flag, so the host-tunnel mode keeps working independently of the feature. - wasi-crypto-offload no longer pulls ring-crypto: the host performs AEAD for the guest (easytier_host.crypto_aead_seal/open), and a software backend adds no value inside WASI. - build-wasi-core.sh now builds with --no-default-features and an explicit list. endpoint-discovery was the only default that pulled rustls/ring; ring compiles C shims for wasm32-wasip1 that surface as env.ring_core_* imports, which the Go host cannot provide. Covered by two unit tests for the setter. * style(wasi): remove extra blank line from runtime module Remove the extra blank line at the end of the WASI runtime module. This restores the repository-wide cargo fmt check for PR #2734. --------- Co-authored-by: 刘金发 <liujinfa9242@dingtalk.com> Co-authored-by: KKRainbow <5665404+KKRainbow@users.noreply.github.com>