mknod /dev/net/tun fails (not implemented)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
I have a program that wants to create a network tunnel. It's mknod command fails with a not-implemented. It would be nice if this did work, because although I have Windows tunneling properly through this tunnel, the Linux subsystem is not tunnelling like I would expect. Which is very very strange.
Alternatively, if the Linux subsystem didn't (apparently) bypass Winsock, then this would be a non-issue for me personally (although I could see other people wanting to be able to tunnel separately in Bash vs in Windows proper)
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
Start by reproducing the mknod failure for /dev/net/tun in the Linux subsystem and read the issue's discussion about Winsock and tunneling behavior. Determine the expected behavior for creating and using the tunnel; done means the command no longer reports not implemented and the subsystem's tunnel traffic behaves as documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100