Banning incoming connection from a node connected via Tor does not work as expected #9689

issue madmarks opened this issue on February 4, 2017
  1. madmarks commented at 3:13 PM on February 4, 2017: none

    Blocking via GUI one connected incoming Tor node with 127.0.0.1:port blocks any other incoming 127.0.0.1 nodes.

    banincommingtornode

    I want to ban incoming connections just from specific Tor node but now it is not possible.

    • Version: Bitcoin Core v0.13.2 64-bit
    • OS: Windows 7 x64
  2. sipa commented at 6:43 PM on February 4, 2017: member

    That's not possible as Tor connections' source node is not visible. To your node, they all look like they're coming from 127.0.0.1.

  3. madmarks commented at 1:02 AM on February 5, 2017: none

    Thanks @sipa. Is there some workaround to ban incoming connections just from Tor nodes running specific version as I see version is reported by GUI?

  4. fanquake added the label Questions and Help on Feb 5, 2017
  5. gj12 commented at 3:56 PM on February 19, 2017: none

    Why would you want to block tor nodes? You can block them via IP tables, but you can't get every bridge of the tor network. It's basically useless.

  6. madmarks commented at 8:27 PM on February 20, 2017: none

    Why would you want to block tor nodes? @gj12, I want to ban nodes running old version. It is easy with regular nodes but not possible for tor nodes.

  7. MarcoFalke commented at 12:40 AM on April 26, 2020: member

    Closing, because it is not possible

  8. MarcoFalke closed this on Apr 26, 2020

  9. DrahtBot locked this on Feb 15, 2022

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-17 03:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me