reason to not use port 443 also for the vpn connection?

[ne0YT]

Is your feature request related to a problem? Please describe.
form some places tcp 443 is open to the internet, but other ports are not. so it would make life easier to be able to connect to tcp 443 form the netbird clients instead.

Describe the solution you'd like
not only use tcp 443 for the webui but also for the vpn

Describe alternatives you've considered
reverse-proxy

[saule1508]

I am not sure I understand, but from my experience netbird management and netbird signal both can use 443 (grpc) and for coturn you can also use tcp 443 (address will be turns:...:443?transport=tcp. Also if you use the relay functionality it can use https.
But for wireguard itself, I don't know, I think it uses udp and cannot be changed. Maybe this is what your request would do ?
By having coturn listening on tcp 443 we are able to use netbird client on a restrictive corporate environment (behind zscaler)

[mgarces]

hi @ne0YT ; like @saule1508 perfectly described, we already run most of the control layer on TCP 443, but what you are asking is related to Wireguard itself. You can configure your client to run on any port (as long as it's available on your host), but this will be UDP, and on restrictive environments, even if 443 and 80 are allowed (TCP), Wireguard would still be blocked (UDP != TCP). Perhaps the best way you could go around this would be to use UDP 53 (DNS), but again, a restrictive network will probably block all requests to UDP 53 for exact IP addresses (like 1.1.1.1).

[ne0YT]

hi @ne0YT ; like @saule1508 perfectly described, we already run most of the control layer on TCP 443, but what you are asking is related to Wireguard itself. You can configure your client to run on any port (as long as it's available on your host), but this will be UDP, and on restrictive environments, even if 443 and 80 are allowed (TCP), Wireguard would still be blocked (UDP != TCP). Perhaps the best way you could go around this would be to use UDP 53 (DNS), but again, a restrictive network will probably block all requests to UDP 53 for exact IP addresses (like 1.1.1.1).

hi @mgarces how do I configure my client ot use port 443 udp?