When trying to use the Wiresock VPN Client service and also when trying to run Wiresock as a process, the application works temporarily before exiting. Running the process with log-level all gives no errors, and the Windows Event Viewer provides no additional details to the reason for the service exiting. How can I diagnose this problem?
Hmm, I suspect that this termination may be due to the panic of the Boringtun library on some particular network packet. Could you collect and share the pcap files by running the Wiresock with -log-level all until the application unexpectedly exits?
For those facing a similar issue, check the MTU configuration setting. As a rule, it should not exceed 1420 bytes (1440 bytes for IPv4 only tunnels), specifying a larger value, such as 1500, results in the behavior described above.