topic Re: URL category for anydesk in Next-Generation Firewall Discussions

URL category for anydesk

Carracido — Wed, 14 May 2025 09:49:37 GMT

Hi community!

I´m trying to create a url custom category that matches Anydesk traffic so I can decide what non-decrypt rule anydesk is using.

In the URL filtering logs I only see the url anynet%20relay:6568 and I tried to create a custom category with that url but it doesn´t seem to match.

I have followed also the suggestions from this discussion without success:

https://live.paloaltonetworks.com/t5/general-topics/solution-for-quot-ssl-decryption-bypass-for-anydesk-quot/td-p/385369/page/2

It seems there´s a limitation with the token separators that Palo Alto offers:(. / ? & = ; +) and you cannot create an expression to match urls like anynet%20relay:6568.

Does anyone has a suggestion on how to create an expression that can match urls like anynet%20relay:6568??

Many thanks in advance!

Re: URL category for anydesk

reaper — Wed, 14 May 2025 10:54:45 GMT

%20 is a blank space which doesn't make sense in a URL

according to anydesk you'd need to use *.net.anydesk.com as FQDN and ports tcp/80, tcp/443 and tcp/6568, and udp/50001–50003 for discovery

https://support.anydesk.com/knowledge/firewall

Re: URL category for anydesk

Raido_Rattameister — Wed, 14 May 2025 13:09:50 GMT

Anydesk does use spaces and %20 in URL so add also those:

*.net.anydesk.com/

AnyNet Relay

anynet%20relay:80/

anynet%20relay/