I’m unsure what limitation wouldnt allow this, I bind nearly all my game servers to 0.0.0.0 including other source games. Without the ability to bind to 0.0.0.0 my server is unable to connect to steam so no item servers. My networking is setup such that Game Server > Tailscale > VPS then VPS(through prerouting) > Tailscale > Game Server. I would really like to have the functionality to bind the ip to 0.0.0.0 or if you can inform me of some way to work around this. Thanks!
Reproduction Steps
Create new tf2 instance.
Set “Application IP Binding” in “Network and Ports” to 0.0.0.0
Attempt to start instance.
Instance will fail to start and state IP cannot be set to 0.0.0.0 or loopback address.
AMP requires binding to a specific IP for all srcds/hlds servers so that the UDP logger is able to work with the server and AMP can receive server console output
This has been the case for years in AMP
Why doesn’t binding to the local Tailscale interface IP work for you?
Binding to just the tailscale interface causes the server to be unable to connect to the steam item servers. Other players can connect and play on the server though, just without items. I’ve made sure port 26900 is open just like 27005 & 27015 as it recommends in ( Source Dedicated Server - Valve Developer Community ) and have tried adding “-sport 26900” to “Additional Command Line Parameters”.
I previously was able to bind to 0.0.0.0 when using lgsm and that would solve this issue.
Im essentially using tailscale as a bridge to a simple vps to get around the cgnat of my isp for my home server.
So
Home Server <> Tailscale <> VPS w/ Public IPv4
Error for connection to the steam servers is:
”Could not establish connection to Steam servers. (Result = 3)”