| Summary: | Atheros wireless card won't stay connected with baselayout 1.12.1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Michael T <thayer> |
| Component: | [OLD] baselayout | Assignee: | Roy Marples (RETIRED) <uberlord> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | mobile+disabled |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Michael T
2006-07-21 02:05:34 UTC
I meant -Bw of course. And it obviously does not work "out of the box" with baselayout 1.11 as dhcp is not started. Would probably take some fiddling to work out how to do it properly. Next thought on the matter - perhaps dhcp could be left running when the "wireless disconnected" event is received, and only stopped if no "connected" event is received in the next, say, sixty seconds. Are you using ifplugd to control ath0? If so, don't! Also, what dhcp client are you using? Lastly, please attach your conf.d/net and test using baselayout-1.12.2 refreshly released. Same results with baselayout 1.12.2. I am not using ifplugd, and my dhcp client is dhcpcd. conf.d/net contains just: modules=( "wpa_supplicant" ) wpa_supplicant_ath0="-Dmadwifi" Extract from the system log (after emerging the new baselayout and restarting net.ath0): [...] Aug 1 21:28:31 [wpa_cli] interface ath0 CONNECTED Aug 1 21:28:32 [rc-scripts] Configuration not set for ath0 - assuming DHCP Aug 1 21:28:32 [dhcpcd] MAC address = 00:0e:9b:a2:91:ae Aug 1 21:28:32 [dhcpcd] verified 192.168.178.21 address is not in use Aug 1 21:28:32 [dhcpcd] your IP address = 192.168.178.21 [...] Aug 1 21:28:42 [dhcpcd] terminating on signal 15 [...] Aug 1 21:29:01 [wpa_cli] interface ath0 DISCONNECTED Aug 1 21:29:12 [wpa_cli] interface ath0 CONNECTED Aug 1 21:29:12 [rc-scripts] Configuration not set for ath0 - assuming DHCP Aug 1 21:29:12 [dhcpcd] MAC address = 00:0e:9b:a2:91:ae Aug 1 21:29:13 [dhcpcd] verified 192.168.178.21 address is not in use Aug 1 21:29:13 [dhcpcd] your IP address = 192.168.178.21 [...] Aug 1 21:29:21 [rc-scripts] WARNING: openvpn.innotek has not yet been started. Aug 1 21:29:22 [wpa_cli] interface ath0 DISCONNECTED Aug 1 21:29:22 [dhcpcd] terminating on signal 15 Aug 1 21:29:32 [wpa_cli] interface ath0 CONNECTED Aug 1 21:29:33 [rc-scripts] Configuration not set for ath0 - assuming DHCP Aug 1 21:29:33 [dhcpcd] MAC address = 00:0e:9b:a2:91:ae Aug 1 21:29:33 [dhcpcd] verified 192.168.178.21 address is not in use Aug 1 21:29:33 [dhcpcd] your IP address = 192.168.178.21 Aug 1 21:29:42 [wpa_cli] interface ath0 DISCONNECTED Aug 1 21:29:43 [dhcpcd] terminating on signal 15 [...] Aug 1 21:30:23 [wpa_cli] interface ath0 DISCONNECTED Aug 1 21:30:34 [wpa_cli] interface ath0 CONNECTED Aug 1 21:30:34 [rc-scripts] Configuration not set for ath0 - assuming DHCP Aug 1 21:30:34 [dhcpcd] MAC address = 00:0e:9b:a2:91:ae Aug 1 21:30:35 [dhcpcd] verified 192.168.178.21 address is not in use Aug 1 21:30:35 [dhcpcd] your IP address = 192.168.178.21 [...] I think this may be related: http://www.mail-archive.com/networkmanager-list%40gnome.org/msg00086.html Unfortunately, the new baselayout seems (?) to think that these scanning pauses are disconnections, and restart dhcpcd, so that half the connected time is spent obtaining an IP address. Looking at the logs in my router, I can also see lots of disconnections and reconnections. As I said, ifplugd had the same problem, which is why I stopped using it for wireless. (In reply to comment #4) > Unfortunately, the new baselayout seems (?) to think that these scanning pauses > are disconnections Actually wpa_supplicant is saying that the association has been lost. The only difference between versions is that 1.12 uses wpa_cli to monitor wpa_supplicant to start and stop dhcp and others if wpa_supplicant looses association. 1.11 does not do this and this is what you are seeing. So therefore it's an error with wpa_supplicant, madwifi, the hardware used or just a very unreliable signal Hm, just checked again, and this time after 30 minutes connection, there is nothing in the system log (or the router's log) about lost connections. I will keep observing it from time to time. |
