04-23-2025 08:19 AM
I've noticed when trying to just use the appIDs, any web traffic not able to be identified ("incomplete", "insufficient-data") will hit the policy even though the appID doesn't technically match the policy. My other thought was just to allow the unidentified traffic on 80/443 in a policy just before the deepseek policy but that is not an option (I was thinking after the session got established, it would then start hitting the deny).
I know the new deepseek appIDs have been out for a while but is it still best practice to use those appIDs in conjunction with URL filtering?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
