-
-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
obfs4 bridge support #34
Comments
What exactly should be done here to support it? |
Include obfs4proxy packet. If obfs4 enabled, file
I think list of bridges can be filled from an external file. And we can determine by the fact that the parameter with the path to the file with bridges is filled in, whether the use of the bridge is enabled. |
@b1oki I'm not sure how many of the users here need it so that we should include it by default. Will take a look at the details, especially the effort and impact on image size, and see what can we do for it. |
Looks like obfs4proxy package only exist in the edge branch right now: Can't find it in v3.16 branch: Let's add the package in the image first, as it's more advanced usage, I believe that users who needed will be able to mount self-modified config and the bridge list into the container, at least don't need to install the package again. |
Runs on Raspberry, but cannot connect to Relay. Maybe bridges unavailable. Message: "Delaying directory fetches: No running bridges". Tryied bridges from https://torscan-ru.ntc.party/ and https://bridges.torproject.org/bridges/?transport=obfs4. Might @NickiHell help me |
Add in Dockerfile: Add in torrc:
You can find bridges via https://t.me/GetBridgesBot |
Thank you, but I think the Country's Firewall is too strong.
|
You're doing something wrong. Bridges should work, it says in the logs that there are no bridges. |
With torrc
|
Run container with bridges on x86_64. For now using volumes. Example: cat ./bridges.txt
ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy
Bridge obfs4 x.x.x.x:xxx xxx cert=xxx iat-mode=0
UseBridges 1
docker run -d --restart=always --name tor-socks-proxy -p 0.0.0.0:9100:9150 -v $(pwd)/bridges.txt:/home/bridges.txt ghcr.io/peterdavehello/tor-socks-proxy sh -c "cat /home/bridges.txt >> /etc/tor/torrc; /usr/bin/tor -f /etc/tor/torrc" |
Got error with "obfs4proxy" on Ubuntu 20.04 x64By some reason "obfs4proxy" failed with status code 256
SolvedReplace "obfs4proxy" > "lyrebird".
Maybe help to someone! |
Perhaps there is another way to bypass the blocking of the Tor, but this method seems to me the most obvious.
The text was updated successfully, but these errors were encountered: