Misbehaving peer v0.15.99 #12343

issue Willtech opened this issue on February 3, 2018
  1. Willtech commented at 12:52 PM on February 3, 2018: contributor

    Just a note for @petertodd in case there is any issue, I safely exited bitcoin-qt v0.15.1 and picked up this in the log file on restart (I have my ban threshold set low):

    2018-02-03 12:41:57 receive version message: /Satoshi:0.15.99/: version 70015, blocks=526679, us=62.212.73.141:38050, peer=5
    2018-02-03 12:42:03 Misbehaving: seed.btc.petertodd.org peer=5 (0 -> 20) BAN THRESHOLD EXCEEDED
    2018-02-03 12:42:03 ERROR: non-continuous headers sequence
    2018-02-03 12:42:03 ProcessMessages(headers, 162003 bytes) FAILED peer=5

    The blocks= value is significantly higher than the preceding peers.

    I presume the DNS name and IP of a seed node are not private.

    side note: the only new entry in the ban list is ::/128

  2. gmaxwell commented at 8:50 AM on February 4, 2018: contributor

    You are connecting out over tor. The dnsseed mechanism in that case works by connecting to the named dnsseeds directly. One of the dnsseeds returned to you a host that is some altcoin. Your node noticed it was an altcoin and banned it. I don't think there is anything to report here other than perhaps petertodd might want to put better filtering on his dnsseed.

  3. fanquake added the label P2P on Feb 4, 2018
  4. MarcoFalke closed this on Feb 4, 2018

  5. MarcoFalke locked this on Sep 8, 2021
Contributors
Labels

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-29 03:15 UTC

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