bitnodes sending sendaddrv2 after verack

[Gregory Sanders]

which violates the spec, resulting in a disconnection from Bitcoin Core: https://github.com/bitcoin/bips/blob/master/bip-0155.mediawiki#signaling-support-and-compatibility

the code in repo seems to be doing the right thing, so just reporting this

2024-03-06T16:22:13.902517Z [net] Added connection peer=83
2024-03-06T16:22:13.902576Z [net] connection from 18.222.202.184:41035 accepted
2024-03-06T16:22:13.903730Z [net] received: version (103 bytes) peer=83
2024-03-06T16:22:13.903794Z [net] sending version (103 bytes) peer=83
2024-03-06T16:22:13.903909Z [net] send version message: version 70016, blocks=833423, txrelay=1, peer=83
2024-03-06T16:22:13.903943Z [net] sending wtxidrelay (0 bytes) peer=83
2024-03-06T16:22:13.904007Z [net] sending sendaddrv2 (0 bytes) peer=83
2024-03-06T16:22:13.904185Z [net] sending verack (0 bytes) peer=83
2024-03-06T16:22:13.904258Z [net] receive version message: /bitnodes.io:1.0/: version 70016, blocks=833422, us=100.15.116.202:8333, txrelay=1, peer=83
...
2024-03-06T16:22:14.902409Z [net] received: verack (0 bytes) peer=83
2024-03-06T16:22:14.902536Z New inbound v1 peer connected: version: 70016, blocks=833422, peer=83
2024-03-06T16:22:14.902588Z [net] sending sendcmpct (9 bytes) peer=83
2024-03-06T16:22:14.902762Z [net] sending ping (8 bytes) peer=83
2024-03-06T16:22:14.902838Z [net] sending feefilter (8 bytes) peer=83
2024-03-06T16:22:14.902990Z [net] received: sendaddrv2 (0 bytes) peer=83
2024-03-06T16:22:14.903021Z [net] sendaddrv2 received after verack from peer=83; disconnecting
2024-03-06T16:22:14.916477Z [net] disconnecting peer=83
2024-03-06T16:22:14.916698Z [net] Cleared nodestate for peer=83

[ayeowch]

Thanks for the report. This looks like someone is using a modified copy of this repo.
The crawler from bitnodes.io is currently using /bitnodes.io:0.3/ subver. The log above shows /bitnodes.io:1.0/ and the IP differs from the one mentioned at the footer of https://bitnodes.io