gabvil wrote:Maybe something related to the AP and the ath5k module could be the reason.
I have a 5007EG from Atheros and a Linksys router (WRT-320n). Several hours searching for the reason for the constant drop of my connection. I give a chance to the router that was failing in the connection establishment. Ath5k/Ath9k is really mature but not enough to achieve stability. Kernel is the correct one in this case. Do you have madwifi? Could you find something about "ath5k" on /var/log/messages.
Append here the result of this:
- Code: Select all
tail -f /var/log/messages > test_ath5k.txt
Should tell us in the moment of giving the start/restart/stop of this module the behaviour on this while you run the script.
Maybe your router have a log that could give you the clue.
Kind regards.
madwifi is not installed.
Here is the contents of that file:
Apr 1 11:09:10 kiwi sshd[9775]: Received signal 15; terminating.
Apr 1 11:09:11 kiwi avahi-daemon[7270]: Withdrawing address record for 192.168.0.20 on wlan0.
Apr 1 11:09:11 kiwi avahi-daemon[7270]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.20.
Apr 1 11:09:11 kiwi avahi-daemon[7270]: Interface wlan0.IPv4 no longer relevant for mDNS.
Apr 1 11:09:11 kiwi kernel: [ 1525.058086] wlan0: deauthenticating from 00:23:69:23:72:5b by local choice (reason=3)
Apr 1 11:09:11 kiwi kernel: [ 1525.062192] cfg80211: Calling CRDA to update world regulatory domain
Apr 1 11:09:11 kiwi avahi-daemon[7270]: Interface wlan0.IPv6 no longer relevant for mDNS.
Apr 1 11:09:11 kiwi avahi-daemon[7270]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::202:6fff:fe5a:b45c.
Apr 1 11:09:11 kiwi avahi-daemon[7270]: Withdrawing address record for fe80::202:6fff:fe5a:b45c on wlan0.
Apr 1 11:09:33 kiwi /etc/init.d/net.wlan0[10263]: Failed to configure wireless for wlan0
Apr 1 11:09:33 kiwi /etc/init.d/net.wlan0[10100]: ERROR: net.wlan0 failed to start
Apr 1 11:09:49 kiwi /etc/init.d/net.wlan0[10434]: Failed to configure wireless for wlan0
Apr 1 11:09:49 kiwi /etc/init.d/net.wlan0[10271]: ERROR: net.wlan0 failed to start
Apr 1 11:10:01 kiwi cron[10603]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Apr 1 11:10:03 kiwi /etc/init.d/net.wlan0[10617]: Failed to configure wireless for wlan0
Apr 1 11:10:03 kiwi /etc/init.d/net.wlan0[10442]: ERROR: net.wlan0 failed to start
Apr 1 11:10:17 kiwi /etc/init.d/net.wlan0[10788]: Failed to configure wireless for wlan0
Apr 1 11:10:17 kiwi /etc/init.d/net.wlan0[10625]: ERROR: net.wlan0 failed to start
Apr 1 11:10:40 kiwi /etc/init.d/net.wlan0[10796]: net.wlan0: caught SIGINT, aborting
Apr 1 11:10:43 kiwi kernel: [ 1617.571869] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 1 11:10:44 kiwi kernel: [ 1618.781837] wlan0: authenticate with 00:23:69:23:72:5b (try 1)
Apr 1 11:10:44 kiwi kernel: [ 1618.784472] wlan0: authenticated
Apr 1 11:10:44 kiwi kernel: [ 1618.784493] wlan0: associate with 00:23:69:23:72:5b (try 1)
Apr 1 11:10:44 kiwi kernel: [ 1618.787377] wlan0: RX AssocResp from 00:23:69:23:72:5b (capab=0x401 status=0 aid=3)
Apr 1 11:10:44 kiwi kernel: [ 1618.787380] wlan0: associated
Apr 1 11:10:44 kiwi kernel: [ 1618.788531] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Apr 1 11:10:45 kiwi avahi-daemon[7270]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.20.
Apr 1 11:10:45 kiwi avahi-daemon[7270]: New relevant interface wlan0.IPv4 for mDNS.
Apr 1 11:10:45 kiwi avahi-daemon[7270]: Registering new address record for 192.168.0.20 on wlan0.IPv4.
Apr 1 11:10:46 kiwi avahi-daemon[7270]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::202:6fff:fe5a:b45c.
Apr 1 11:10:46 kiwi avahi-daemon[7270]: New relevant interface wlan0.IPv6 for mDNS.
Apr 1 11:10:46 kiwi avahi-daemon[7270]: Registering new address record for fe80::202:6fff:fe5a:b45c on wlan0.*.
Apr 1 11:10:55 kiwi kernel: [ 1629.122019] wlan0: no IPv6 routers present
Apr 1 11:20:01 kiwi cron[11341]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Apr 1 11:30:01 kiwi cron[11371]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Apr 1 11:40:01 kiwi cron[11396]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Apr 1 11:50:01 kiwi cron[11410]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Apr 1 12:00:01 kiwi cron[11431]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Apr 1 12:00:01 kiwi cron[11432]: (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Apr 1 12:10:01 kiwi cron[11444]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Apr 1 12:13:00 kiwi pulseaudio[11510]: ratelimit.c: 2 events suppressed
Apr 1 12:15:00 kiwi avahi-daemon[7270]: Withdrawing address record for 192.168.0.20 on wlan0.
Apr 1 12:15:00 kiwi avahi-daemon[7270]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.20.
Apr 1 12:15:00 kiwi avahi-daemon[7270]: Interface wlan0.IPv4 no longer relevant for mDNS.
Apr 1 12:15:00 kiwi kernel: [ 5474.281975] wlan0: deauthenticating from 00:23:69:23:72:5b by local choice (reason=3)
Apr 1 12:15:00 kiwi kernel: [ 5474.288180] cfg80211: Calling CRDA to update world regulatory domain
Apr 1 12:15:00 kiwi avahi-daemon[7270]: Interface wlan0.IPv6 no longer relevant for mDNS.
Apr 1 12:15:00 kiwi avahi-daemon[7270]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::202:6fff:fe5a:b45c.
Apr 1 12:15:00 kiwi avahi-daemon[7270]: Withdrawing address record for fe80::202:6fff:fe5a:b45c on wlan0.
Apr 1 12:15:40 kiwi /etc/init.d/net.wlan0[11930]: Failed to configure wireless for wlan0
Apr 1 12:15:40 kiwi /etc/init.d/net.wlan0[11767]: ERROR: net.wlan0 failed to start
Apr 1 12:16:53 kiwi /etc/init.d/net.wlan0[11947]: net.wlan0: caught SIGINT, aborting
Apr 1 12:17:10 kiwi kernel: [ 5604.501914] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 1 12:17:11 kiwi kernel: [ 5605.711839] wlan0: authenticate with 00:23:69:23:72:5b (try 1)
Apr 1 12:17:11 kiwi kernel: [ 5605.713399] wlan0: authenticated
Apr 1 12:17:11 kiwi kernel: [ 5605.713421] wlan0: associate with 00:23:69:23:72:5b (try 1)
Apr 1 12:17:11 kiwi kernel: [ 5605.715482] wlan0: RX AssocResp from 00:23:69:23:72:5b (capab=0x401 status=0 aid=3)
Apr 1 12:17:11 kiwi kernel: [ 5605.715486] wlan0: associated
Apr 1 12:17:11 kiwi kernel: [ 5605.716621] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Apr 1 12:17:12 kiwi avahi-daemon[7270]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.20.
Apr 1 12:17:12 kiwi avahi-daemon[7270]: New relevant interface wlan0.IPv4 for mDNS.
Apr 1 12:17:12 kiwi avahi-daemon[7270]: Registering new address record for 192.168.0.20 on wlan0.IPv4.
Apr 1 12:17:13 kiwi avahi-daemon[7270]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::202:6fff:fe5a:b45c.
Apr 1 12:17:13 kiwi avahi-daemon[7270]: New relevant interface wlan0.IPv6 for mDNS.
Apr 1 12:17:13 kiwi avahi-daemon[7270]: Registering new address record for fe80::202:6fff:fe5a:b45c on wlan0.*.
Apr 1 12:17:22 kiwi kernel: [ 5616.290017] wlan0: no IPv6 routers present
------
I don't think it is a faulty wifi driver. I found this link
https://bugzilla.novell.com/show_bug.cgi?id=637183#c5 which caused me to do more testing.
If I run
/etc/init.d/net.wlan0 stop/start or restart
cat: /sys/class/net/wlan0/carrier: Invalid argument
is repeated 10 times then the command aborts with an error.
If I let the command terminate on its own, and run the command again it aborts with an error again; however, if I interrupt the command before it terminates with ^c, the next time I run the command, wlan0 comes up OK. Once wlan0 is up, there are no stability issues, it is rock solid and runs for days with no issues.
I monitored /sys/class/net/wlan0/carrier while running the commands and when wlan0 is up, it has a 1 in it; however, when wlan0 is down, it is empty causing the cat error.
I think this is an issue of incorrect communication with the hardware. Either the wifi card is being put in a dormant state and then not being correctly awoken or the start/restart script has a bug in it checking the carrier file before the wifi card is up under some circumstances. Somehow aborting the command changes something and wlan0 starts.
I have always used iwconfig with wifi. wpa_supplicant is an alternative. Do you know if it does a better job talking to the hardware?