T5 Server is unable to bind to another interface

[BaconBrad]

Hi guys

Decided to setup a T5 server today finally... only been 4 years since I first started with T6!

My question was that the argument net_ip does not seem to work with T5 servers to specify which address/interface it should bind to?

command line
.\bin\plutonium-bootstrapper-win32.exe t5sp "serverfolder removed" -dedicated +set key "removed" +set net_ip 0.0.0.0 +set net_port 28960 +set sv_config fivezm.cfg

I have a P2P tunnel running on the VM where the servers are hosted and I need to bind the T5 server to another address or all available addresses (0.0.0.0) however the T5 server keeps wanting to use the machines IPv4 address from its other interface which is also behind NAT but not usable in my scenario for example during startup this will be displayed "Binding to 192.168.1.136:28960".

I need to bind the server to 10.x.x.x range as that is where the ip tunnel is running, I have no issues with T6 so am suspecting that potentially T5 does not have this capability for whatever reason.

Again it will always use the machines 192.x.x.x NAT address no matter what I specify in the command line e.g. +set net_ip 10.3.0.6 or +set net_ip 0.0.0.0 etc

Hopefully one of the smart cookie devs/admins can kindly advise?

Cheers
Brad

[Xerxes]

IIRIC it should bind to all interfaces already but prints the first one and uses the default one.
But I don't have a set-up I can use to re-create it.