When will QUIC protocol be supported on all platforms? #79736
Replies: 5 comments 12 replies
-
/fyi @wfurt |
Beta Was this translation helpful? Give feedback.
-
https://devblogs.microsoft.com/dotnet/dotnet-7-networking-improvements/ Perhaps we should document the native dependencies in API docs @ManickaP ? Note that Now , "All" is overloaded question. There is currently no plan for mobile platforms and from .NET prospective the support depends on MsQuic availability. WASM is also problematic AFAIK. Older Windows are problematic. There is #69978 but it will not work out of the box e.g. you would need to work on packaging and dependencies. macOS should work but there are no binary packages, primarily because signing and packaging issues. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the response. I am working to implement DNS-over-QUIC support for my projects so hoping that QUIC support improves in .NET. I did try installing I understand that adding support for all platforms may not be feasible but at least popular ones should be supported. Like right now Windows 10 which has a huge install base is not supported. |
Beta Was this translation helpful? Give feedback.
-
Based on the discussions here, I have written a blog post guide for my .NET based project that helps users to enable QUIC support which someone here may find useful. |
Beta Was this translation helpful? Give feedback.
-
MsQuic 2.1.8 was released on Friday and the Linux package does have proper dependencies e.g. it won’t silently install but not function if there is no OpenSSL 1.1 (e.g. Ubuntu 22.04) $sudo apt-get install libmsquic
Some packages could not be installed. This may mean that you have
The following packages have unmet dependencies:
libmsquic : Depends: libssl1.1 but it is not installable
E: Unable to correct problems, you have held broken packages. You can either force install without dependencies or swap the order. (see example below) $sudo dpkg -i libssl1.1_1.1.1f-1ubuntu2.17_amd64.deb
Preparing to unpack libssl1.1_1.1.1f-1ubuntu2.17_amd64.deb ...
Unpacking libssl1.1:amd64 (1.1.1f-1ubuntu2.17) ...
Setting up libssl1.1:amd64 (1.1.1f-1ubuntu2.17) ...
Processing triggers for libc-bin (2.35-0ubuntu3) ...
$ sudo apt-get install libmsquic
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
libmsquic
1 upgraded, 0 newly installed, 0 to remove and 224 not upgraded.
Need to get 4,127 kB of archives.
After this operation, 6,144 B of additional disk space will be used.
Get:1 https://packages.microsoft.com/ubuntu/22.04/prod jammy/main amd64 libmsquic amd64 2.1.8 [4,127 kB]
Fetched 4,127 kB in 1s (3,039 kB/s)
(Reading database ... 269943 files and directories currently installed.)
Preparing to unpack .../libmsquic_2.1.8_amd64.deb ...
Unpacking libmsquic (2.1.8) over (2.1.7) ...
Setting up libmsquic (2.1.8) ... Support for OpenSSL 3.x should be in MsQuic 2.2 (works in current main branch) |
Beta Was this translation helpful? Give feedback.
-
.NET 7 has added support for QUIC protocol which right now works only on Windows 11 and Windows Server 2022 out of the box. I have read that it is supported on Linux but does not work and any dependency that is required to be installed is also not documented. It also seems to be still in preview as it requires the code to have
[RequiresPreviewFeatures]
attribute set to compile.So, the question is when can we expect QUIC support to be generally available on all supported platforms?
Beta Was this translation helpful? Give feedback.
All reactions