U/sh4zbot found out that this docker image can’t work as a SOKS proxy since it has a hardcoded SocksPort 0 in its run file, that can’t be overridden. Or I am simply to stupid to operate it correctly even after trying for several evenings… So, it seems, the official docker image does not work for me. Since then starting fails with an error that SOCKS is already defined. Also, I can’t add the optional environment variable option OBFS4V_SOCKSPort=9050 Neither OR nor PT ports accept SOCKS connections as usual. However, until this day I did not manage to get it to route my own local traffic via SOCKS. At least I see traffic flowing through it well in bridged mode. The official image seemed like a good starting point since it is validated, up to date and has reasonable distribution (or so I assume).Setup was a bit time consuming but the container worked after a bit. It is important for me to have both in the same node.Īt first, I tried the official image: thetorproject/obfs4-bridge I am trying to dockerize (via Ansible) everything important with my homelab rebuild (after catastropy struck, but that is another story).īeforehand I had TOR running smoothly as a bridge and as a local SOCKS proxy for my personal access. Sorry for my second post in a short while, but I am a bit desperate.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |