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

Why was UDP closed in the latest update? #609

Closed
Phoenix1969 opened this issue Jan 26, 2024 · 9 comments · Fixed by #611
Closed

Why was UDP closed in the latest update? #609

Phoenix1969 opened this issue Jan 26, 2024 · 9 comments · Fixed by #611

Comments

@Phoenix1969
Copy link

Peers connecting has become horrible since the last update and i noticed the closed connection. it is effecting the entire network.
Why and what are we supposed to do about it?

@meowsbits
Copy link
Contributor

meowsbits commented Jan 29, 2024

Can you say more about your finding the UDP closed in the latest update? Which update? Where was it closed? I don't believe we ever intended to do that, so we'll need to investigate on your context. We also run several always-on boot nodes and several ephemeral test nodes, and haven't been able to reproduce the issue.

We have indeed received multiple reports of problematic peering (eg. #610), but haven't been able to solidify a rationale for it with 100% certainty.

What we do know is that per our network explorer on https://etcnodes.org/, the ETC network is dominated by CoreGeth/ETCMCgethNodes, which we know to be configured to be undiscoverable, which certainly doesn't help the network any. Likewise, if your node is undiscoverable (eg firewalled), poor peering can be expected since the protocol becomes unilateral and synchronous rather than bilateral and asynchronous.

@ziogaschr
Copy link
Member

@Phoenix1969 can we also please know your location (if allowed to be shared), in order we check on a node in the same locations as you. It might need more time to find good nodes close to you, and we might be able to find the cause and resolve it easier.

@LordExodus
Copy link

Upnp doesn't seem to work with the latest version compared to version 1.12.10. When starting, the port is opened on the router but closed again after a short time, maybe with lease time or something

@ziogaschr
Copy link
Member

@LordExodus this is a great finding to start with. I will test both versions to verify it. Thanks

@ziogaschr
Copy link
Member

You did a great find @LordExodus.
Do you know how to build #611 and try this release to let us know if this works for you?
If you can't build it yourself and you are willing to test, please let me know your operating system and I can send you a custom build to test with.

@LordExodus
Copy link

LordExodus commented Feb 1, 2024

Please build it for me. I am on win64... Thank you! @ziogaschr

@meowsbits
Copy link
Contributor

@LordExodus
Copy link

Thank you for that! @meowsbits @ziogaschr Its working flawless now. This will also fix a lot of undiscoverable ETCMC nodes. Hope the next stable release comes soon, good work

@ziogaschr
Copy link
Member

Thanks for testing @LordExodus. Indeed we were trying to find out about the peer issues the last months without luck. Your mention to UPnP helped us to focus here. I looked at this before, but haven't waited for 2 minutes for checking back my router.

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 a pull request may close this issue.

4 participants