Bug 569024
| Summary: | NetworkManager will not connect to the network | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dale Snell <dbuggzie> | ||||||
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 12 | CC: | dcbw, jklimes | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-08-17 16:31:18 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Dale Snell
2010-02-27 17:26:07 UTC
Is it still problem with the latest upgrade? If so, please include: 1. output of nm-tool 2. /var/log/messages Thanks. I upgraded to the latest version in updates-testing, and the problem is still there. If it helps any, this machine is a Dell Inspiron 9300 laptop. It has a Broadcom BCM4401-B0 Ethernet NIC (eth0) and an Intel PRO/Wireless 2915ABG [Calexico2] wireless NIC. The driver for eth0 is b44; the wireless device is shut off in the BIOS since I almost never use it. I'll upload the output of nm-tool and the relevant portion of /var/log/messages as separate attachments. Created attachment 406595 [details]
The output of nm-tool.
Created attachment 406596 [details]
/var/log/messages
comment #4: Apr 14 11:12:17 localhost NetworkManager: <info> (eth0): IP6 addrconf timed out or failed. Your connection has probably IPv6 method set to "Automatic". That's why NM tries to configure IPv6, but it times out (your network is probably not IPv6-enabled). So NM marks the connection as invalid even if IPv4 succeeded. I think it could be regarded as a bug. We may just issue a warning that IPv6 is not available and continue with IPv4 only. To resolve the issue, open nm-connection-editor: 1. click on "System eth0" connection on "Wired" tab 2. click "Edit..." 3. click "IPv6 Settings" tab 4. change Method from "Automatic" to "Ignore" 5. click Apply For reference, I think it is the same issue as bugs: bug 565926 bug 567978 bug 569192 That fixed it! As soon as I hit "Apply" the little green lights spun around and then everything was connected. Thank you! This sure looks like a repeat of the other bugs you referenced. My DSL modem/router is IPv4 only, so I've never bothered with IPv6. Sounds to me like Anaconda set things up correctly during installation, but something in the update changed the settings. What's really odd is that it only happened on the Dell machine. My IBM T40 was happy as a clam with NetworkManager. It never occurred to me that the settings would be different. Unfortunately I can't check the T40's settings, since its display died just after this mess started. A couple days ago, though, I bought a 64-bit AMD Sempron desktop system, and it has no trouble. I just checked its settings for NetworkManager, and lo and behold, IPv6 was set to "Ignore." Sunspots and gremlins? :-) This got fixed in the run-up to F13 and the update was rolled out right after that as well. *** This bug has been marked as a duplicate of bug 567978 *** |