Your message dated Sun, 10 Jan 2016 21:52:39 +0100
with message-id <[email protected]>
and subject line Re: ifupdown fails to bring up tap interfaces at boot
has caused the Debian Bug report #427417,
regarding ifupdown fails to bring up tap interfaces at boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
427417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427417
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ifupdown
Version: 0.6.8
Severity: Normal
ifupdown fails to bring up the tap interface during boot. If "ifup tap0" is
run after the boot has completed, it works properly all of the time,
including when the tun driver isn't already loaded, so that is only a problem
during boot.
Using a stock Debian kernel (2.6.21 on AMD64 although I saw the same behaviour
with 2.6.18 and 2.6.20), the following messages are generated during boot:
Configuring network interfaces...SIOCSIFADDR: No such device
tap0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
Failed to bring up tap0
done
Loading the tun driver after attempting to bring up the device is obviously a
problem (assuming that the load messages aren't delayed). As such, a test
with the tun driver loaded via /etc/modules yields the following output
during boot:
Configuring network interfaces...SIOCSIFADDR: No such device
tap0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: Cannot assign requested address
Failed to bring up tap0
done
Running ifconfig after booting with the tap module loaded via /etc/modules
yields the following output for tap0:
tap0 Link encap:Ethernet HWaddr 2E:1C:30:A7:9C:C2
inet6 addr: fe80::2c1c:30ff:fea7:9cc2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:53 (53.0 b) TX bytes:468 (468.0 b)
Without loading the modules via /etc/modules ifconfig yields no output for
tap0. I have seen similar behaviour with the tap driver statically linked
into a custom kernel, however it wasn't as consistent, there were a a few
times where it would actually work.
Here is the contents of /etc/network/interfaces.
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
auto tap0
iface tap0 inet static
address 172.24.0.1
netmask 255.255.255.0
vde2-switch -
James
--- End Message ---
--- Begin Message ---
Modprobing tun does not create any tap devices. Instead, these devices
are created on demand when another process opens /dev/net/tun and
requests that a network interface is created. So either that process has
to call "ifup tap0", or you have to start that process from a pre-up
line in the tap0 stanza. Another possibility is perhaps to have
"allow-hotplug tap0" instead of "auto tap0".
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
