I finally succeeded with the Tor Bridge set-up according to the config and approach detailed in my blog-post but I've also included the updated config in the markdown below:

RunAsDaemon 1
BridgeRelay 1

Log notice file /var/log/tor/notices.log
Log debug file /var/log/tor/debug.log

ORPort 3443

ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4

ExtORPort auto

Nickname SatoshiNakamoto
SatoshiNakamoto <0xc78e9d242552d5da800a87b588dc3d2024a9fa0f@ethmail.cc>

RelayBandwidthBurst 200 KB # But allow bursts up to 200KB/s (1600Kbps)

ExitPolicy reject *:*

Here's my new problem- ever since I started running a Lightning Node (Bitcoin Full Node + Lightning- again, detailed in my other blog-post) on a Raspberry Pi 3 in conjunction with 8 Ethereum mining-rigs operating at full-bore on a small-business grade router connected to a fiber connection, the Tor Bridge I've set-up appears to bottleneck my local network, which then requires a reset. I've troubleshot the aforementioned by testing multiple configurations: I was able to run Bitcoin Core (no Lightning Network, just a regular Bitcoin node on another Raspberry Pi 3) and a Tor Bridge without any issues, however, ever since running the Lightning Node on the other Raspberry Pi 3 with RaspiBlitz (again, that includes the Bitcoin full-node and the Lightning node) while mining Ethereum on 8 separate mining-rigs, I'm unable to run a Tor Bridge- even when if torrc file is throttled for limited bursts i/a/o 200 kb/s. Any help would be appreciated- thanks!

Your Answer

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

Browse other questions tagged or ask your own question.