misc/90413: tap0 interface not configured at boot-time

Guido Boehm send-pr.fbsd at lenix.de
Wed Dec 14 17:50:03 PST 2005


>Number:         90413
>Category:       misc
>Synopsis:       tap0 interface not configured at boot-time
>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:   Thu Dec 15 01:50:02 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Guido Boehm
>Release:        6.0-STABLE
>Organization:
>Environment:
FreeBSD xyz.unixuni.net 6.0-STABLE FreeBSD 6.0-STABLE #2: Fri Dec  9 01:44:12 CET 2005 root at xyz.unixuni.net:/usr/obj/usr/src/sys/XYZ  i386
>Description:
adding a "tap0"-interface to "network_interfaces" or "cloned_interfaces" in 
"/etc/rc.conf" results in this message repeated two times during system startup:
  "ifconfig: interface tap0 does not exist"

"device tap" is in kernel-configuration, "openvpn" can open and utilize "tap0"
without any problems.

i use "/etc/start_if.tap0" as a workaround:
 $ cat /etc/start_if.tap0 
 #!/bin/sh
 echo 1 > /dev/tap0

for me this is important since "named" couldn't bind to that interface/ip 
otherwise, by the time "openvpn" allocates it "named" has already dropped 
priviliges (running as user "bind")
>How-To-Repeat:
see description
>Fix:
              
>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list