* Re: why does kernel 3.8-rc1 put all TAP devices into state RUNNING during boot
[not found] <50E7FD79.1080605@gmx.de>
@ 2013-01-08 0:27 ` Max Krasnyansky
0 siblings, 0 replies; only message 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] only message in thread
only message in thread, other threads:[~2013-01-08 0:27 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <50E7FD79.1080605@gmx.de>
2013-01-08 0:27 ` why does kernel 3.8-rc1 put all TAP devices into state RUNNING during boot Max Krasnyansky
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).