kern/55917: tun# devices cannot be created in 4.8-STABLE
Jukka A. Ukkonen
jau at mawit.com
Sun Aug 24 01:20:19 PDT 2003
>Number: 55917
>Category: kern
>Synopsis: tun# devices cannot be created in 4.8-STABLE
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Aug 24 01:20:16 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator: Jukka A. Ukkonen
>Release: FreeBSD 4.8-STABLE i386
>Organization:
Mawit Ltd.
>Environment:
System: FreeBSD hvergelmir.thunderbolt.fi 4.8-STABLE FreeBSD 4.8-STABLE #0: Sun Aug 24 10:15:57 EEST 2003 root at hvergelmir.thunderbolt.fi:/usr/src/sys/compile/hvergelmir i386
>Description:
It does not seem to make any difference whether one configures
pseudo-device tun
in the kernel or not. When trying ifconfig -a no tun# devices
are listed. Creating one with ifconfig tun0 create fails.
When trying kldload /modules/if_tun.ko kernel complains that
the device or module is already present. (Which it should be
of course when compiled in the config phase.)
>How-To-Repeat:
# kldstat
Should show no if_tun.ko.
# ifconfig -a
Should show no tun0 etc.
# ifconfig tun0 create
Fails complaining about SIOCIFCREATE and wrong argument.
# kldload /modules/if_tun.ko
Complaint about the module already being present.
>Fix:
None known yet.
The symptoms make me suspect the call parameters to ioctl
SIOCIFCREATE might have changed in the kernel, but the
user-land has not kept up. - This guess might be totally
in the woods. It is just the first potential explanation
that occured to me.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list