microsoft / microsoft/ctsTraffic
Binding onto interface
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 289
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
It seems like the binding onto an interface is broken. I can specify the interface alias through compartment but it allows traffic over other interfaces because they're in the same compartment (adding new compartments is currently broken using netsh).
Contributor guide
No contributing guide indexed for this repository
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
Start by tracing how ctsTraffic applies a compartment-specified interface alias to its socket binding. Reproduce the reported case with multiple interfaces in the same compartment and verify whether traffic uses interfaces other than the selected one. Done means traffic is restricted to the specified interface, or the remaining limitation is documented if netsh cannot create the needed compartments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100