Ability to disconnect/ban peers from the GUI #5866

issue PRabahy openend this issue on March 7, 2015
  1. PRabahy commented at 6:03 pm on March 7, 2015: contributor

    This is a feature requests, not a bug.

    Now that I have been using the new Peers screen in bitcoin-qt, I have noticed that there are several peers that are doing something that I don’t like (using too much bandwidth, multiple connections from the same ip, etc.) I would like an option to right click on a peer and be able to disconnect or ban them. Also, it would be nice if the same right click menu had an option to reserve an inbound slot for a specific peer, but that would likely be a bit more tricky.

  2. laanwj commented at 10:02 am on March 9, 2015: member
    There aren’t even RPC commands to do this. Those should come first. I think it’d be nice to have, although having to babysit your peer list shouldn’t be necessary.
  3. laanwj added the label GUI on Mar 9, 2015
  4. jonasschnelli commented at 3:34 pm on March 11, 2015: contributor
    I also like the idea of having a RPC command disconnectpeer and banpeer (over a peer id or peer ip arg). A context menu in the GUI-Console with those function could make sense.
  5. MrKrzYch00 commented at 3:56 pm on March 11, 2015: none

    I can say that implementing banpeer is not that hard actually. I did it myself in cloned sourcecode as a part of addnode rpc command (addnode IP:port ban) and it seems to work, the ban code also performs disconnect. However just disconnecting can be less of use since that peer can reconnect right away (unless we are blocking incoming connections).

    Another thing to note is some peers disconnecting/banning other peers that are syncing with network, for example people with low upload limit that are lagged (I myself have max ~80KiB/s upload). I doubt that it will be abused to that extent, but it can always hurt the network, though.

  6. aussiehash commented at 10:47 am on May 17, 2015: none
    +1
  7. LeMiner commented at 3:48 pm on May 18, 2015: none
    As a full node owner, I’m going to +1 this as well. It’ll be a great addition to QT and will be much faster/easier than adding ip’s to a firewall(s).
  8. MrKrzYch00 commented at 4:30 am on May 19, 2015: none
    For ban code I use this modification: https://github.com/MrKrzYch00/bitcoin/commit/0672b0feafecab98409790eabd52b56939b954e4 so far I have no problems with it running.
  9. jonasschnelli commented at 10:34 am on November 27, 2015: contributor
    This is possible now. See #6315. Closing.
  10. jonasschnelli closed this on Nov 27, 2015

  11. MarcoFalke locked this on Sep 8, 2021

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: 2024-11-17 00:12 UTC

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