FAForever / FAForever/client

Clients on local network are forced through proxy

Open
#588 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
78
Forks
89
Avg merge
22d 15h
Merged PRs (30d)
1

Description

I experienced clients on my local network being rerouted through the in-game proxy if ports are not forwarded. If ports are correctly forwarded, no connection is established.

This can be reproduced by having two clients on the same LAN with appropriate ports forwarded (192.168.1.x1 has port 6112 forwarded while 192.168.1.x2 has 6114 forwarded). Have 192.168.1.1x host a game that 192.168.1.x2 attempts to connect to. Make sure that the client has been restarted.

If the ports are not correctly forwarded, (e.g. both clients are attempting to use 6112 and neither is forwarded) the game simply chooses a proxy to connect the two. This results in poor connection latency (300+ ms) and regular disconnects in game.

I expected the client to automatically use local connections when available. If 192.168.1.1x gets a connection request from 192.168.1.2x, it should attempt to use local connections first. Using the local network instead of bouncing off of an external server would improve network performance.

In short, the client currently ignores local network connections and requires a proxy for two or more players on the same network to play together.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.