4 ms·
The only place where it falls shorts is that it doesn't go through as easily as SSL/IPSec on restrictive networks like corporate firewalls, but maybe that will
by m-p-3 7y ago
The only place where it falls shorts is that it doesn't go through as easily as SSL/IPSec on restrictive networks like corporate firewalls, but maybe that will go away when it becomes more common (and hopefully adopted in enterprises).
- RL_Quine 7y agoI've honestly not had a lot of issues with that up until now. Real world it doesn't seem to be blocked by a whole lot of things, except where you only have port 80 and 443 anyway. I've actually seen it work in a lot of places I wouldn't have expected it to, like hotel wifi.
- big_chungus 7y agoI've seen the same, likely because the DPI boxes haven't yet caught up.
- deleted 7y ago[deleted]
- therealmarv 7y agoActually there are workarounds to get Wireguard running over TCP and port 80/443 described here (like udp tunnel). I also wanted to check them out for very restrictive networks in the near future: https://github.com/StreisandEffect/streisand/issues/1633 https://github.com/StreisandEffect/streisand/issues/1633