Re: why does kernel 3.8-rc1 put all TAP devices into state RUNNING during boot

2013-01-07 Thread Max Krasnyansky
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 mtu 1500 >+ br0: flags=4419 mtu 1500 >- tap0: flags=4099 mtu 1500 >+ tap0:

Re: why does kernel 3.8-rc1 put all TAP devices into state RUNNING during boot

2013-01-07 Thread Max Krasnyansky
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=4355UP,BROADCAST,PROMISC,MULTICAST mtu 1500 + br0:

why does kernel 3.8-rc1 put all TAP devices into state RUNNING during boot

2013-01-05 Thread 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 mtu 1500 > br0: flags=4419 mtu 1500 < tap0: flags=4099 mtu 1500 > tap0: flags=4163 mtu 1500 May I ask you if this changed

why does kernel 3.8-rc1 put all TAP devices into state RUNNING during boot

2013-01-05 Thread 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=4355UP,BROADCAST,PROMISC,MULTICAST mtu 1500 br0: flags=4419UP,BROADCAST,RUNNING,PROMISC,MULTICAST mtu 1500 tap0: