Please merge madwifi-ng patches to allow VMware bridged networking to work stably

[Scott Henson]

Basically the madwifi-ng driver returns something that vmware doesn't like. This is current edgy. I'll link in a bug report that has a patch.

[Scott Henson (scotth)]

http://madwifi.org/ticket/407

[Scott Henson (scotth)]

There seems to be a fix for this bug in the madwifi-trac ticket. It involves commenting out a few lines in the driver and an updated version of vmware. Could we maybe get it fixed?

[Stéphane Graber (stgraber)]

It's not only related to vmware-player, it also appears with vmware-server and vmware workstation.
For vmware Workstation it's still here even in the latest beta version.
Commenting the lines in the source code of madwifi and recompiling it fix the issue.

[VMware Build Team (vmware-builds)]

This sounds like a madwifi issue. I'm not aware of problems with any other network drivers. Please reopen if you feel otherwise.

[Sergio Zanchetta (primes2h)]

The 18 month support period for Feisty Fawn 7.04 has reached its end of life some months ago.
As a result, we are closing the linux-restricted-modules-2.6.20 task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Thanks in advance!

[Przemek K. (azrael)]

Madwifi is deprecated now. Please use the ath5k or ath9k driver