-
Notifications
You must be signed in to change notification settings - Fork 37.7k
Avoid "Unknown command" messages when receiving getaddr on outbound c… #7642
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
Conversation
18d8158
to
d84ea1a
Compare
utACK Tiny nit: can you use a less wide commit title? See http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html for example. |
utACK rebroad@d84ea1a |
utACK d84ea1a |
utACK. e.g. else if (strCommand == NetMsgType::HEADERS && !fImporting && !fReindex) // Ignore headers received while importing |
d84ea1a
to
9988554
Compare
@sipa commit reworded |
…on outbound c… 9988554 No "Unknown command" for getaddr command. (R E Broadley)
Could be tagged with "Needs backport" |
…onnections. Github-Pull: bitcoin#7642 Rebased-From: d84ea1a
Backported as part of #7938. Removing label 'Needs backport'. |
…onnections. Github-Pull: bitcoin#7642 Rebased-From: d84ea1a
…onnections.
Replaces #6344 and addresses concerns raised (i.e. now logs this exceptional event).