tame mulch
My geolocation of the dedicated server and clients are US based.
When the relay connection is established to Russia servers this introduces latency that is unplayable for combat type mechanics.
My firewall has windrose.support wildcarded allow.
In this example my client is connecting to my dedicated server (both have same external IP).
Normally this connects to the eu/us based relays and latency is fine
However this afternoon I see in server logs I see connecting to coturn-.windrose.support
R5LogIceProtocol: [1260894] R5P2p::R5IceConnection::R5IceConnection [734005af69aa4a09891a279e7848d07c] Create R5IceConnection. TransportType TCP. IceControlling true. IsRelayOnly false. UseLocalhostOnly false. CoturnServer coturn-.windrose.support:3478;
...
R5LogIceProtocol: [1260907] ...Connection::BuildTurnProtocolAsync::<lambda> [734005af69aa4a09891a279e7848d07c] Add Relay Ice Candidate: TCP 155.212.169.178:54751 9c4856410e345abe4cf024ee537c82a5 16777215 relay raddr (not showing my IP) rport 42539
Pinging 155.212.169.178 with 32 bytes of data:
Reply from 155.212.169.178: bytes=32 time=134ms TTL=46
I do not want the my client to connect to coturn-.windrose.support
I tried blocking coturn-.windrose.support on my firewall but this prevented my client from connecting to my server at that time.
Besides I (others) generally try to block any ru traffic
Maybe the api server for US was down at the time?
Trying again 15min later? resulted is the faster "normal" IP.
R5LogIceProtocol: [1315367] ...Connection::BuildTurnProtocolAsync::<lambda> [d7d0c9fc782b45f6b1010d11d231c621] Add Relay Ice Candidate: UDP 18.198.170.147:24892 9923bf94d5a7138488216ec6189363b6 16777215 relay raddr (not showing my IP)rport 50111 [D:\Source\Build\work\gameRepoCheckoutDir\Plugins\R5BusinessLogicCore\Source\R5P2pGate\Cpp\IceProtocol\R5IceConnection.cpp:1484]
I realize direct IP is a workaround/solution but maybe there's a bug here.
lapis wharf