The ISP has contracted a service that captures bridges@ and BridgeDB. Meek works but the connection is very slow (60~100 kbps). How do I get obfs4 bridges that they cannot capture?

  • 1
    Hi, do you have proof of this contract? – cacahuatl Mar 4 '17 at 18:38
  • Or any reason at all to believe that's the case? – cacahuatl Mar 4 '17 at 18:47
  • I know they were looking for bridges to block. I do not know how they managed to stop everything I can get in BridgeDB and bridge@. – Liber Mar 4 '17 at 19:06
  • Probably by blocking traffic that cannot be categorised. – cacahuatl Mar 4 '17 at 19:07

Bridges that are not listed in BridgeDB are distributed manually.

As such you'd need to know someone or some organisation running such a bridge and contact them to request usage of it and obviously they'd have to actually trust you (i.e. that you weren't trying to find out the bridge address to censor it).

I find it unlikely your ISP has such a contract (there are easier paths to take and I doubt you've tested every bridge in bridgedb), but I'd love to know more if you have more information on that.

  • It's hard to find a bridge that works. When encounter is an obfs4 that only works for a few hours. The ISP team grew. They may be paying new people to block the bridges. – Liber Mar 4 '17 at 19:23
  • Then an unlisted bridge would also be discovered and blocked by the same process? – cacahuatl Mar 4 '17 at 23:30
  • Old bridges obfs4 worked months. New obfs4 bridges work 3 to 4 days. – Liber Mar 5 '17 at 3:02
  • It is increasingly difficult to find a bridge that works. I believe they are sweeping BridgeDB and blocking bridges. – Liber Mar 5 '17 at 3:04
  • Not listed obfs4 bridge may be the solution. – Liber Mar 5 '17 at 3:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.