NAT Reflection Rules or Split DNS for locally-hosted ARK Server?
-
I have a TrueNAS Scale Windows 10 VM running ARK Server Manager (ASM) in which I have two ARK servers in a cluster. The Win10 VM gets an IP assigned by pfSense, and I can access either of the ARK servers using that IP address as a LAN user, but cannot see the other server to travel to from inside the game. Using Pure NAT rules (and automatically creating associated rules), I think I have port-forwarded the necessary ports for both servers correctly, but can only verify the TCP ports are open using canyouseeme.org testing my WAN address. I do see traffic using the pfSense packet capture on both UDP and TCP ports, so I know the traffic is getting through. Both ARK servers show a status of "Available - No Loopback", which means external users will be able to see the other server to travel to, but LAN users will not. I know I must be missing something really simple, but I am just not seeing what it is. Can anyone help me?
EDIT:
Here are some test results, if it helps:
And here are what my rules currently look like: