From: Jason Boxman (jasonb_at_edseek.com)
Date: 2002-07-27 03:24:01 UTC
On Friday 26 July 2002 06:30 am, Jouni Malinen wrote:
> On Mon, Jul 08, 2002 at 10:11:36PM -0400, Jason Boxman wrote:
> > I mentioned this the first time, but no one acknowledged my post, and it
> > seems important, so here it is again:
> >
> > wlan0 hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res =- 110)
> > hostap_pci: wlan0: resetting card
> > **
> > box hangs
>
> Does this still happen with the latest CVS version?
>
> > I'm bridging wlan0 with eth2, a regular Netgear FA PCI card. I didn't
> > experience this behavior during the time I used hostap without bridging.
> >
> > I have WEP disabled. I was copying a large file. Death was abrupt and
> > almost immediate. Actually, the last thing I did was scan for APs on my
> > WPC11v3 and, while connected to the hostap card, proceeded to connect to
> > another AP. Then death.
>
> Hmm.. Did I understood correctly? The host that crashed was using Host
> AP driver with bridging. There was heavy traffic between the AP (using
> Host AP) and the station that started scanning for APs. When the station
> was about to re-associate (while still copying the file?) with another
> AP, the AP (with Host AP) crashed. (?)
Yes, that's exactly how it appeared on my end. This was with the last tar.gz release. I haven't tried to duplicate those conditions with CVS yet.