-
Notifications
You must be signed in to change notification settings - Fork 846
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix geth rlpx ping command #5917
Conversation
Signed-off-by: Stefan <[email protected]>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. The only thing that need to be reverted is the update of the reference tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems the reference tests have been updated by accident.
Signed-off-by: Stefan <[email protected]>
reference tests submodule version fixed
* fix geth rlpx ping command Signed-off-by: Stefan <[email protected]> --------- Signed-off-by: Stefan <[email protected]> Signed-off-by: Justin Florentine <[email protected]>
* fix geth rlpx ping command Signed-off-by: Stefan <[email protected]> --------- Signed-off-by: Stefan <[email protected]>
PR description
The geth cmd
./build/bin/devp2p rlpx ping enodeAddress
expects the client with address enodeAddress to respond with a HelloMessage right after successfully receiving the handshake message from the initiator.
Existing behaviour in Besu is to wait for the HelloMessage from the initiator before sending the HelloMessage back.