BeatUpServer instance port numbers are currently hardcoded to start at 8106 and count up, leading to issues if multiple instance processes exist behind the same IP address. Further, versatile port assignments may be desirable for more complex hosting setups with containers, network address translation, and whatnot. Ephemeral (auto-assigned) ports should also be supported, however these pose a unique challenge in that upstream firewalls must to be informed of the ports to forward (hole punching was deemed non-viable, as the server isn't necessarily aware of the address a given client will have when connecting to it). Additionally, there should be warnings for attempting to use port numbers which some ISPs are known to block (i.e. 5000, the hardcoded start port prior to 7fff22aca39dfc0879da808aaedd385c96d57304).
BeatUpServer instance port numbers are currently hardcoded to start at 8106 and count up, leading to issues if multiple instance processes exist behind the same IP address. Further, versatile port assignments may be desirable for more complex hosting setups with containers, network address translation, and whatnot. Ephemeral (auto-assigned) ports should also be supported, however these pose a unique challenge in that upstream firewalls must to be informed of the ports to forward (hole punching was deemed non-viable, as the server isn't necessarily aware of the address a given client will have when connecting to it). Additionally, there should be warnings for attempting to use port numbers which some ISPs are known to block (i.e. 5000, the hardcoded start port prior to 7fff22aca39dfc0879da808aaedd385c96d57304).