* why does kernel 3.8-rc1 put all TAP devices into state RUNNING during boot
@ 2013-01-05 10:16 Toralf Förster
2013-01-08 0:27 ` Max Krasnyansky
0 siblings, 1 reply; 2+ messages in thread
From: Toralf Förster @ 2013-01-05 10:16 UTC (permalink / raw)
To: Maxim Krasnyansky; +Cc: Linux Kernel
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 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>"
...
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: why does kernel 3.8-rc1 put all TAP devices into state RUNNING during boot
2013-01-05 10:16 why does kernel 3.8-rc1 put all TAP devices into state RUNNING during boot Toralf Förster
@ 2013-01-08 0:27 ` Max Krasnyansky
0 siblings, 0 replies; 2+ messages in thread
From: Max Krasnyansky @ 2013-01-08 0:27 UTC (permalink / raw)
To: Toralf Förster; +Cc: Linux Kernel, netdev
On 01/05/2013 02:16 AM, Toralf Förster wrote:
> 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 1500
>
> May 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-01-08 0:27 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-05 10:16 why does kernel 3.8-rc1 put all TAP devices into state RUNNING during boot Toralf Förster
2013-01-08 0:27 ` Max Krasnyansky
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox