Creating circuit error: how to understand it?

zrok
29

It seems that we have the same problem with socks shares.

I Configuration: socks

Host1 (500Mbps)

zrok share private -b socks --headless --open
[   1.043]    INFO sdk-golang/ziti.(*listenerManager).createSessionWithBackoff: {session token=[d56f711f-7077-4a60-872f-e4cd2be27bf8]} new service session
[   1.182]    INFO main.(*sharePrivateCommand).shareLocal: allow other to access your share with the following command:
zrok access private q2y67021wywn

Host2 (100Mbps)

zrok access private q2y67021wywn -b 127.0.0.1:9999 --headless

Host3 (20Mbps)

zrok access private q2y67021wywn -b 127.0.0.1:9999 --headless

II We validate the configuration.

Host2 (100Mbps)

curl --proxy socks5://127.0.0.1:9999 -s -w '%{time_total}s' -o /dev/null https://www.google.com
0.322686s

Host3 (20Mbps)

curl --proxy socks5://127.0.0.1:9999 -s -w '%{time_total}s' -o /dev/null https://www.google.com
0.303178s

III We run the test.

Host3 (20Mbps): downloading at 2512kB/s

curl --proxy socks5://127.0.0.1:9999 -o /dev/null https://mirror.in2p3.fr/pub/fedora/linux/releases/42/Workstation/x86_64/iso/Fedora-Workstation-Live-42-1.1.x86_64.iso
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  2 2287M    2 61.0M    0     0  2488k      0  0:15:41  0:00:25  0:15:16 2512k

Host2 (100Mbps): http request

curl --proxy socks5://127.0.0.1:9999 -s -w '%{time_total}s' -o /dev/null https://www.google.com
17.690794s

curl --proxy socks5://127.0.0.1:9999 -s -w '%{time_total}s' -o /dev/null https://www.google.com
19.403398s


curl --proxy socks5://127.0.0.1:9999 -s -w '%{time_total}s' -o /dev/null https://www.google.com
21.163678s

IV Conclusion

While downloading from Host3 at a very low speed 2MB/s we obtain on Host2 having 100Mbps network connection the execution time about 20 seconds.