-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Autonat + Quic Fails on Localhost #3308
Comments
Is
This is caused by the connection not being able to keep up with the inbound messages, e.g. because its task is not getting polled or the remote send the packets faster than the local peer can handle them. But should not be related to AutoNAT. Nothing comes to my mind right now with just these logs. Could you share your code / steps to reproduce? |
The code is based on n0-computer/iroh#586 You can build the binary using
which will print out a "Ticket" and in another shell run
Autonat is controlled here: https://github.com/n0-computer/iroh/blob/17e037dc0ce55da105aab04542fe09e2c3b924e8/iroh-share/src/p2p_node.rs#L65 and the transport is built here: https://github.com/n0-computer/iroh/blob/17e037dc0ce55da105aab04542fe09e2c3b924e8/iroh-p2p/src/swarm.rs |
Additional note: this does not happen when using the tcp address, same setup |
I haven't had time to look into this yet, but I am currently looking into an issue around closing streams in QUIC, see #3343. This issue might be related. Did you observe any error logs here around closing a stream? |
Summary
I have two nodes (iroh) running on localhost. When A dials B on quic-v1 and the autonat protocol is enabled the connection is established but killed again very shortly after, when autonat is disabled, the connection stays established
In the logs of the dialing node I found
and on the other node it gets into a state of printing these messages over and over again
Version
0.50.0
The text was updated successfully, but these errors were encountered: