Bug 184201
Summary: | NetworkManager dropping connection (affecting both e1000 and ipw2200) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dave Maley <dmaley> | ||||
Component: | NetworkManager | Assignee: | Christopher Aillon <caillon> | ||||
Status: | CLOSED NOTABUG | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | rawhide | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-03-09 07:00:43 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
Dave Maley
2006-03-07 06:34:19 UTC
Created attachment 125745 [details]
syslog errors/messages
also should note that wpa_supplicant package is latest rawhide (0.4.8-5) and although it's chkconfig'ed off it does appear to be running in a daemon mode (when wireless), which makes /sbin/service think it's started: [dave@flanders ~]$ sudo chkconfig --list | grep wpa wpa_supplicant 0:off 1:off 2:off 3:off 4:off 5:off 6:off [dave@flanders ~]$ sudo service wpa_supplicant status wpa_supplicant (pid 7971) is running... [dave@flanders ~]$ ps -ef | grep wpa root 7971 1 0 01:45 ? 00:00:00 /usr/sbin/wpa_supplicant -dd -g /var/run/wpa_supplicant-global dave 7994 2611 0 01:45 pts/2 00:00:00 grep wpa ...and doing a `service wpa_supplicant stop` will cause the wireless connection to cease working. Shortly after reporting this bug I started NetworkManager again but left NetworkManagerDispatcher stopped (didn't have anything configured for use w/ dispatcher anyways). And since then I haven't encountered the problem. Is it possible that NetworkManagerDispatcher is actually the cause of this? problem has not re-appeared ... closing |