I had similar problems with madwifi myself. It turns out that the packaged version of madwifi in dapper has a known memory leak. I could trigger it when my machine was acting as an access point - just start a file copy and bam!
Since then I tried using madwifi-ng and haven't had the problem since.
How did your testing go with madwifi-ng?
I had similar problems with madwifi myself. It turns out that the packaged version of madwifi in dapper has a known memory leak. I could trigger it when my machine was acting as an access point - just start a file copy and bam!
Since then I tried using madwifi-ng and haven't had the problem since.