>> Please let me know, if you are able to get the OBFS4
>> bridge working without exposing the ORPort. Respectfully,
> Yes, that's working
Great News!
> == Announcements ==
> rdsys is ignoring the running flag now :)
> * To hide your bridge's ORPort:
> ORPort 127.0.0.1:auto
>
> AssumeReachable 1
Per Roger's comment in the Issue, it sounds like I can simply firewall incoming connections to the ORPort and add the AssumeReachable 1 directive to the torrc? Is that correct?
> The previously mentioned logs and the Tor metrics showing the bridge as offline can be ignored.
The failure logs and metrics are going to be confusing to new obfsbridge operators. I suppose documenting this on the obfsbridge setup page will have to be sufficient in the interim; along, with pointing them to the bridgedb metrics page.