Bug 374861
| Summary: | NetworkManager Issues | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mike McGuire <mmcguire74> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 8 | CC: | bernd.bartmann, dcbw, tim.liim, twegener, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 0.7.0-0.6.6.svn3109.fc8 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-12-03 05:35:48 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: | |||
|
Description
Mike McGuire
2007-11-10 17:40:24 UTC
issue #1 > 1. Network Manager will not connect using STATIC ip addressing. related bug: bug375481 NM won't work with static IP addressing at this time. What options _do_ show up in the menu when you are allowed to fill in the security details? Does WPA Pre-shared Key do what you need? The options are: wep wpa-psk wpa2-enterprise but the wpa2-psk is missing from the dropdown. Wpa-psk does work but doesn't provide the encryption level that we desire. wpa-psk will actually do both wpa and wpa2, in reality. I've renamed the option to "WPA & WPA2 Personal" which will show up in the next build. Dan...I verified that it will do wpa2 by setting the router to wpa2-personal only, using (AES). I believe in F7 that the system log showed WPA2 as the encryption scheme with the CCMP (aes) cipher. I don't see this in the F8 system log. NetworkManager-0.7.0-0.6.6.svn3109.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager' I just tried the NetworkManager that is currently in the updates-testing repo and it still experiences the same issue with it trying to obtain an ip even though the network configuration is set for STATIC ip addressing. It just won't connect... NetworkManager-0.7.0-0.6.6.svn3109.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report. Why is this bug closed??? There is still issues using the latest NM packages containied in the updates-testing repo. When using STATIC ip addressing NM still tries to to start DHCP. Here is an excerpt from the long. Notice NM trying to start DHCP, I have never run DHCP, the network is set up as STATIC.. Dec 3 03:51:42 localhost NetworkManager: <info> Activation (eth1) Beginning DHCP transaction. Dec 3 03:51:42 localhost NetworkManager: <info> dhclient started with pid 2063 Dec 3 03:51:42 localhost NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete. Dec 3 03:51:42 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.6-Fedora Dec 3 03:51:42 localhost dhclient: Copyright 2004-2007 Internet Systems Consortium. Dec 3 03:51:42 localhost dhclient: All rights reserved. Dec 3 03:51:42 localhost dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Dec 3 03:51:42 localhost dhclient: Dec 3 03:51:42 localhost NetworkManager: <info> DHCP: device eth1 state changed (null) -> preinit Dec 3 03:51:42 localhost dhclient: Listening on LPF/eth1/00:0e:35:d0:e0:43 Dec 3 03:51:42 localhost dhclient: Sending on LPF/eth1/00:0e:35:d0:e0:43 Dec 3 03:51:42 localhost dhclient: Sending on Socket/fallback Dec 3 03:51:42 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8 Dec 3 03:51:50 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13 Dec 3 03:52:03 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13 Dec 3 03:52:16 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10 Dec 3 03:52:26 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 17 Dec 3 03:52:27 localhost NetworkManager: <info> Device 'eth1' DHCP transaction took too long (>45s), stopping it. Dec 3 03:52:27 localhost NetworkManager: <info> eth1: canceled DHCP transaction, dhclient pid 2063 Dec 3 03:52:27 localhost NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Timeout) scheduled... Dec 3 03:52:27 localhost NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Timeout) started... Dec 3 03:52:27 localhost NetworkManager: <info> Activation (eth1) failed for access point (mesa_wifi) Dec 3 03:52:27 localhost NetworkManager: <info> Marking connection 'Auto mesa_wifi' invalid. Dec 3 03:52:27 localhost NetworkManager: <info> Activation (eth1) failed. This bug was closed because the issue with WPA2 Personal was resolved. NM does not yet work with Static IP setups (there's a tracking bug for this already) so if you require static IP at this time, please disable NetworkManager. |