Have been running an obfs3 bridge for a while. Since I was building a new Debian server wanted to add obfs4, but when I configure TBB to point to the obfs4 port [Z] I get "general SOCKS failure" in the TBB log. Changing it back to use obfs3 and port [Y] works fine. How can I fix it so obfs4 works too?
Here are the relevant lines from torrc: --- ORPort [X]
BridgeRelay 1 PublishServerDescriptor bridge
ServerTransportPlugin obfs3 exec /usr/bin/obfs4proxy managed ServerTransportListenAddr obfs3 0.0.0.0:[Y] ServerTransportListenAddr obfs4 0.0.0.0:[Z] ExtORPort auto ---
If I do netstat -pan, I see obfs4proxy is listening on both ports on all interfaces. I tried to add "--log-file logfile" after /usr/bin/obfs4proxy in torrc but then it wouldn't start the proxy at all. I'm not finding any other log messages showing a problem. Tor's log is clean, just shows it starting both proxy instances (which netstat confirms.) Obfs4proxy is the packaged version 0.0.6.
Not sure where else to look or change. I'd like to get it working but have commented out the obfs4 line for now.
On 13 Oct 2016, at 10:53, pvr6@sigaint.org wrote:
Have been running an obfs3 bridge for a while. Since I was building a new Debian server wanted to add obfs4, but when I configure TBB to point to the obfs4 port [Z] I get "general SOCKS failure" in the TBB log. Changing it back to use obfs3 and port [Y] works fine. How can I fix it so obfs4 works too?
Here are the relevant lines from torrc:
ORPort [X]
BridgeRelay 1 PublishServerDescriptor bridge
ServerTransportPlugin obfs3 exec /usr/bin/obfs4proxy managed
Here, you ask obfs4proxy yo of obfs3 for you, but not obfs4. Try obfs3,obfs4 instead.
And then give tor browser the full line from the bridge line file in the obfs4proxy directory (the exact file name is in the obfs4proxy readme).
T
ServerTransportListenAddr obfs3 0.0.0.0:[Y] ServerTransportListenAddr obfs4 0.0.0.0:[Z] ExtORPort auto
If I do netstat -pan, I see obfs4proxy is listening on both ports on all interfaces. I tried to add "--log-file logfile" after /usr/bin/obfs4proxy in torrc but then it wouldn't start the proxy at all. I'm not finding any other log messages showing a problem. Tor's log is clean, just shows it starting both proxy instances (which netstat confirms.) Obfs4proxy is the packaged version 0.0.6.
Not sure where else to look or change. I'd like to get it working but have commented out the obfs4 line for now.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------------
On 13 Oct 2016, at 10:53, pvr6@sigaint.org wrote:
...
ServerTransportPlugin obfs3 exec /usr/bin/obfs4proxy managed
"teor" teor2345@gmail.com wrote: Here, you ask obfs4proxy yo of obfs3 for you, but not obfs4. Try obfs3,obfs4 instead.
And then give tor browser the full line from the bridge line file in the obfs4proxy directory (the exact file name is in the obfs4proxy readme).
Thank you! I did have obf3,obfs4 exec in there while testing but I was trying to put the obfs4 bridge into the client the same way I always had for obfs3 and that did not work. Putting in the right info of: obfs4 <IP ADDRESS>:<PORT> <FINGERPRINT> cert=[certstring] iat-mode=0 got it working right away once I saw it wanted the server's ID key fingerprint instead of the bridge's. Left the obfs4 proxy running this time!
tor-relays@lists.torproject.org
-
pvr6＠sigaint.org -
teor