[FEATURE] Networking custom IP about arkascendedservermanager

[JensvandeWiel]

as long if it is its own/virtual interface you should be able to use the ip

[flames]

Yes, i am using 0.0.0.0 currently. I see the connection stack is different in ASA vs ASE. Strange thing is, when i start the server w/o manager, it is nearly instantly visible in the game lobby. This is what made me think, that ASA server propagates the configured IP address to Epic, as ASE servers did with Steam (there was exactly that behaviour, when you don't propagate the real WAN IP to steam, it took up to 10 minutes after server start until it was visible/joinable via Steam or game lobby.
To avoid misunderstanding, my interface IP != WAN IP, it is a 1:1 NAT WAN IP -> server interface IP + outbound NAT server interface IP -> WAN IP. when i curl icanhazip.com on the server, it returns the corresponding WAN IP which is bound to the server, not my main WAN IP (as said, i have multiple WAN IPs, but those are not the interface IPs of the server, there is still NAT).
To check, if my assumption is right or wrong, i will test it soon with binding to the interface IP, instead of any.
Closing this Issue. If i can elaborate something more, will reopen it. Thanks!

[flames]

Ups, can't close my self :)