[bug] Libp2p relay reconnection issues

[burdiyan]

After removing our fork of libp2p and updating to the newest version, we continue having issues with relay connectivity.

1. Even if relay is configured as static - on failed reconnection the client forgets this relay forever. Submit PR to fix that.
2. When the client loses network, the relay will remove the reservation, so the client should reserve again after reconnecting.

[juligasa]

As for the connection issues it's resolved with 4c88550. I will open an issue in go-libp2p so they can include something similar and we don't need to use our own fork

[burdiyan]

@juligasa Great! Please post here the link to the issue in libp2p when you open it.

[juligasa]

@juligasa Great! Please post here the link to the issue in libp2p when you open it.

libp2p/go-libp2p#1782

[GaboHBeaumont]

so we should close the issue?

[burdiyan]

I think we should close whenever libp2p accepts our PR and we use the upstream version instead of our fork.

[GaboHBeaumont]

Beautiful.

On Tue, 27 Sep 2022 at 11:16, Julio Garcia ***@***.***> wrote: As for the connection issues it's resolved with 4c88550 <4c88550>. I will open an issue in go-libp2p so they can include something similar and we don't need to use our own fork — Reply to this email directly, view it on GitHub <#774 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7TCNHHD6CCFVX5VP35YR3WAK3O7ANCNFSM6AAAAAAQVV2ZPI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- --------------------------------- *Gabriel H Beaumont* mintter.com @GaboHBeaumont <https://twitter.com/GaboHBeaumont> +34655394504 Madrid

[juligasa]

merged here