Summary: | Strange disassociates on madwifi-ng-0.9.x, but not on 0.0.1531 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jozsef Daniel <simius> |
Component: | Current packages | Assignee: | Steev Klimaszewski (RETIRED) <steev> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | mobile+disabled |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jozsef Daniel
2006-10-01 11:57:38 UTC
What the holy cow is going on with this bug? Am I the only one on Earth who has experienced it? I mean, for me it was rather consistent. And now the old madwifi-ng versions got removed. If there is a known workaround, it is not critical. While I may be the maintainer, I do not have the hardware, I have semi-easy access to it (a co-worker has a card that I can use from time to time.) I haven't seen anyone else report this, so yes, it IS possible that you are the only one experiencing this. If you would care to donate the hardware so that I could better deal with bugs with madwifi-ng in a more timely manner to your satisfaction, then I would be greatly appreciative. As it stands, I cannot reproduce this, and no one else has seemed to. I finally found a solution. Applying the madwifi-association-fix.patch fixes the problem, and seemingly improves the stability of the association greatly. I use a US Robotics wireless router as an access point, with WPA-PSK by wpa-supplicant. As this patch does seem to cause trouble for some (bug#146459), but is needed in other setups, I suggest using a new USE flag for toggling it until it becomes unnecessary. |