05-18-2015, 01:37 AM
I see most of your questions have already been answered, so I'll just tackle the IP binding. Currently that is not possible, but it shouldn't be too difficult to add in a very rudimentary form. There's a question of plugins, though - we have API available to plugins that can make connections, both client and server, to the outside world, using TCP and UDP. We could enforce the same IP binding globally for the plugins, too, or we could make it a separate setting (server binds to IP1, plugins bind to IP2). Does that scenario make any sense at all from the hosting point of view, or are we allowed not to bother? 
Also we currently bind to both IPv4 and IPv6. If there is an interface specified for binding, I fear that it might force only one of those to be used. Is that acceptable?
Finally, do we need to provide the possibility of multiple specific IPs bound to a single server? Say, for example, you want it to listen on IP1 and IP3, but not on IP2. This would become rather ugly to code.
Also we currently bind to both IPv4 and IPv6. If there is an interface specified for binding, I fear that it might force only one of those to be used. Is that acceptable?
Finally, do we need to provide the possibility of multiple specific IPs bound to a single server? Say, for example, you want it to listen on IP1 and IP3, but not on IP2. This would become rather ugly to code.