Linux porting

[zelytra]

Description of needs

Make BetterFleet work on Linux distributions. This feature is not in development (yet) and is still in discussion

Tasks

• [ ] Generate Linux image with SOT running on it to test @zelytra
• [ ] Tauri adaptation to generate Linux installer @zelytra
• [ ] CI/CD adaptation to handle Linux release @zelytra
• [ ] Change the method to retrieve UDP connection on Linux distro @dadodasyra

Notes

This issue may be splited into multiple MR

[zelytra]

Problem:

When SoT is run under Wine, the wineserver process manages the emulated network stack instead of the game process itself. This complicates determining the specific network port and traffic associated with the game.

Current Method:

1. Use netstat to identify the UDP port wineserver is listening on:

   netstat -4panu | grep wineserver

   Example output:

   udp 0 0 0.0.0.0:32796 0.0.0.0:* 31538/wineserver

2. Use a packet capture tool (e.g., ngrep) to monitor traffic on the identified port:

   sudo ngrep -W single -d any udp and dst port 32796

   Example output:

   U 172.166.255.146:30401 -> 192.168.1.11:32796 [network frame]

3. The need for root permissions to capture packets with tools like ngrep is noted as a limitation.

Challenges:

• Wineserver handles all network-related tasks, so determining which wineserver instance corresponds to the specific game process can be ambiguous if multiple wineservers are running.
• The process requires administrative privileges for packet capture, which may not always be ideal.
• There's a potential for a less specific solution due to Proton's reliance on Wine.

Context:

• Sea of Thieves is available on Windows via two platforms: Steam and the Xbox app. The Xbox app version relies on Microsoft Store DRM, making it incompatible with Linux.
• The Steam version is the only viable option, as it runs with Proton/Wine for Windows-to-Linux compatibility.

Next Steps:

The author suggests exploring Wine documentation to determine if there's a way to link a wineserver to a specific Wine process. Additionally, they note that requiring administrative privileges for packet capture is also the norm on Windows. The discussion leans toward refining the solution for better specificity while acknowledging that the current approach is functional.