incompatible peers not detected/disconnected #6293

My node has connected to an incompatible node, which it has remained connected to even though it is providing no value:-

2015-06-16 19:27:48 Added connection to 85.187.169.169:8333 peer=177 2015-06-16 19:27:49 send version message: blocks=322214, them=85.187.169.169:8333, peer=177 2015-06-16 19:27:58 receive version message: /UnattainiumV2:0.9.4.2/: version 70002, blocks=705812, us=80.235.35.22:11094, peer=177, peeraddr=85.187.169.169:8333 2015-06-16 19:27:58 initial getheaders (361216) to peer=177 (startheight:705812) 2015-06-16 19:28:05 ERROR: AcceptBlockHeader: prev block not found 2015-06-16 19:28:05 Misbehaving: peer=177 (0 -> 10) 2015-06-16 19:28:05 ERROR: invalid header received 2015-06-16 19:28:05 ProcessMessages(headers, 162003 bytes) FAILED peer=177 2015-06-16 19:29:00 inv (new) block 00000000008721d7925eb5ba827dd7e1a44bddfa5a98f2f72062bd6c89512ea6 from peer=177 <-----cut------> 2015-06-16 19:35:04 inv (new) block 7242e6aa391648d84f22e9d7a7ebb99365030cf98dd26c24b0ed84a2b6fe6286 from peer=177

Clearly, this node is running an incompatible blockchain, and the headers received were invalid. Is there any reason to keep a node such as this connected for long?

Fix is to set misbehave to 100 for headers with prev block not found?

Not an invalid block chain. Just sending headers for which you don't have the parent.

@sipa Look at it's start height - it has a height far larger than the current bitcoin blockchain has reached. Also, why is it sending headers for which I don't have the parent? This should never happen, should it?

Oh, interesting. I missed that.

Yeah, it should not send unrequested headers.

This still an open issue @rebroad?