Conversation
Notices
-
Embed this notice
Anyone got any experience running wireguard over non permissive networks? The ole running it over UDP53/UDP123 isn't cutting the mustard. I've got a wifi network with a captive portal (Cisco) that I often have to use when the LTE in this place is screwed. Other VPN's work fine, but I prefer to run my shit over wireguard when I can.
-
Embed this notice
@reldred back in the day I put an ssh tunnel over port 80/443 to get around the corporate firewall, but wireguard, no
-
Embed this notice
@reldred at least openvpn on tcp 80 or 443 is the first thing I'd try.
-
Embed this notice
@bajax @reldred > tcp over tcp
Good luck
-
Embed this notice
@reldred most of these I've dealt with blocked all UDP traffic by default. if you really need to do that often, you might need something like openVPN as a fallback.
I know it's a pita
-
Embed this notice
@pwm@darkdork.dev yeah that was the go back in the day, was great on campus networks half the time you could just do it over the normal SSH port because the netadmins were lazy and didn't like their own stuff getting blocked. I found it even worked on some campuses that forced everyone through an authed socks proxy, could still ssh outbound with no restrictions.
-
Embed this notice
@pwm@darkdork.dev i dont wanna setup ovpn though i hate it so much 😭
-
Embed this notice
@pwm @reldred rofl it was awful but when you're stuck in class you can tolerate a lot
-
Embed this notice
@reldred I despise ovpn
Once wg hit the kernel I was done forever
-
Embed this notice
@pwm@darkdork.dev Yeah I've been using WG a bit on mikrotik hardware which Showed Me The Light. The fact that it also worked well over CGNAT'd connections was super handy. At my last work I started pivoting everyone who was able to away from l2tp/ipsec to wireguard tunnels. Tunnels established instantly, were more robust, could handle ad-hoc multi-site setups for events over starlink and LTE connections easily, was great.