9999 ping for all servers on ubuntu/proton

[fossil bay]

github.com/ValveSoftware/Proton/issues/938#issuecomment-2597039636

my message keeps getting deleted but here is a link to the github issue with proton logs

LogSquadOnlineServices: Icmp ping failed, FIcmpEchoResult: 4, Reported Ping: -1.000000
273390.301:0188:018c:warn:seh:OutputDebugStringA "[2025.01.16-22.42.09:354][418]LogSquad: Warning: SQFindSessionsCallbackProxy: Failed to ping {7th} 7th Rangers - Operation Quicksilver, defaulting to MAX_QUERY_PING\r\n"
273390.301:0188:018c:trace:seh:dispatch_exception code=40010006 flags=0 addr=00006FFFFFC1CF07 ip=6fffffc1cf07
273390.301:0188:018c:trace:seh:dispatch_exception  info[0]=00000000000000a7
273390.301:0188:018c:trace:seh:dispatch_exception  info[1]=000000002f55e2a0
273390.301:0188:018c:warn:seh:dispatch_exception "[2025.01.16-22.42.09:354][418]LogSquad: Warning: SQFindSessionsCallbackProxy: Failed to ping {7th} 7th Rangers - Operation Quicksilver, defaulting to MAX_QUERY_PING\r\n"

obviously I don't have 9999 ping when I join the server but this makes finding a server with good ping annoyingly difficult

it used to work just fine until the update to epic servers and has been broken since

[clever pasture]

What proton version are you using?

[lofty needle]

I have the same issue

[gentle mortar]

Problems with ur internet connection, check it

[lofty needle]

My internet connection is fine...

[fossil bay]

nothing to do with internet connection, it's an issue with the game on linux

[fossil bay]

attached logs are Proton: 1736791942 experimental-9.0-20250113, but the problem persists even on the latest proton version

[gentle mortar]

This issue usually occurs after technicall work has been carried out on the network. The problem can be fixed by restarting the router and loggind out of steam, followed by logging back in(several times)

[fossil bay]

chat gpt response? that's not the solution and the logs clearly show this is a linux specific issue

[gentle mortar]

Solution from Russian servers

[fossil bay]

well I can tell you the problem has nothing to do with my connection, as shown by multiple linux users reporting it, and I myself have completely wiped and reinstalled linux multiple times and bought a completely new computer since it first occurred and even changed my internet service provider after moving. the problem still persists and is obviously a proton compatibility issue the devs need to fix

[clever pasture]

Last week I tried to play Squad on Fedora 42 and i didnt have any ping issues.
Any proton was working.

[fossil bay]

most likely only affects debian based, @lofty needle are you on a debian based linux?

[split lance]

I think it has something to do with ICMP being blocked via default on Linux.

[vast swallow]

I'm on arch and I don't have this issue, so definitely something to do with ubuntu and its derivatives

[vast swallow]

ICMP is blocked for incoming requests by default, but not for outgoing, so that wouldn't be the issue this time around.

otherwise the ping command would never work 😉

[split lance]

EOS use's ICMP for ping for servers, it may use the same for client.
So EOS would have to ping client to get response.

Might be worth trialing

[vast swallow]

well it would be the client sending the ping to the server, not the other way around

99% of home routers block incoming requests anyway, so it wouldn't be a problem unique to linux, nobody would be getting the correct pings