Is the ban scored increased when constantly disconnecting and reconnecting?

[stevenroose]

I have this peer that permanently connects to my node, sends a sendcmpct message and then either disconnects himself or is disconnected by btcd.

A small fragment if the logs:

2017-07-14 09:39:30.217 [INF] BMGR: New valid peer 59.110.63.71:53422 (inbound) (/Satoshi:0.13.0/)
2017-07-14 09:39:30.217 [INF] BMGR: Lost peer 59.110.63.71:53422 (inbound)
2017-07-14 09:39:30.217 [INF] BMGR: New valid peer 59.110.63.71:54402 (inbound) (/Satoshi:0.13.0/)
2017-07-14 09:39:30.217 [INF] BMGR: Lost peer 59.110.63.71:54402 (inbound)
2017-07-14 09:39:42.260 [INF] BMGR: Processed 1 block in the last 12.04s (2217 transactions, height 471155, 2017-06-14 01:03:41 +0200 CEST)
2017-07-14 09:39:48.750 [ERR] PEER: Can't read message from 59.110.63.71:56755 (inbound): ReadMessage: unhandled command [sendcmpct]
2017-07-14 09:39:54.524 [INF] BMGR: Processed 1 block in the last 12.26s (2508 transactions, height 471156, 2017-06-14 01:11:00 +0200 CEST)
2017-07-14 09:39:54.524 [INF] BMGR: New valid peer 59.110.63.71:56755 (inbound) (/Satoshi:0.13.0/)
2017-07-14 09:39:54.524 [INF] BMGR: Lost peer 59.110.63.71:56755 (inbound)
2017-07-14 09:39:58.621 [ERR] PEER: Can't read message from 59.110.63.71:57936 (inbound): ReadMessage: unhandled command [sendcmpct]
2017-07-14 09:40:07.863 [INF] BMGR: Processed 1 block in the last 13.33s (2516 transactions, height 471157, 2017-06-14 01:13:19 +0200 CEST)
2017-07-14 09:40:07.863 [INF] BMGR: New valid peer 59.110.63.71:57936 (inbound) (/Satoshi:0.13.0/)
2017-07-14 09:40:07.863 [INF] BMGR: Lost peer 59.110.63.71:57936 (inbound)
2017-07-14 09:40:14.365 [ERR] PEER: Can't read message from 59.110.63.71:59892 (inbound): ReadMessage: unhandled command [sendcmpct]
2017-07-14 09:40:28.700 [INF] BMGR: Processed 1 block in the last 20.83s (2548 transactions, height 471158, 2017-06-14 01:32:03 +0200 CEST)
2017-07-14 09:40:28.700 [INF] BMGR: New valid peer 59.110.63.71:59892 (inbound) (/Satoshi:0.13.0/)
2017-07-14 09:40:28.700 [INF] BMGR: Lost peer 59.110.63.71:59892 (inbound)
2017-07-14 09:40:28.700 [INF] BMGR: New valid peer 59.110.63.71:33645 (inbound) (/Satoshi:0.13.0/)
2017-07-14 09:40:29.958 [ERR] PEER: Can't read message from 59.110.63.71:33645 (inbound): ReadMessage: unhandled command [sendcmpct]

If I try btcctl node remove 59.110.63.71 perm, it can't find the peer, probably because of the port being missing. But because it's an inbound peer, the port changes every time he connects.

[davecgh]

Regarding the message type, we'll probably need to modify it to not disconnect on that new message, but simply ignore it.

The perm flag only refers to removing peers that were previously added as permanent/persistent peers either via the --addpeer command line flag, btcctl node connect "addr" perm, or btcctl addnode "addr" add.

[MaxSan]

Having same issue. Eventually block height seems to slip behind at undetermined amount of time.

2019-11-02 12:13:18.998 [INF] SYNC: Lost peer 88.99.167.175:13063 (inbound)
2019-11-02 12:13:31.204 [INF] SYNC: New valid peer 112.208.231.249:35582 (inbound) (/bread:2.1/)
2019-11-02 12:13:32.797 [INF] SYNC: Lost peer 112.208.231.249:35582 (inbound)
2019-11-02 12:13:44.301 [INF] SYNC: New valid peer 188.65.213.21:32137 (inbound) (/nodes.bitcoin-russia.ru:0.0.1f/)
etc...