-
Notifications
You must be signed in to change notification settings - Fork 26
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
is it possible to change the distribution mechanism of the OBSF4 Bridge to Moat? #73
Comments
You can try to add „BridgeDistribution moat“ to /etc/tor/torrc. However, the tor manual states the following: If set along with BridgeRelay, Tor will include a new line in its bridge descriptor which indicates to the BridgeDB service how it would like its bridge address to be given out. Set it to "none" if you want BridgeDB to avoid distributing your bridge address, or "any" to let BridgeDB decide. (Default: any) According to a discussion amongst developers on GitLab, it may be that it is again possible to request (or even to enforce) in which "basket "("https", "email" and "moat") your OBFS4 bridge relay should fall. Nevertheless, I thought that with the default ("any "), an OBFS4 bridge relay has to run stable for quite a time before the bridge distribution mechanism changes to "moat". Unfortunately, I couldn't find anything about this aspect anymore. |
I have already set up several bridges with torbox and then it always took a while until a distribution mechanism was activated. Either HTTPS or MOAT was displayed. I haven't had E-MAIL yet. |
Feel free to contribute. The new option should be integrated / combined with the other, already existing options (menu entry 3 in the sub-menu). |
With commit #7a15a3417458d11a500390f6a798dd17e174e5bc the distribution method can be configured. It will be helpful if @DEC-entralized could test it out. It will be released with the next TorBox release (v.0.4.2). |
Hello, I'm sorry that I didn't manage to take care of it in time. |
According to your first post, your bridge can be reached and should work. This doesn't mean that you will immediately see the use of your bridge. It can take several days or weeks until you see an advertised bandwidth and a consistent set of users (see here). Don't get discouraged if you don't see user connections right away (see also here for more details). However, you should be able to use your bridge for your second TorBox and/or also for the TorBrowser. Did you try to use your bridge for TorBrowser on a computer in another network without TorBox in between? When you download and start the TorBrowser 10.5.x, go to the Tor Network Settings, choose "Provide a Bridge", and enter your Bridge information. |
Hi, I'll try again with a TOR browser to connect to my Bridge PI. to understand. If I don't have a fixed public ip, it doesn't matter or do I have to generate a fixed ip via ddns? And does that also work with a dual stack internet connection? |
You don't need a public IP, as long as your provider supports the port forwarding. However, the IP distributed with the bridge address has to be fixed. In the example below, the path to 187.199.36.90 has to be clear, the OBFS4 bridge relay and the port 6667 has to be accessible on that IP address: obfs4 187.199.36.90:6667 03421E8462B2446FAA5D0F632C9B349C6C58433A cert=nnzsKeikJZ2foFyIzu3TixukCUvoyym2p0M2bxjlCL28C7y1ieb1yO0ohmCGO9i07aDBBA iat-mode=0 I don't think DDNS can help you in any way because it has nothing to do with domain name resolution. Also, if the tor log tells you that your ports are reachable, the TCP reachability test is positive, and Tor Metrics tells you that your relay is online, there is not more to do.
I cannot answer that question because I didn't have the opportunity to test this. |
So I replaced the new files from the 0.4.2 branch with those in my bridge. But there is no menu entry for the distribution mechanism mode. I have now done it via the advanced config. have to wait and see what relaysearch says my new bridge is not there yet. my ports 443 and 4235 are attainable. now also with ipv6. |
So my bridge is now also available for my wifi torbox PI. I'm celebrating right now: P I made the mistake when adding the bridge not to give the certificate .... Grrrr xD |
The selection of the distribution mechanism mode is shown when you use menu entry 3 "Check and/or change the configuration". However, at the moment you have to re-enter all the configuration settings - I guess I can do it better, and will try it tomorrow. |
New on menu-config
|
Implemented with TorBox version 0.4.2! |
is it possible to change the distribution mechanism of the OBSF4 Bridge on Moat? I only ever see HTTPS but then my bridge is only distributed via the website and not automatically when clients request.
The text was updated successfully, but these errors were encountered: