How to restrict ignite not to use some network interfaces while communicating

[kagrawal-tibco]

Hi team, we are using TcpDiscoveryVmIpFinder for node discovery :
In one of the Usecase :
There are multiple network interfaces(primary and backup or public and private IPs)
Now when we start server and client nodes on different machines and one of the Server node cannot join a cluster because the server tries to connect with the IP of the backup network (port seems blocked by a firewall).

Note that the backup IP is not part of discovery URL though. Can we restrict ignite not to listen to some ips in the network.

[ptupitsyn]

Please share config files and exception details

[kagrawal-tibco]

We have basic config file attached and there is no exception as such but can see request sent from to backup interface
Below is example the 192 is IP from backup interface.
netstat -an|grep 7401

tcp6       0      0 10.x.x.x:7401        10.x.x.x:32929       ESTABLISHED
tcp6       0      0 10.x.x.x:7401        10.x.x.x:47303       ESTABLISHED
tcp6       0      0 192.168.x.x:7401      192.168.x.x:50423     ESTABLISHED
tcp6       0      0 10.x.x.x:47303       10.xx.x:7401        ESTABLISHED

Uploading configIgnite.txt…