I think I asked this question previously in another issue thread, but I never received a response.
When setting up a remote client connection, one of the parameters is the IP address. Many or most networks today use DHCP to manage IP addresses. So it’s possible (probable?) that if a remote client is rebooted, when it comes back on the network, the client it will have a new IP address.
It appears that Glasswire cannot correct for this. On my remote machine, I was not able to establish the remote connection with the original IP addr I used in setup after that machine was rebooted. I had to go in the Settings on my Glasswire client again and change the remote IP addr to the new DHCP assigned IP addr. And, of course, this required that I first determine on the remote machine what that new IP addr was.
This is manageable, but is still a rather significant limitation on the Glasswire Remote Connection. Am I correct in this observation? And is there anything Glasswire can do to pick up a change DHCP assigned IP addr and continue the remote connection activity?