Post by saltius on Sept 3, 2020 22:06:21 GMT -5
About Cluster travelling within LAN.I've digged a few threads and concluded as follow:
To perform cluster travelling within LAN, the clients should connect the server using its external IP other than internal LAN IP.
And to make that kind of connection possible, the router should have NAT loopback function enabled and port forwarding set correctly.
What I found myself is all these above are only for steam clients.
For epic clients, it is a different story.
They can perform cluster travelling within LAN as long as cluster ID/Server port set correctly, nothing more is required!
And when epic client users go to ob or supply crate and click server transfer button, they got server list with filter(and will list all server within LAN, though one may need to wait a bit longer) not like steam clients got cluster server list(no server would show up if client connect within LAN). That is the difference.
I doubt Wildcards may fix this issue of epic client to make LAN players miserable.
To perform cluster travelling within LAN, the clients should connect the server using its external IP other than internal LAN IP.
And to make that kind of connection possible, the router should have NAT loopback function enabled and port forwarding set correctly.
What I found myself is all these above are only for steam clients.
For epic clients, it is a different story.
They can perform cluster travelling within LAN as long as cluster ID/Server port set correctly, nothing more is required!
And when epic client users go to ob or supply crate and click server transfer button, they got server list with filter(and will list all server within LAN, though one may need to wait a bit longer) not like steam clients got cluster server list(no server would show up if client connect within LAN). That is the difference.
I doubt Wildcards may fix this issue of epic client to make LAN players miserable.