Binding onto interface
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- networking
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.
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).
- Dominant language
- C++
- Stars
- 290
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from microsoft/ctsTraffic
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
microsoft/ctsTraffic#39 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
microsoft/ctsTraffic#23 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
microsoft/ctsTraffic#22 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/ctsTraffic#12 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/ctsTraffic#11 ·
All issues in microsoft/ctsTraffic
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
RobotLocomotion/drake#25023 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
mamedev/mame#16263 · 4 comments ·
Maintainers usually reply within 1 day