Wireless card drops default route when inactive

Discussion in 'Linux Networking' started by cjcoriale, Aug 25, 2005.

  1. cjcoriale

    cjcoriale Guest

    Hi all,

    I am having an issue with my Netgear WG311v2 wireless card. I recently
    got it working using the ACX100 driver for the Texas Instrument acx111
    chipset that the card has. The problem is that when I let the machine
    sit idle and go back to use it, the default route is no longer there
    and it has to be restored manually, even though I noticed that doing a
    ping will restore it, but simply using a browser will not.
    I am running FC3, kernel 2.6.9-1.667
    driver version = acx100-0.2.0pre8_plus_fixes_51 and firmware version
    that I got off of the Windows driver cd. I've tried other firmware
    versions from web with the same results.

    Here is a snippet of the log file with definite suspect statements, but
    I am not certain they are the contributing factor to the problem. The
    DEAUTHEN line seems like an issue along with the NETDEV WATCHDOG
    timeout:


    Aug 25 08:46:12 sweetwater kernel: DEAUTHEN <4>00:0f:b5:43:61:13
    <4>00:0f:b5:43:61:13 <4>00:12:17:11:b0:12 <4>00:12:17:11:b0:12
    <4>00:12:17:11:b0:12
    Aug 25 08:46:12 sweetwater kernel: Processing deauthen packet. Hmm,
    should this have happened?
    Aug 25 08:46:12 sweetwater kernel: acx_set_status: Setting status = 2
    (WAIT_AUTH)
    Aug 25 08:46:12 sweetwater kernel: <acx_set_timer> Elapse = 1500000
    Aug 25 08:46:14 sweetwater kernel: acx_timer: status = 2
    Aug 25 08:46:14 sweetwater kernel: resend authen1 request (attempt 2).
    Aug 25 08:46:14 sweetwater kernel: Sending authentication1 request,
    awaiting response!
    Aug 25 08:46:14 sweetwater kernel: <acx_set_timer> Elapse = 2500000
    Aug 25 08:46:14 sweetwater kernel: 00:0f:b5:43:61:13
    <4>00:0f:b5:43:61:13 <4>00:12:17:11:b0:12 <4>00:12:17:11:b0:12
    <4>00:12:17:11:b0:12
    Aug 25 08:46:14 sweetwater kernel: Algorithm is ok
    Aug 25 08:46:14 sweetwater kernel: acx_process_authen auth seq step 2
    Aug 25 08:46:14 sweetwater kernel: acx_set_status: Setting status = 3
    (AUTHENTICATED)
    Aug 25 08:46:14 sweetwater kernel: <acx_set_timer> Elapse = 1500000
    Aug 25 08:46:14 sweetwater kernel: Sending association request,
    awaiting response! NOT ASSOCIATED YET.
    Aug 25 08:46:14 sweetwater kernel: association: requesting capabilities
    0x0001
    Aug 25 08:46:14 sweetwater kernel: acx_set_status: Setting status = 4
    (ASSOCIATED)
    Aug 25 08:46:14 sweetwater kernel: ASSOCIATED!
    Aug 25 08:46:15 sweetwater kernel: acx_timer: status = 4
    Aug 25 08:46:24 sweetwater kernel: Got Info IRQ: status 0x0002, type
    0x4100: (unknown)
    Aug 25 08:46:26 sweetwater last message repeated 2 times
    Aug 25 09:01:01 sweetwater crond(pam_unix)[9578]: session opened for
    user root by (uid=0)
    Aug 25 09:01:01 sweetwater crond(pam_unix)[9578]: session closed for
    user root
    Aug 25 09:03:06 sweetwater kernel: NETDEV WATCHDOG: wlan0: transmit
    timed out
    Aug 25 09:03:06 sweetwater kernel: acx100: Tx timeout!
    Aug 25 09:03:06 sweetwater kernel: recalibrating ACX111 radio. Not
    tested yet, please report status!!
    Aug 25 09:03:06 sweetwater kernel: successfully recalibrated radio



    Any info would be appreciated.
    Thanks in advance.
    Chris.
     
    cjcoriale, Aug 25, 2005
    #1
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.