why does kernel 3.8-rc1 put all TAP devices into state RUNNING during boot
Subsystems (2)
At my stable Gentoo Linux I'm observed a change behaviour for the configured TAP devices after the boot process.
$ diff 3.7.1 3.8.0-rc1+ | grep UP < br0: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500
Quoted 1 line
br0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
< tap0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
Quoted 1 line
tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
May I ask you if this changed behaviour is intended ?
FWIW I configured those devices at that system in this way :
$ head -n 20 /etc/conf.d/net # /etc/conf.d/net #
# KVM
#
bridge_br0="tap0 tap1 tap2 tap3" config_br0="192.168.0.254/8"
brctl_br0="setfd 0
sethello 10
stp off"
rc_net_br0_need="net.tap0 net.tap1 net.tap2 net.tap3"
config_tap0="null"
tuntap_tap0="tap"
tunctl_tap0="-u <me>"
...
Signature · 3 lines
MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
Quoted 10 lines · Toralf Förster
At my stable Gentoo Linux I'm observed a change behaviour for the configured TAP devices after the boot process.
$ diff 3.7.1 3.8.0-rc1+ | grep UP - br0: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500 + br0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 - tap0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 + tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500May I ask you if this changed behaviour is intended ?
I'm not aware of any changes in this behavior.
btw Looks like it changed for your bridge interfaces as well. So it's not really specific to the TAP devices.
Someone from netdev would know :)
Max