wasi-sockets missing bits · C#/.net-collaboration

Stream: C#/.net-collaboration

Topic: wasi-sockets missing bits

Pavel Šavara (Sep 24 2024 at 15:11):

@Dave Bakker (badeend) and others

I would appreciate your feedback on the set of (posix) features that I found missing in wasi-libc while working on dotnet

please help me to confirm that limitations I listed in the description at the top of my PR are

not going to be implemented, because security, isolation, ... etc.
are just missing right now, but in principle it could be implemented
or I understood something wrong and it should be working already

many thanks!

cc @dicej

[WASI] sockets by pavelsavara · Pull Request #106977 · dotnet/runtime

Limitations permanent design of WASI ? WASIp2 doesn't support SO_LINGER -> PlatformNotSupportedException WASIp2 doesn't support DONTFRAGMENT->IP_MTU_DISCOVER -> PlatformNotSuppor...

Pavel Šavara (Sep 24 2024 at 15:14):

I'm not looking for authoritative answers or fixes. Just for sanity check.

Dave Bakker (badeend) (Sep 24 2024 at 15:41):

I'll look into it later today probably

Dave Bakker (badeend) (Sep 24 2024 at 19:19):

Done

Pavel Šavara (Sep 25 2024 at 11:15):

For mixing pollables https://github.com/WebAssembly/wasi-libc/issues/542

polling on mix of libc-posix socket/file descriptors with non-libc WASI pollable handles · Issue #542 · WebAssembly/wasi-libc

In context of dotnet sockets I would like to be able to wasi:poll_poll on mix of handles which were created by consuming other WASI APIs, like wasi:http and file handles obtained by using libc sock...

Last updated: Dec 13 2025 at 20:04 UTC