Also, they may use either HTTP or HTTPS, for no apparent reason. Next session one or both may be different. In the session I have going right now, the machines are .com and.
From the names, it’s clear that these machines are picked by random chance (or some algorithm), so there’s no assurance that you’ll get the same ones from one session to another. You got me pointed in the right direction but with a snag, as you’ll see.Īnydesk opens at two connections to machines in. Kind of takes us back to the question of how to put *. I call this a better workaround rather than a solution because I'll bet Anydesk changes the relay machines' names and addresses on a regular basis for security reasons. For those who might find it useful, I've got this list in the WatchGuard IP address import format and I'd be happy to share it (is there a way to upload a file here?). gives a list of ALL the hosts and their IP addresses in a domain. in those packet filters?Īddendum: I may have found a better workaround. So we have proof of concept but no apparent way to make something operational.Īre there any thoughts on how to actually use *. Indeed, in the next session, Anydesk used a"relay" site that's on a different subnet. Since the names of these Anydesk machines are pretty much gibberish, I have to assume they are picked by some rule that looks like random from here. Luckily, both sites are in 64.31.35.0/24 (64.31.35.22 and 64.31.35.242), so I added HTTP and HTTPS packet filters with this subnet and it did the trick. This is where your idea of packet filters comes in, sort of. After 10 minutes, it dropped and the connection to the host along with it.
The connection to the latter opened when the client machine contacted the host. The former connection opened on the client machine when the program started and stayed open until the program closed. In one session, Anydesk opened connections on port 443 to and port 80 to. It does not publish a list of IP addresses or names for these sites so far I can find. Information from Anydesk says it uses sites on *. That is indeed the key but easier said than done. Set up a packet filter From the client PC or LAN to the domains and ports that AnyDesk uses.
0 kommentar(er)
