Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fortiguard identifies and blocks Wireguard #1586

Open
TarekSalama opened this issue Sep 16, 2019 · 2 comments
Open

Fortiguard identifies and blocks Wireguard #1586

TarekSalama opened this issue Sep 16, 2019 · 2 comments

Comments

@TarekSalama
Copy link

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?

@TC1977
Copy link
Contributor

TC1977 commented Sep 30, 2019

What if you change the Wireguard port to 1194 (Open VPN) or 443 (https)? Or something completely random?

@TarekSalama
Copy link
Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants