Does quic always build on top of Tcp?

[harsh4786]

A noob question but I’m trying to setup quic, and pass it inside my SwarmBuilder, does quic always have to be built over tcp? I’m asking this after looking at an example in the rust libp2p repo

[mxinden]

I am not sure what you are referring to with "over". Can you rephrase?

As a good example on how to use QUIC, see:

rust-libp2p/examples/chat-example/src/main.rs

Lines 51 to 64 in 608e2db

	// Set up an encrypted DNS-enabled TCP Transport over the yamux protocol.
	let tcp_transport = tcp::async_io::Transport::new(tcp::Config::default().nodelay(true))
	.upgrade(upgrade::Version::V1Lazy)
	.authenticate(noise::Config::new(&id_keys).expect("signing libp2p-noise static keypair"))
	.multiplex(yamux::Config::default())
	.timeout(std::time::Duration::from_secs(20))
	.boxed();
	let quic_transport = quic::async_std::Transport::new(quic::Config::new(&id_keys));
	let transport = OrTransport::new(quic_transport, tcp_transport)
	.map(|either_output, _| match either_output {
	Either::Left((peer_id, muxer)) => (peer_id, StreamMuxerBox::new(muxer)),
	Either::Right((peer_id, muxer)) => (peer_id, StreamMuxerBox::new(muxer)),
	})
	.boxed();

Note that this will become easier with #4120.

[harsh4786]

Getting this error when I try to initialize a QUIC object and pass it inside my SwarmBuilder, I know it's a type issue but how to achieve that type.

[thomaseizinger]

You still need to do the .map and box up the connection object produced by the QUIC transport. See line 61 in the above example.

[harsh4786]

I can't upgrade my quic transport to have tls

[thomaseizinger]

I am not sure what you mean? QUIC implies TLS, you don't need to explicitly configure it. Can you share the code that is not working?

[harsh4786]

Ohh I see, thanks. I thought I had to explicitly add TLS authentication to my quic transport