Invalid message start in communication with Node

[martin-key]

2018-01-12 05:55:09 PROCESSMESSAGE: INVALID MESSAGESTART version peer=442992
2018-01-12 05:55:09 PROCESSMESSAGE: INVALID MESSAGESTART version peer=442993
2018-01-12 05:55:09 PROCESSMESSAGE: INVALID MESSAGESTART version peer=442994
2018-01-12 05:55:09 PROCESSMESSAGE: INVALID MESSAGESTART version peer=442995

This is what I've got from the logs. Also in BTG -
2018-01-12 05:55:08 ERROR: ProcessNewBlock: AcceptBlock FAILED currently looking for more info.

[martin-key]

This happens on BTG core, version 0.15.0.2. It causes a lot of ping.

[martin-key]

After investigation I found out that the traffic was caused by 2 IPs that were trying to reach the nodes. Is there a possibility that the pool somehow exposes information about the IPs of the coin daemons ? After blocking the IPs the traffic dropped 6 times .... I have no such problems on my other nodes and the 2 for the pool were made specially for the pool. Moreover upon changing the nodes I have seen on the graphs that the traffic rises where the pool is pointed.

[martin-key]

The drop is when I have banned the IPs

[rterbush]

These messages are caused by some "feature" of the BTG node software. Not clear if this change has yet to be implemented.

BTCGPU/BTCGPU#160

We should probably not be banning based on this warning.

[martin-key]

I have removed the IPs causing this and had no such problem. Could be an attack. However this is not the explanation for this:

[oliverw]

@StarbuckBG Nope. The pool does not expose the daemons anywhere.

[martin-key]

Ok! I will setup a testnet for BTG tomorrow so we can test the pool as the current testnet is still not restart to low diff.

…

On 12 Jan 2018, at 19:35, Oliver Weichhold ***@***.***> wrote: @StarbuckBG <https://github.com/starbuckbg> Nope. The pool does not expose the daemons anywhere. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#169 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADrjrVpiHOdOw5kjuyPWI2zDJcatkKOKks5tJ5VHgaJpZM4RcDHv>.

[martin-key]

The problem with the rejected blocks is fixed by this - f5bd439

Tested in private BTG regtest network and working. Seems that the BTC segwit block is ok, but please double check.

Fix is included my PR #157

[martin-key]

Closing for now.