Factorio Forums

I have requested assistance in the technical help forum but as far as I can tell, it's an issue outside of my network.

I can host a hidden server perfectly. I provide the IP to someone and they can join.
I can host a public server but with faults. The server will show in the public matchmaking list but no one can join from the matchmaking list. However, if someone uses the direct IP, it works flawlessly, just as a hidden server would.

Please refer to this post to see logs and what I've attempted.
viewtopic.php?f=49&t=33964

Thanks!

Please upload (not post the content) the complete log-files of host and peer after an unsuccessful connection attempt.

Loewchen wrote:Please upload (not post the content) the complete log-files of host and peer after an unsuccessful connection attempt.

I started the server and waited for it to be ready. Then went to my client, started it up, searched for the server and attempted connection. I then closed the client, and then gracefully shut down the server.

Here are the resulting logs:
Client: Server:

This looks similair to this problem @ Technical help forum.
viewtopic.php?f=49&t=33964

EDIT: it is the same, derp.

This is the part that is relevant:

xBlizzDevious wrote:I have requested assistance in the technical help forum but as far as I can tell, it's an issue outside of my network.

I can host a hidden server perfectly. I provide the IP to someone and they can join.
I can host a public server but with faults. The server will show in the public matchmaking list but no one can join from the matchmaking list. However, if someone uses the direct IP, it works flawlessly, just as a hidden server would.

Please refer to this post to see logs and what I've attempted.
viewtopic.php?f=49&t=33964

Thanks!

Hi, this looks like you are behind a NAT that is not automatically traversable by Factorio. How exactly do you determine the IP that you give to people manually? Does it include setting a forwarded address on your router?

So I've read the other topic, and it really looks like problems with cone NAT like impetus maximus said. Problem is, that Factorio doesn't know you have forwarded the port and tries to go through the NAT on its own, which fails for this type. A workaround would be to make an option "my external address is <some address> and I'm certain about it" that would override the whole pingpong server fun. Any ideas on where to best set it?

cube wrote:-snip-
Hi, this looks like you are behind a NAT that is not automatically traversable by Factorio. How exactly do you determine the IP that you give to people manually? Does it include setting a forwarded address on your router?

cube wrote:So I've read the other topic, and it really looks like problems with cone NAT like impetus maximus said. Problem is, that Factorio doesn't know you have forwarded the port and tries to go through the NAT on its own, which fails for this type. A workaround would be to make an option "my external address is <some address> and I'm certain about it" that would override the whole pingpong server fun. Any ideas on where to best set it?

Specifically, I use dtdns.net for a dynamic domain name, that is hooked to my non-static IP. I have a pfSense router that has 34197 (modded, private server) and 34198 (vanilla, public server) forwarded to the computer that hosts the server.

I'm not sure what "cone" NAT is. I assume it's the way in which it does the address translation?
As for the absolute address setting - if you're asking me - I'd suggest either the config.ini for client or server support or in the server-settings file.

Is there some sort of workaround I can do? In the other thread, it was suggested that I set an outbound NAT rule but that only caused more confusion, returning a 0.0.0.0 IP.

And thanks for looking into this.

found a video about disabling auto handling of outbound NAT in pfSense v2.1.3 here. worth a shot.

So I'll try to add these options in 0.15. In the meantime you can try fiddling with your router settings so that packets from your_computer:34198 exit the router at public_ip:34198 (and there is a corresponding forward from public_ip:34198 to your_computer:34198).

impetus maximus wrote:found a video about disabling auto handling of outbound NAT in pfSense v2.1.3 here. worth a shot.

THANKS! I thought that this is what I did, but obviously not as I just tried it again, following this video and it works perfectly.

cube wrote:So I'll try to add these options in 0.15. In the meantime you can try fiddling with your router settings so that packets from your_computer:34198 exit the router at public_ip:34198 (and there is a corresponding forward from public_ip:34198 to your_computer:34198).

This will be handy for anyone else having the same issue as me. Thanks for looking into it! The fix above works so for now I shall use that.

so you got the server working?

impetus maximus wrote:so you got the server working?

Yes, I did.

excellent