WireGuard stop working after serval hours

[jwfang]

Operating system

Linux

System version

Linux sing-box 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 Linux

Installation type

Original sing-box Command Line

If you are using a graphical client, please provide the version of the client.

No response

Version

sing-box version unknown

Environment: go1.22.1 linux/arm64
Tags: with_gvisor,with_quic,with_dhcp,with_wireguard,with_ech,with_utls,with_reality_server,with_acme,with_clash_api
Revision: 7fd9abe802d5e22c20b46dcfc9e1bafa71f28f63
CGO: disabled

Description

I have CloudFlare Warp and VPS WireGuard outbands, but all stop working after serval hours.

This is unrelated to #1415 , which may caused by stale local bound IP. I can confirm the bound IP are valid. After selecting WireGuard outband or health-checking for it, there are packets back and forth from server-side, but only with fixed length 148 and 92, as follows from tcpdump:

xxx.39380 > yyy.444: UDP, length 148 yyy.444 > xxx: UDP, length 92

Reproduction

Just create a configuration with WireGuard outbound with system_interface: false, and wait for serval hours.

Logs

No response

Integrity requirements

• [X] I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
• [X] I confirm that I have provided the server and client configuration files and process that can be reproduced locally, instead of a complicated client configuration file that has been stripped of sensitive data.
• [X] I confirm that I have provided the simplest configuration that can be used to reproduce the error I reported, instead of depending on remote servers, TUN, graphical interface clients, or other closed-source software.
• [X] I confirm that I have provided the complete configuration files and logs, rather than just providing parts I think are useful out of confidence in my own intelligence.