Hi,
the parameter host was tolerated in 12/15. In fact it has no effect on the server. IQ was listening on all available interfaces (a netstat will show the 0.0.0.0:port line). Looks like 16 (partially) fixed the host parameter (host parameter it may be used on client side only to specify where the server is located):
I. 01/20 14:03:39. Trying to start TCPIP link ...
I. 01/20 14:03:39. Error parsing passed options - TCP/IP
I. 01/20 14:03:39. Unknown option "host"
[partially - the parameters is still ignored when it has a single value/IP, IQ will listen on all available interfaces/IPs]
The parameter MyIP is used to restrict the listener to the IP(s) listed here. MyIP doesn't allow you to specify the port (the reason why the 3rd test fails). You may use it like in test 2, or list the IP addresses one after another, comma separated:
MyIP=1.1.1.1,2.2.2.2
The same rules goes for the parameter PORT (ServerPort)
The outcome of your configuration is an IQ listening on both IP* addresses, on both ports on each IP:
TCP 1.1.1.1:2638 0.0.0.0:0 LISTENING
TCP 1.1.1.1:9638 0.0.0.0:0 LISTENING
TCP 2.2.2.2:2638 0.0.0.0:0 LISTENING
TCP 2.2.2.2:9638 0.0.0.0:0 LISTENING
(* IP addresses were edited, the ports used in my test were 2638 and 9638)
However, I cannot see how you can combine them, so the server will listen on IP1 on Port1 only and IP2, Port2 only !?!?!?
Dan