http://bugs.winehq.org/show_bug.cgi?id=24150
--- Comment #2 from iCeCloW iceclow@gmail.com 2010-08-26 04:57:44 --- (In reply to comment #1)
(In reply to comment #0)
When using any windows program through wine, if the vmware virtual network interfaces (vmnet0, vmnet1 ...) are up vmware incorrectly selects those virtual interfaces for networking instead of the correct one (wlan0).
I assume you mean, any Wine process selects the wrong interface, rather than vmware? If vmware is selecting the wrong interface, that's a vmware bug.
How do you determine which interface the app is selecting? Can you provide at least one app that does this, along with steps to reproduce it?
You are right, I meant that wine incorrectly selectes the network interface to use in windows program, sorry.
An easy program to test this withis eMule. eMule has a web server and with that feature enable in preferences, you can see the ip address the web server is using on the servers tab, in the right panel. If vmware interfaces are up, the web server takes the ip adress from those virtual interfaces. If you disable the vmware network interfaces (through Vmware's Virtual Network Editor) the emule web server gets the right ip from wlan0. Also while the vmware interfaces are up, the program is unable to connect.