Question about 'iwconfig wlanX ap' command

mrcool at stupidgamerz.com mrcool at stupidgamerz.com
Wed Dec 1 12:35:59 EST 2004


Hello!

Jouni, thanks for your response...  tried your suggestion:

>You might want to
>test with host_roaming=1, which actually allows the firmware to start
>scanning if the client gets disassociated.

I did this yesterday morning.  Within 8 hrs dmesg was giving this:

   A1=00:02:6f:30:82:f0 A2=00:60:b3:8c:77:16 A3=ff:ff:ff:ff:ff:ff
A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
   A1=00:02:6f:30:82:f0 A2=00:60:b3:8c:77:16 A3=ff:ff:ff:ff:ff:ff
A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
   A1=00:02:6f:30:82:f0 A2=00:60:b3:8c:77:16 A3=ff:ff:ff:ff:ff:ff
A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
   A1=00:02:6f:30:82:f0 A2=00:60:b3:8c:77:16 A3=ff:ff:ff:ff:ff:ff
A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
   A1=00:02:6f:30:82:f0 A2=00:60:b3:8c:77:16 A3=ff:ff:ff:ff:ff:ff
A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
   A1=00:02:6f:30:82:f0 A2=00:60:b3:8c:77:16 A3=ff:ff:ff:ff:ff:ff
A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
   A1=00:02:6f:30:82:f0 A2=00:60:b3:8c:77:16 A3=ff:ff:ff:ff:ff:ff
A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
   A1=00:02:6f:30:82:f0 A2=00:60:b3:8c:77:16 A3=ff:ff:ff:ff:ff:ff
A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
   A1=00:02:6f:30:82:f0 A2=00:60:b3:8c:77:16 A3=ff:ff:ff:ff:ff:ff
A4=00:00:00:00:00:00

and I had to loginto the client and change the essid, then change it back,
and it started working again.  Well, the client had a 20 uptime, so I just
rebooted it becuse it was acting like the interface was getting locked...

Overnight syslog filled up with these:

wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID=00:02:6f:30:82:f0
wifi0: Preferred AP BSSID 00:02:6f:30:82:f0
wifi0: using preferred AP selection
wifi0: JoinRequest: BSSID=00:02:6f:30:82:f0 channel=10
wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID=00:02:6f:30:82:f0
wifi0: Preferred AP BSSID 00:02:6f:30:82:f0
wifi0: using preferred AP selection
wifi0: JoinRequest: BSSID=00:02:6f:30:82:f0 channel=10
wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID=00:02:6f:30:82:f0

And then, this morning, I had 4 emails from my monitor program (nagios)
that the unit had failed to respond a few times overnight at 2am and then
at 4am, it then came back up at about 4:19am and has been up since, but
then it has probably been in use mostly since then.

Is this considered normal? Does anyone else have a suggestion to keed this
link up?  I thought using the monitor program itself would have the "keep
alive" effect, but aparently not, so I dont know if a cron-ed ping 'keep
alive' would help any or not.  If more info as to the configurations are
necessary, let me know and I will send a detailed listing of the computers
and their configurations...

Thanks!

Jerryf



More information about the HostAP mailing list