yourmate Posted September 28, 2024 Share Posted September 28, 2024 I'm unable to connect to a server on the same network as the client using the in game server menu. I believe this is also preventing me from transferring to another server in the cluster. So far I have found 2 workarounds, joining from an external network using a mobile data connection and with the console command "open Localip:Port?Password". Ark is trying to connect using the servers public ip and the response from the server is coming back to the client from a local ip, could this cause ark to ignore the response? Link to comment Share on other sites More sharing options...
arkark Posted September 28, 2024 Share Posted September 28, 2024 You may need to enable NAT Loopback (also known as hairpinning) in your router, so clients on your network can reach server by using the public ip address. Link to comment Share on other sites More sharing options...
yourmate Posted September 28, 2024 Author Share Posted September 28, 2024 I believe I have NAT Loopback set correctly. The above image shows a packet capture on the client. The server is responding to client, just not from the public ip, which I think is causing ark to ignore it. Link to comment Share on other sites More sharing options...
arkark Posted September 28, 2024 Share Posted September 28, 2024 12 hours ago, yourmate said: I believe I have NAT Loopback set correctly. The above image shows a packet capture on the client. The server is responding to client, just not from the public ip, which I think is causing ark to ignore it. Theorically, NAT loopback should rewrite the headers of the packets so in a wireshark taken from the client you should see connections to and from the public IP. You shouldnt be seeing the lan server address. Isnt there other NAT reflection modes in your router? (apart from Pure NAT) Link to comment Share on other sites More sharing options...
yourmate Posted September 28, 2024 Author Share Posted September 28, 2024 Thanks arkark! You where correct. There was still a NAT Reflection setting that i hadn't enabled. After reading the doc's closer I discovered that I needed to "Enable automatic outbound NAT for Reflection" https://docs.netgate.com/pfsense/en/latest/nat/reflection.html Now the traffic looks like what I am expecting and I can connect with the in game server menu. Link to comment Share on other sites More sharing options...
arkark Posted September 29, 2024 Share Posted September 29, 2024 (edited) 13 hours ago, yourmate said: Thanks arkark! You where correct. There was still a NAT Reflection setting that i hadn't enabled. After reading the doc's closer I discovered that I needed to "Enable automatic outbound NAT for Reflection" https://docs.netgate.com/pfsense/en/latest/nat/reflection.html Now the traffic looks like what I am expecting and I can connect with the in game server menu. Nice! That last image shows how a complete NAT loopback would looks like. The previous mode you had enabled was cheaper (in router CPU usage as it does less packet header rewriting) but modern applications tend to detect that as a security problem (due to a mismatch in the packet srcaddr header) and will not work. Edited September 29, 2024 by arkark Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now