Yamux resets stream when both peers are in Client mode about rust-yamux HOT 3 CLOSED

Yes, please file an issue in rust-libp2p. The connection upgrade there is always using Mode::Server for inbound and Mode::Client for outbound upgrades. libp2p-yamux needs to provide a way to override this. Ideally the transport builder also allows access to the connection info.

from rust-yamux.

Yes, this is expected behaviour. Yamux splits the stream ID space into two non-overlapping sets. The client set consists of odd IDs and the server set of even IDs. See https://github.com/hashicorp/yamux/blob/master/spec.md#streamid-field for details.

A tells B to start connecting to the public address of C. At the same time, A answers to C with the publicly visible IP of B. Both nodes create a socket and then bind it to the same address used to contact node A. It then use this socket to connect. B and C start trying to connect to each other, creating a hole in the NAT.

Even when connections are established by a simultaneous connect, one still needs to make one endpoint the server and the other the client. In general this could be based on the ordering of IP addresses, e.g. the endpoint with the smaller IP address assumes the client role and the other one the server. This is purely needed for the ID space split mentioned above and does not have other implications.

from rust-yamux.

Thanks for your response.

The client set consists of odd IDs and the server set of even IDs

Yes, that's what I understood of the current code.

Even when connections are established by a simultaneous connect, one still needs to make one endpoint the server and the other the client.

I implemented that logic in my PoC and indeed it works fine now. But in a libp2p project, I don't think I can do that. Maybe I should open an issue there with my use case?

from rust-yamux.