Elena Frank

@geotro yes it is supported. You can combine them in the same manner as it is done here with tcp and quic: https://github.com/libp2p/rust-libp2p/blob/a7148648858fe10e9ba4c2793c7e12392b49c0ab/transports/quic/tests/smoke.rs#L118-L136 and either replace the `tcp_transport` with your...

**Changelog** - Add link to libp2p/rust-libp2p#3133

> Why are you referring to TCP in the context of QUIC? I was referring to TCP to point out how you could support both TCP and QUIC together with...

Good point @Ralith, thanks for raising it! I was thinking about the case of e.g. a simple request-response-protocol, where after writing the response the remote doesn't know if the response...

> I'm getting rust client crashes with the following: > > ``` > [2022-12-04T19:48:10Z INFO rust_client] dial to QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb failed: Transport([("/ip6/2604:1380:4602:5c00::3/tcp/4001/p2p/QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb", Other(Custom { kind: Other, error: Transport(B(A(A(B(Os { code: 110,...

> My rust-client, running on a Raspberry Pi B+, stalls after >10h. > > The last log lines: > > ``` > Dec 01 10:18:46 raspberrypi rust-client[21355]: [2022-12-01T09:18:46Z INFO rust_client]...

I assume you mean "remote" DCUtR peers? Just to help my understanding, could you briefly explain why this is needed?