Bug 140760

Summary:	No tun device present
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Michael Stather <kontakt>
Component:	Basesystem	Assignee:	Kay Sievers <kasievers>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	max
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Michael Stather 2005-12-22 15:23:40 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.

Comment 1 Kay Sievers 2005-12-22 15:58:13 UTC

tun is expected to be in /dev/net/tun.

Comment 2 Michael Stather 2005-12-22 17:40:51 UTC

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

Comment 3 Kay Sievers 2005-12-22 20:40:05 UTC

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

Comment 4 Michael Stather 2005-12-22 21:36:51 UTC

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.

Comment 5 Kay Sievers 2005-12-22 21:52:49 UTC

/dev/net/tun is sufficient