Nick Banks
Nick Banks
Should we make this "Not Supported" in user mode until/if we test/support it really?
@anrossi is going to reach out to .NET to see if they use this or plan to use this in .NET 7.
No known users outside of HTTP.sys currently.
Yes, if some app reserves ports (port exclusions) then it's by design that your QUIC app cannot use it. I'm not sure what you want MsQuic to do here.
MsQuic grabs a port reservation on Windows (to deal with the other bug .NET brought about MsQuic incorrectly sharing ports) to restrict access to just the current process, but still...
We opened this internal bug to track possibly support this scenario in Windows: - [Bug 40464377](https://microsoft.visualstudio.com/OS/_workitems/edit/40464377): Apps that create port reservations for binding are blocked by port exclusions
FYI, here's a repo with a good start we can work from: https://github.com/wkgcass/msquic-java (thanks @wkgcass!).
@newlunarfire we'd love any help you'd like to contribute!
I did not enable it on OSX, because I didn't have a local system to try it on. It _might_ work there if you enable it.
A bit more on this: Normally, the client doesn't set `SO_REUSEPORT` on the socket **unless** UDP port sharing has been explicitly enabled on the client. And this test case is...