When can support the capture of wireguard protocol messages
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
/*
- These are the types that are the same on all platforms, and that
- have been defined by <net/bpf.h> for ages.
/
#define DLT_NULL 0 / BSD loopback encapsulation /
#define DLT_EN10MB 1 / Ethernet (10Mb) /
#define DLT_EN3MB 2 / Experimental Ethernet (3Mb) /
#define DLT_AX25 3 / Amateur Radio AX.25 /
#define DLT_PRONET 4 / Proteon ProNET Token Ring /
#define DLT_CHAOS 5 / Chaos /
#define DLT_IEEE802 6 / 802.5 Token Ring /
#define DLT_ARCNET 7 / ARCNET, with BSD-style header /
#define DLT_SLIP 8 / Serial Line IP /
#define DLT_PPP 9 / Point-to-point Protocol /
#define DLT_FDDI 10 / FDDI */
At present, it supports the above 10 kinds. I hope it can support wireguard for Windows. Thank you
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 with the DLT_* definitions shown in the issue and inspect how Npcap maps supported link-layer types on Windows. Determine how WireGuard protocol messages should be represented in the capture path; done means WireGuard traffic can be captured consistently on Windows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100