No response to version packet on testnet

[brian_armstrong]

Hi,

I've run into a strange problem when I try to connect to the official client on testnet (I'm doing some testing locally).

My code sends the version packet, the client updates to show one connection has been made, but it doesn't seem to send any version packet (or anything else) in response.  So the handshake just ends there.

This was all working normally yesterday and I can't think of anything I've changed since then.

Has anyone ever encountered this?  I don't have any port conflicts I can see.  I thought maybe the connection was banned (for misbehaving peer) so I set bantime=0 but this didn't change anything.  It hasn't reached the max number of connections.  Under what other conditions would the official client not send a version packet in response on testnet?

Really stuck here, thanks!!

[1715178473]

1715178473

[1715178473]

1715178473

[genjix]

Hah! I just woke up confused as hell why my code isn't working. Thanks for letting me know why.

bitcoin.org/feb20

Guess I shouldn't have ignored all those bazillions of alerts yesterday.

tl;dr version packets now have a checksum.

[Luke-Jr]

The funny thing is, since this was announced 2 years ago, I happily woke up to my node implementation working for the first time ever (I didn't bother wasting time on hacks that were going away in less than 20 days)

[brian_armstrong]

Yep this was it!!!  bitcoin.org/feb20

Adding the checksum fixed it.  Thank you so much!