[bisq-network/bisq] Unreachable local Bisq onion takes way too long to detect (Issue #6142)

[jmacxx]

@JeremyRand, I have written PR #6147 that does the self connect over Tor to test incoming connectivity.  It succeeds with normal Bisq setups and complains when run on Whonix.  I do not know how to configure Whonix to allow incoming Tor connections, spent quite some time with the documentation and opened up all the firewalls I could find, but without success.

In your particular example since your node is still unreachable, I posit the theory that your Bisq just happened to have an **outgoing** connection to a peer that took your offer.  Bisq randomly connects to 8 or so peers to propagate P2P messaging the same way Bitcoin core does, and these connections change over time.

If you can provide any suggestion on how to configure Whonix, I would be glad to hear it.  It looks like the Whonix Bisq guide may have overlooked this issue.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/6142#issuecomment-1097153101
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/bisq/issues/6142/1097153101 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220412/8dfbbf06/attachment-0001.htm>