WSL: mknod `/dev/net /tun' function is not implemented

I’ve installed vpnc (sudo apt-get install vpnc) and tried to run it, but unsuccessfully.

I’ve got this error:

mknod: `/dev/net/tun’: function is not implemented vpnc-connect: can’t initialise tunnel interface: Inappropriate ioctl for device

Any help would be greatly appreciated, as I often need to work through the VPN. Thanks.

About this issue

  • Original URL
  • State: closed
  • Created 10 years ago
  • Comments: 30 (3 by maintainers)

Most upvoted comments

@inakalepsie - Thanks for the feedback. If you would like to setup VPN through WSL, help us prioritize that by also providing that feedback through our user voice page

This is important especially for Cisco IPSec VPN. The only reason I use linux subsystem on windows is to get around the lack of support of cisco ipsec in windows 10 native vpn settings.

But what about WSL1?

Sorry for the late reply. Long weekend here.

Unfortunately I can’t give too many details about the roadmap but I can give some clues. First, if you look at our release notes so far they show off a bit of our priorities (usermode, networking, bug fixes). Second, we have stated publicly that filesystem performance is pretty high on our list. Finally, we really do pay attention to User Voice so expect to see something from that list.

On /dev/net/tun, we do know that we have issues with VPN’s, but we haven’t fully investigated yet. This is one of those situations where we need to prioritize against everything else. As always, User Voice is a great place to vote to help raise visibility.

@JockDaRock Usermode usermode usermode, more interop, and better FS performance

Can’t you set up the tunnel on Windows and then set your routes to use the Windows tunnel?

Yep. I spend some of my day with bits and bytes going through an OpenSSL tunnel via a Windows TAP driver to California. Have since before the OP.

Someone mentioned further back “yes, I could set up VPN tunnel from Windows, but I would prefer to do it from WSL”. Someone is bound to say it again. But that isn’t really a well-formed ask under the present WSL design, since (unlike in a VM) your Windows Network is your WSL network. It is roughly equivalent to “I want to administer my Windows network with the Linux kernel ABI”.

So, yeah, UserVoice, sure – I guess. But there are a lot of technical reasons why that isn’t real feasible, and those reasons don’t have much to do with “tunnels”. [With the obligatory caveat, anything is technically possible even if it isn’t especially feasible.]

[ed] User Voice here and here.

@hiemal, could you please provide output when you do

ipconfig /all

?

I have a fix prepared for DNS resolution when you connect to VPN on windows, but need to verify that your VPN networking interface is reported as point-to-point interface (which is a Windows requirement).