wired ethernet disabled between reboots, was: when startup delays become bugs
dcbw at redhat.com
Fri May 17 04:47:21 UTC 2013
On Thu, 2013-05-16 at 21:47 -0400, Nico Kadel-Garcia wrote:
> On Thu, May 16, 2013 at 5:01 PM, Adam Williamson <awilliam at redhat.com> wrote:
> > On Thu, 2013-05-16 at 14:57 -0600, Chris Murphy wrote:
> >> On May 16, 2013, at 2:17 PM, Chris Murphy <lists at colorremedies.com> wrote:
> >> >
> >> > OK well this isn't right. On every reboot, wireless is activated and connected to. But the wired connection is disabled.
> >> https://bugzilla.redhat.com/show_bug.cgi?id=963952
> >> The most relevant line I'm finding is this:
> >> May 16 14:19:22 F19.localdomain NetworkManager: <info> (p5p1): deactivating device (reason 'managed') 
> >> This doesn't happen when booting from Live media, so something's
> >> changed since then it seems. The only two things I can think of are
> >> the groupinstall virtualization, and creating a VM with a NIC set to
> >> bridged mode. But on F18, that same setup doesn't cause this behavior.
> > I was still operating under the belief that KVM bridging isn't really
> > compatible with NM; on my VM host box I disabled NM and used
> > network.service. Is that no longer the case?
> My harsh experience is that server grade networking is not compatible
> with NetworkManager. Pair bonding, trunked VLAN's, and KVM bridging
> all remain unsupported by NetworkManager's GUI's and command line
It didn't used to be very compatible with server-type networking, but
that's exactly what we've been working hard on for the past year or so.
Bonding, bridging, VLANs, an Infiniband are all supported by the current
NetworkManager 0.9.8, though it doesn't (yet) cooperate well when
external tools touch things. That's going to get a lot better quite
soon. The 0.9.8 GUI and nmcli both have support for all of the
aforementioned interface types.
More information about the devel