[ previous ] [ next ] [ threads ]
 
 From:  Phill R Kenoyer <phill at bmg50 dot com>
 To:  'M0n0Wall' list <m0n0wall at lists dot m0n0 dot ch>
 Subject:  confirmed wifi problem still exists.
 Date:  Fri, 26 Nov 2004 22:05:55 -0800
I did a test this morning on m0n0wall to see if the wifi bug still 
exists in the hostap mode drivers.  It does.

Nov 26 03:11:18 ap2 /kernel: wi1: timeout in wi_seek to 1e3/0; last 
status 81e3
Nov 26 03:11:18 ap2 /kernel: wi1: timeout in wi_seek to 15e/3c; last 
status 8000
Nov 26 03:11:18 ap2 /kernel: wi1: timeout in wi_cmd 0x010b; event 
status 0x0000
Nov 26 03:11:18 ap2 /kernel: wi1: xmit failed
Nov 26 03:11:18 ap2 /kernel: wi1: wi_cmd: busy bit won't clear.
Nov 26 03:11:18 ap2 /kernel: wi1: xmit failed
Nov 26 03:16:24 **********  netcheck: ap2 DOWN!  **********

If your connected to m0n0wall using wirelss 802.11b and put your client 
wifi card into "power save mode" then the wifi card on m0n0wall will 
lockup.  The only way I know of to fix this is to have m0n0wall reboot 
when the error is detected.

This week I'm going to try and figure out a way to get a shell script 
to run on the box and check for the error message.  When found it will 
reboot.

Note: Hostap on Linux does not suffer from this problem.

I don't know, but maybe upgrading the hostap drivers in the FreeBSD 
kernel will fix it?

Anyway, I'll let you all know if I'm successful in getting my script to 
run on m0n0wall.