You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've just wired up Autonat in some of my systems and have started seeing this error.
I'm not sure where the Uvi max length is being set in config and as far as I can see, it only affects serialisation.
I have set up a separate libp2p project with an autonat client dialling over either TCP or QUIC to the same server, it seems that first connects if I have just restarted the server but as more and more load reaches the server, we start seeing this issue on the client side.
Summary
I've just wired up Autonat in some of my systems and have started seeing this error.
I'm not sure where the Uvi max length is being set in config and as far as I can see, it only affects serialisation.
I have set up a separate libp2p project with an autonat client dialling over either TCP or QUIC to the same server, it seems that first connects if I have just restarted the server but as more and more load reaches the server, we start seeing this issue on the client side.
Expected behavior
An autonat outbound probe should be sent, resulting in a peer attempting to dial me.
Actual behavior
I get an error, causing NAT discovery to fail
Relevant log output
No response
Possible Solution
No response
Version
No response
Would you like to work on fixing this bug ?
Maybe
The text was updated successfully, but these errors were encountered: