Re: No IP4 address after NetworkManager update

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Community assistance, encouragement, and advice for using Fedora." <fedora-list@xxxxxxxxxx>
Subject: Re: No IP4 address after NetworkManager update
From: Mike Wohlgemuth <mjw@xxxxxxxxxx>
Date: Tue, 10 Mar 2009 08:05:36 -0400
In-reply-to: <20090310101356.26bf4d6f@xxxxxxxxxxxxxx>
References: <20090310101356.26bf4d6f@xxxxxxxxxxxxxx>
Reply-to: "Community assistance, encouragement, and advice for using Fedora." <fedora-list@xxxxxxxxxx>
User-agent: Thunderbird 2.0.0.19 (X11/20090105)

Mark Knoop wrote:

Yesterday's updates included:

Mar 09 09:44:45 Updated: 1:NetworkManager-glib-0.7.0.99-1.fc10.i386
Mar 09 09:44:50 Updated: 1:NetworkManager-0.7.0.99-1.fc10.i386

On booting this morning, NetworkManager fails to bring up eth0
completely - it gets an IPV6 address, but no IP4, and my router can't
see the box.

...

Any ideas?

No ideas, just a me too.

Woogie

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Follow-Ups:
- Re: No IP4 address after NetworkManager update
  - From: Robert Locke
- Re: No IP4 address after NetworkManager update
  - From: Aaron Konstam

References:
- No IP4 address after NetworkManager update
  - From: Mark Knoop

Prev by Date: Re: getting the F10 respin with "jigdo" -- the short version
Next by Date: Re: yum updates reports a NetworkManager Conflict...
Previous by thread: No IP4 address after NetworkManager update
Next by thread: Re: No IP4 address after NetworkManager update
Index(es):
- Date
- Thread

[Index of Archives] [Current Fedora Users] [Fedora Desktop] [Fedora SELinux] [Yosemite News] [Yosemite Photos] [KDE Users] [Fedora Tools] [Fedora Docs]