6 commits

Author	SHA1	Message	Date
heinrich5991	89a4a0c5c6	Only compare with old STUN server address if we have any	2022-07-10 16:53:15 +02:00
heinrich5991	92f27bdb30	Don't periodically retry STUN if successful ... Trying again for each connection establishment is enough. Previously, it was re-requested every 10 minutes. Fixes #5273.	2022-05-31 17:53:11 +02:00
heinrich5991	71d47c3329	Log send errors with debug instead of error severity ... They're normal in case a protocol stack isn't initialized supported by the host or if there's no route. CC #5273	2022-05-31 17:49:11 +02:00
Dennis Felsing	e31fa7051e	Fix clamp in CStun::Update (fixes #5282)	2022-05-31 13:31:43 +02:00
def	3116494f6e	Fix some uninitialized variables, found with valgrind	2022-05-22 12:18:49 +02:00
heinrich5991	4fb050ccb7	Use STUN to determine UDP connectivity and show diagnostics ... These diagnostics are supposed to guide the user to problem resolution. They're displayed if no packet is received from the server within one second of connecting. No message if we don't have STUN servers. "Trying to determine UDP connectivity..." if no answer has been received from the STUN server yet and it hasn't timed out yet. "UDP seems to be filtered." if the STUN request has timed out. "UDP and TCP IP addresses seem to be different. Try disabling VPN, proxy or network accelerators." if the STUN request has returned an IP address different from the one obtained via HTTP from info2.ddnet.tw. "No answer from server yet." otherwise, if the STUN request has returned no interesting data, indicating that it's likely the game server's fault.	2022-05-18 09:21:31 +02:00