#21272: Onionperf deployment -------------------------+------------------------------ Reporter: hiro | Owner: metrics-team Type: enhancement | Status: needs_review Priority: Medium | Milestone: Component: Metrics | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -------------------------+------------------------------
Comment (by robgjansen): Replying to [comment:58 karsten]: > Ah, that directory contains .tpf files from Torperf instances (`torperf-*` and `siv*`) as well as OnionPerf instances (`op-*`). The latter should contain all keys that OnionPerf produces. Mind checking again? Ahh, ok. I'm now looking at `op-us-5242880-2017-03-21.tpf`. The data element I think you are looking for is: {{{ ENDPOINTREMOTE=199-119-112-144.i95.net:199.119.112.144:8080 }}} I think that 8080 is the port that the tgen client requests Tor to connect to. I see the problem now. From the code, it appears that this port (8080 in this case) is the `--tgen-connect-port`, i.e., the port that the tgen client asks Tor to connect to. This not necessarily be the same as the `--tgen-listen-port`, since the remote server machine could have firewall rules set up to forward requests on various ports to the actual listening port. So, I wonder which of the following is correct: - hiro is using `--tgen-connect-port=8080` and `--tgen-listen-port=8080` - hiro is using `--tgen-connect-port=8080` and `--tgen-listen-port=80` and forwarding requests on 8080 over to the server running on 80 - my conclusion after reading the code is incorrect. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21272#comment:59> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs