Skip to content

Telemetry and auto-connect

SRS needs current IL-2 telemetry to identify the player, coalition, aircraft, and multiplayer SRS server. The game sends this data to the SRS client on UDP port 4322.

If Server and VOIP are green but IL-2 is gray, SRS has reached the radio server but is not receiving fresh game telemetry. This is not an SRS server outage. If a VPN is running, check VPN software first.

If all connection indicators remain gray, first verify that SRS has a valid server address and that your network can reach it.

  1. Close IL-2.
  2. Start SRS.
  3. Open Help → Telemetry Diagnostics.
  4. Run the check and use the offered repair action if a problem is found.
  5. Restart IL-2 after a repair.
SRS Telemetry Diagnostics window ready to run a check

The diagnostics inspect both Great Battles and Korea when they are installed. They verify the telemetry section in each startup.cfg, check port ownership, inspect known third-party telemetry applications such as IL2WinWing, and report relevant Windows Firewall state.

The completed report identifies each detected game installation and clearly marks successful checks, warnings, and repairs:

Completed SRS telemetry report for Great Battles and Korea

SRS needs an enabled telemetry target using port 4322. Additional telemetry applications must use separate endpoints when they cannot reliably share the same UDP listener.

Do not replace unrelated startup.cfg settings. The built-in repair preserves unrelated content and encoding, backs up the original before its first change, maintains a known-good recovery copy, and restores a read-only attribute after updating the telemetry section. If the file is missing, empty, or incomplete, SRS refuses to modify it and offers to restore a valid backup while IL-2 is closed.

Allow IL2-SR-ClientRadio.exe on both Private and Public Windows Firewall profiles. Multiplayer networks can be classified differently from a user’s normal home network.

If Windows previously displayed a firewall prompt and only one network type was selected, use Telemetry Diagnostics or Windows Defender Firewall settings to correct the application rule.

Some VPN clients block or redirect the local traffic that IL-2 uses to send telemetry to SRS, even though both run on the same PC. SRS then does not detect that IL-2 is running and the IL-2 indicator stays gray. Telemetry Diagnostics may still report that everything is set up correctly, because the game configuration itself is fine.

To check whether your VPN is the cause:

  1. Disconnect the VPN.
  2. Restart IL-2.
  3. Check whether the IL-2 indicator turns green.

If it does, look in your VPN’s settings for an option that keeps local traffic working while connected. Names vary between VPN apps; look for local network (LAN) access, the VPN’s own firewall or kill switch, or split tunnelling. With split tunnelling, exclude the game (Il-2.exe for Great Battles, IL2Series.exe for Korea) and IL2-SR-ClientRadio.exe. If your VPN has no such option, disconnect it while flying with SRS.

Force-feedback and hardware tools can also consume IL-2 telemetry. SRS and IL2WinWing should not both attempt to own UDP port 4322. Use Telemetry Diagnostics to apply the supported split-port configuration instead of manually guessing port values.

SRS confirmation for configuring IL2WinWing compatibility

If the IL-2 indicator remains gray, send support:

  • a screenshot of the complete Telemetry Diagnostics result
  • the relevant game’s startup.cfg
  • clientlog.txt from the SRS application folder, captured while IL-2 is running
  • the game edition and whether it is Steam or standalone
  • whether a VPN, and which one, was running

Use the Report a Problem button on the Help tab so the report includes the correct project and support destination.