TCP traceroute doesn't show hops icmp works fine
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
- ocaml
- Domain
- networking
Research direction
Start by reviewing the existing ICMP/UDP traceroute work and the linked Docker for Mac issue 4833 to understand the TCP failure. Done means TCP traceroute reports network hops in the same useful way as the working ICMP and UDP paths.
Written by the indexing model from the issue text.
Description
It looks like there was some work done previously to fix this for ICMP/UDP but it would be great if TCP was supported as it will better show the user path through the network. Any chance this could be looked into and fixed?
issue 4833
Thank you.
- Dominant language
- OCaml
- Stars
- 1.2k
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Getting set up
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 moby/vpnkit
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
flaky-test
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
vacp2p/nim-libp2p#3194 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
permissionlesstech/bitchat#1743 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Sendspin/aiosendspin#447 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100