Repository navigation
network throughput significantly reduced #6
Description
I compared the download of a file with AnyConnect, OpenConnect and OpenConnect w/ocproxy.
AnyConnect and OpenConnect were comparable, but ocproxy was taking 10x as long. Is this a known issue with OpenConnect or specific to ocproxy? I've been digging around trying to implement a comparable script to ocproxy to debug this, but haven't had any luck making the initial handshake.
Thanks
Activity
drewwells commentedon Apr 25, 2016
Tunsocks suffers from the same issue.
Jimmy-Z commentedon Sep 21, 2018
I was going to use ocproxy but saw this issue, I resorted to run openconnect on a TUN device and use 3proxy to provide SOCKS proxy, performance is about 80%~90%, I haven't tested extensively though.
cernekee commentedon Sep 21, 2018
Could also use vpnns on Linux (which is part of the ocproxy package) since that is implemented using a tun device + namespaces.
kutukvpavel commentedon Dec 14, 2024
I faced the same problem, with ocproxy video streaming became impossible due to extremely unreliable speed. One minute it's at 10Mbps, next minute it drops to 0.2Mbps (20% of raw OpenConnect to less than 1% of it). Using vpnns didn't help. I suspect it's related to TCP meltdown, since ocproxy does not support UDP #4 .
Had to switch to tunsocks and my speeds are back to 50-60% of raw OpenConnect w/DTLS.