WebAssembly / WebAssembly/WASI
TCP & UDP: Customize bind behavior
Open
Nobody has claimed this yet.
P-sockets
S-inactive
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
Relevant socket options:
- SO_REUSEADDR
- SO_EXCLUSIVEADDRUSE
- SO_RANDOMIZE_PORT
- SO_RANDOMPORT
- IP_BIND_ADDRESS_NO_PORT
- SO_PORT_SCALABILITY
- SO_REUSE_UNICASTPORT
- SO_REUSEPORT
- SO_REUSEPORT_LB
- SO_ATTACH_REUSEPORT_CBPF
- SO_ATTACH_REUSEPORT_EBPF
- SO_DETACH_REUSEPORT_BPF
- TCP_REUSPORT_LB_NUMA
- SO_INCOMING_CPU
- SO_INCOMING_NAPI_ID
- SO_BINDTODEVICE
- SO_BINDTOIFINDEX
- IP_UNICAST_IF
- IPV6_UNICAST_IF
- IP_BOUND_IF
- IPV6_BOUND_IF
- SO_REUSE_MULTICASTPORT
- IP_FREEBIND
- IPV6_FREEBIND
- IP_TRANSPARENT
- IPV6_TRANSPARENT
- IP_BINDANY
- IPV6_BINDANY
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named in the issue; begin by finding the TCP/UDP bind API and its existing option handling. Done requires an agreed scope and specified behavior for the listed socket options, with coverage for the supported cases.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100