Bridge meek 0.0.2.0:1 url=https://meek-reflect.appspot.com/ front=www.google.com
DataDirectory C:\Users\...\Desktop\Tor Browser\Browser\TorBrowser\Data\Tor
DirReqStatistics 0
GeoIPFile C:\Users\...\Desktop\Tor Browser\Browser\TorBrowser\Data\Tor\geoip
GeoIPv6File C:\Users\...\Desktop\Tor Browser\Browser\TorBrowser\Data\Tor\geoip6
UseBridges 1
I used: https://bridges.torproject.org/bridges?transport=obfs3
And set config on Whonix-Gateway:
DisableNetwork 0
UseBridges 1
Bridge obfs3 54.80.31.102:40872 FDC7A....(it's too long to retype)
and receive an error:
[INFO] [whonixcheck] Tor Bootstrap Result: Bootstraping for x seconds. 5 % done. Tor Circuit: not established. Tor reports: WARN BOOTSTRAP PROGRESS=5 TAG=conn_dir SUMMARY="Connection to directory server" WARNING="Can't connect to bridge" REASON=PT_MISSING COUNT=3 RECOMMENDATION=warn
meek (from your config above) is a transport. A Tor pluggable transport (How can we help? | Tor Project | Support). Stuff that works on the host using TBB, doesn’t necessarily work with Whonix (using “system Tor”) out of the box. The only transports bridges that are documented and simple to use with Whonix for now are ordinary bridges and obfs3 bridges.
How to use most of these fancy new great transports in Whonix [or Debian, system Tor] is still undocumented. I am not saying it’s impossible, but figuring out needs a developers mindset.
