VirtualHere Client Interface Binding

Submitted by Omegawkd on #1

Hi there,

I know it is possible to bind the server to a specific interface.

Is it possible to also bind the client - Windows in this case, to a specific interface.

I have a use case where my system has 3x network interfaces and I need to stop the software sending Multicast packets on all of them --- it actually sends out on the first (or wrong one) and the server does not honour the request [as it is listening on a different VLAN as such].

Now, I know I can just the block the outbound traffic on those other two interfaces --- and I did this and it works, but it would be more ideal to be able to bind the client software to an interface and have it only communicate on that interface.

Thanks for your time.

Submitted by Michael on Thu, 2024/09/05 - 06:23

#2

You can uncheck Auto-Find hubs and then manually specify the IP address of the particular virtualhere server.

 

Submitted by Omegawkd on Thu, 2024/09/05 - 18:09

#3

Hi there,

Thanks for coming back to me.

Yes, I note I can do this but that is not what I need.

I still need the Auto-find feature to work but need to be able to tack it to a specific interface only; it woould be ideal to be able to set it to listen to an interface just like the server.

Submitted by Michael on Thu, 2024/09/05 - 18:55

#4

OK, there is no way to send a multicast lookup on a particular interface in the client. This is because usually you can just directly put the IP address of the server into the client and that would use that particular network interface to communicate on.