Most likely a duplicate of the various network reconnect issue reports already open like #971.
Hello @ElementW, per "Improved the client's responsiveness to network changes" in the 2019-05-15 Steam client beta update and https://github.com/ValveSoftware/steam-for-linux/issues/474#issuecomment-492855274 / https://github.com/ValveSoftware/steam-for-linux/issues/474#issuecomment-493182264, please opt into Steam's beta client and retest this issue.
Closing as fixed.
Alright, this is a pretty specific one.
Your system information
pacman -Syutime)Please describe your issue in as much detail as possible:
I sometimes am in a situation where I switch between Wi-Fi and 4G tethering, where the former is slow but unmetered and the latter fast but metered.
This induces a change in the routing table, which Steam seems to not be able to deal with ; all connection to Steam servers appear severed (and consequently downloads cannot be resumed, and games like TF2 can't join servers) until the client is restarted or network comes back on the network interfaces Steam used when started.
This issue has been experienced with both NetworkManager (commonly used on Linux distros) and Intel's
connman(my daily driver network manager), so it's not related to network manager-specific shenanigans.Changes to the routing table are trivial for a network switch (using
connman):4G tether:
Wi-Fi:
Steps for reproducing this issue:
Most other software seem to handle the network switch just fine. Obviously existing connections get broken (with the exception of the very few things supporting mid-session connection change/re-auth (like
mosh), or SCTP), but background software quickly and automatically re-establish theirs to not cause user inconvenience (e.g. Telegram).