Skip to content
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

les: allow LES connection to other servers #13889

Merged
merged 1 commit into from Apr 10, 2017

Conversation

zsfelfoldi
Copy link
Contributor

Unfortunately at the moment we have to either run LES protocol with every LES capable peer (even if it is useless) or drop them. So until we have a proper peer connectivity API which allows connecting through ETH but not through LES, allow LES connection to other servers.

This is a fix for #13877

@mention-bot
Copy link

@zsfelfoldi, thanks for your PR! By analyzing the history of the files in this pull request, we identified @karalabe and @fjl to be potential reviewers.

@karalabe
Copy link
Member

Do servers ever push data to clients without them requesting? E.g. new blocks. What happens if servers receive these pushes? Because they will do so after this pr

@zsfelfoldi
Copy link
Contributor Author

They will send new block announcements to each other and ignore incoming ones, nothing else will happen. Since this is only a temporary workaround until we have a proper solution, I did not want to risk breaking things by adding more conditions.

@fjl fjl merged commit 18bbe12 into ethereum:master Apr 10, 2017
@karalabe karalabe added this to the 1.6.0 milestone Apr 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants