Closed 46620 closed 6 months ago
Try capturing WAN traffic via tcpdump on the host(!) system, not inside the docker container itself.
tcpdump -i eno1 port '(2456 or 2457)'
(Replace eno1 with your actually ethernet interface)
You should see something like the following:
21:14:47.935272 IP 123.123.123.123.39749 > 192.168.178.95.2456: UDP, length 1
21:14:47.936338 IP 123.123.123.123.39749 > 192.168.178.95.2456: UDP, length 1
21:14:50.277664 IP 123.123.123.123.56243 > 192.168.178.95.2457: UDP, length 1
21:14:50.277664 IP 123.123.123.123.56243 > 192.168.178.95.2457: UDP, length 1
If that is not the case, then your router is not properly forwarding the specified ports.
tcpdump doesn't show anything. The default docker container that comes with the dedicated server files from steam works for hosting the game so I don't think it's the router not forwarding the ports, as people can join when I run that.
Tried this again recently and it seems to just work now. Seems to have just been an issue on my system that is no longer an issue.
I've been attempting to set up a server and every time I start the container I can connect using the local IP of the server, but I can't connect using my public IP.
Running the command
sudo netstat -anpe | grep "2456" | grep "LISTEN"
brings up nothing, but removing the LISTEN grep I getSome info about the setup:
docker-compose.yaml