You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I was lucky enough to be able to test Wireguard with Fortiguard installed on the network.
Fortiguard was able to completely disable Wireguard.
I did notice however that it sometimes identified it as a proxy (Wireguard) and sometimes it identified it as an AWS app (where I host it). I did notice also that it sometimes worked and sometimes it worked only after reconnecting to the network. I couldn't find an exact pattern.
Is there a way to completely hide it from getting identified by Fortiguard? Any idea why it was sometimes identified as a proxy/AWS app?
The text was updated successfully, but these errors were encountered:
I am not really experienced with networking but is it possible to change it using Algo?
I know I can probably change it in the server script configuration file but would I need to change anything in the device config files that get auto generated?
So I was lucky enough to be able to test Wireguard with Fortiguard installed on the network.
Fortiguard was able to completely disable Wireguard.
I did notice however that it sometimes identified it as a proxy (Wireguard) and sometimes it identified it as an AWS app (where I host it). I did notice also that it sometimes worked and sometimes it worked only after reconnecting to the network. I couldn't find an exact pattern.
Is there a way to completely hide it from getting identified by Fortiguard? Any idea why it was sometimes identified as a proxy/AWS app?
The text was updated successfully, but these errors were encountered: