4 ms·
I'm a consultant across a bunch of orgs, and some of the fun stuff I've seen recently: Client A requires VPN Client "X" that is exactly version 1.2.3.4. Clien
by jiggawatts 6y ago
I'm a consultant across a bunch of orgs, and some of the fun stuff I've seen recently:
Client A requires VPN Client "X" that is exactly version 1.2.3.4.
Client B requires the same VPN Client "X", but force-upgrades it to "1.2.3.5" or whatever.
I now cannot connect to Client A without uninstalling the VPN client installed by Client B and reinstalling from scratch.
A gentle suggestion to the VPN vendors that write not-backwards-and-forward compatible clients like this: Go die in a fire. Or quit IT and go lay bricks or something. Actually don't do that, I wouldn't want to live in a building you build. It'll probably collapse if the wind isn't blowing at the exact right speed.
Similarly, Client C has a VPN client that is also the kitchen sink, and has a "profile" that overwrites half my system with its junk. It refuses to connect if I edit the profile. I have several coworkers who VPN in via Virtual Machines to work around this.
Many VPN vendors believe that VPN client downloads should require a support login. My feedback: Stop that. Just stop. Publish a straight up download link to every version. Please. Just do it. I promise you won't lose any sales because of this. Really. I promise.
More fun: A large gov org client of ours had spent nearly a decade hard-coding their "LAN subnet range" in a bazillion firewall and IP whitelisting rules in dozens of products. The VPN is in the Cloud and uses a different range (10.x.x.x/8), so now every firewall rule is broken for users connecting from home. 9 months into the pandemic, they're still working on it.
I have Gigabit fibre and a high performance computer. Downloads really do go at 800+ Mbps. I'm yet to see a VPN product that can crack 200 Mbps even during periods of low load and with a matching gigabit link at the other end. Most do 3-20 Mbps, and I've seen as low as 1 Mbps. This is entirely a software problem!
Microsoft deserves the IT equivalent of the Razzie awards for their implementation of IP-HTTPS in DirectAccess which is a) Slow as molasses, b) Limited to 8 cores on the server for no reason, c) Not fixed in 12 years, d) Still theoretically supported, e) Will never be fixed.
Vendors: Benchmark your products please. Once a decade maybe. Or two. No rush. It's not like there's a pandemic on or anything. Take your time.
I have to stop ranting now, I think my blood pressure is rising to dangerous levels...
- magicalhippo 6y agoTo support our customers we usually have VPN access to the servers where our software runs. So invariably our support team needs a ton of different VPN solutions. Like you say some just refuse to co-exist (even between vendors), require 32bit Windows (still!) or other silly things. So support folks have like 5-6 different VMs, each with several different VPN clients in them.
- jeroenhd 6y agoSituations like these are why I like the networking system of Qubes OS. With it you can plug any network VM in front of your applications, usually TOR but there's no reason why it can't be a corporate VPN, and let the rest of your software use that as their uplink. Vendor VPN software will probably never be fixed; there is no financial incentive for playing nice with other vendors and incompatibilities in upgrades means their locked-in customers who need to work with other companies are only incentivized to also upgrade. Sadly a system like Qubes' or using VMs will probably be the only way to combine VPNs from different companies and/or vendors for while...
- Fnoord 6y ago> Sadly a system like Qubes' or using VMs [...] You can do the same with Docker, too. Or an external machine plus some routing voodoo.
- jeroenhd 6y agoThat's true, although routing a browser or generic application through Docker can be difficult sometimes. There's also not that many of these shitty VPN clients with Linux support, which is a major pain.
- Fnoord 6y agoNo idea which shitty VPN clients these are. Am aware of frontends only (also I currently mostly use macOS as client), as well as Sshuttle (provides VPN over SSH via CLI). You can run a container running a browser such as Firefox or Browsh linked to a WireGuard or OpenVPN container. But you can do it without that, too. Have a different user use a different (virtual) interface, for example. Layer 7 packet filter could achieve it as well.
- jeroenhd 6y agoAh, my problems with these systems is that they usually rely on some proprietary Cisco protocol or OpenVPN with an extra authentication daemon. I agree that open source VPNs are thankfully to run, thankfully.
- Fnoord 6y ago> I'm yet to see a VPN product that can crack 200 Mbps even during periods of low load and with a matching gigabit link at the other end. WireGuard and IPsec (the latter being a nightmare to set up) [1]. [1] https://camo.githubusercontent.com/907b408d818e9522afe5168c3f6014eb82773cb2/68747470733a2f2f7777772e636b6e2e696f2f696d616765732f7769726567756172645f636f6d7061726973696f6e732e706e67 https://camo.githubusercontent.com/907b408d818e9522afe5168c3...
- throwaway3neu94 6y agoThe protocol is not the problem here. Most commercial VPN products are IPsec internally, plus some proprietary authentication stuff. (So much that for several, there are open source reimplementations of just those parts, and the actual IPsec is done by the normal Linux kernel IPsec code. See OpenConnect's PulseSecure support for an example.) Also, having both run a VPN for a large network, and worked on VPN software for large networks, once you get to high user counts it's not as trivial as you think. VPNs introduce extra latency, probably the corporate VPN hub is not at all on the shortest path to your actual destination. And corporate VPNs tend to go through (multiple) layers of other filtering. The bottleneck can be Pkts/s, Byte/s or Connections/s and it is not at all obvious which it is. And so on. Besides, there are reasons corporations pay for expensive VPN solutions - certifications and compliance driven requirements such as integration of endpoint management. Not saying it can't be done, but "use IPsec or Wireguard" misses the point entirely. (Of course, if those products were using Wireguard instead of IPsec, it would probably help a bit.)