So ' service is 'psiphon-tunnel-core.exe' and that service stablished the tunnel with the IP's showed in the logs' shows a connection to 196.245.172.67 , Understood. In regards to ' At the beginning, logs show application psiphon and another IP address with action block' can you show those logs - just the standard firewall log view where we can see the action, the source and destination, the port and the application would be enough. Just wanted to ask meanwhile if someone already was able to do this.įor reference, the enviroment with most updated versions have Management R81.10 with Jumbo 87, and gateways clusterXL R81.10 jumbo 82. My experience with RnD is that it will take some time to get a solution. We already opened a case with TAC and provided debug and packet captures that were already sent to RnD.

I also added Uncategorized category with same results. Full https inspection on the client machine without exceptions.Block SSH Protocol (using the service in R80.10 or the application in R77.X).Tried to block on 3 different enviroments with same results, also have a rule meeting the last requirements i found: But now, i guess the app was updated and firewalls are not able to block Psiphon anymore. I have read all posts related to psiphon, provided solutions worked a couple of years ago. Wanted to ask if someone has been able to block psiphon on 2023.

Psiphon port