Bugzilla – Bug 140760
No tun device present
Last modified: 2005-12-22 21:52:49 UTC
I don´t know whether this belongs to enhancements or not, but I´m unable to use the vpnc daemon to connect to a VPN network, because there´s no /dev/tun deice present. If I create one with "mknod -m 600 /dev/tun c 10 200" everything works well but after a restart the tun device isn´t there any more. Since VNC connections are a common feature please include a /dev/tun in SuSE by default. I don´t think it hurts when the user doesn´t use vpnc.
tun is expected to be in /dev/net/tun.
The vpnc which can be installed through YaST expects a /dev/tun, it doesn´t work when I don´t create the defvice by hand as shown above
Then it's a bug in one of the components. The vpnc binary expects the node in /dev/net/tun too. What do these commands print on your box: $ rpm -q vpnc $ strings /usr/sbin/vpnc | grep /tun
Sorry it seems like it works now even without the /dev/tun device. I tried it before and vpnc locked up, then I created the /dev/tun and it worked, so I thought this is the issue. So you can close the bug report, thanks for your help.
/dev/net/tun is sufficient