http://bugs.winehq.org/show_bug.cgi?id=24150
Summary: Wine does not select the right network interface when vmware network interfaces are up Product: Wine Version: 1.3.1 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: iceclow@gmail.com
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).
http://bugs.winehq.org/show_bug.cgi?id=24150
--- Comment #1 from Juan Lang juan_lang@yahoo.com 2010-08-25 19:21:55 --- (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?
http://bugs.winehq.org/show_bug.cgi?id=24150
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Wine does not select the |The right network interface |right network interface |is not selected when vmware |when vmware network |network interfaces are up |interfaces are up |
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.
http://bugs.winehq.org/show_bug.cgi?id=24150
--- Comment #3 from Juan Lang juan_lang@yahoo.com 2010-08-26 11:33:15 --- In general, Wine doesn't do anything special here: winsock calls are passed more or less unmodified to the sockets code in Linux, so this may be a difference in behavior between Linux and Windows, rather than a Wine bug. Just in case, could you attach a +iphlpapi,+winsock trace?
http://bugs.winehq.org/show_bug.cgi?id=24150
--- Comment #4 from iCeCloW iceclow@gmail.com 2010-08-27 09:47:32 --- Created an attachment (id=30425) --> (http://bugs.winehq.org/attachment.cgi?id=30425) +iphlpapi, +winsock trace running emule.exe
http://bugs.winehq.org/show_bug.cgi?id=24150
--- Comment #5 from iCeCloW iceclow@gmail.com 2010-09-28 15:26:06 CDT --- Did those logs help? If you need more information I really want to help!
(In reply to comment #4)
Created an attachment (id=30425)
--> (http://bugs.winehq.org/attachment.cgi?id=30425) [details]
+iphlpapi, +winsock trace running emule.exe
http://bugs.winehq.org/show_bug.cgi?id=24150
iCeCloW iceclow@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |iceclow@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=24150
--- Comment #6 from Juan Lang juan_lang@yahoo.com 2010-09-28 15:40:36 CDT --- (In reply to comment #5)
Did those logs help? If you need more information I really want to help!
I didn't spot anything in the logs. Could you post the output of route -n both with and without the vmware interfaces up?
http://bugs.winehq.org/show_bug.cgi?id=24150
--- Comment #7 from butraxz@gmail.com 2013-06-09 11:47:11 CDT --- This has not been updated for over 900 days.
Is this still an issue in 1.6-rc1 or higher or is this abandoned ?
https://bugs.winehq.org/show_bug.cgi?id=24150
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #8 from Austin English austinenglish@gmail.com --- (In reply to butraxz from comment #7)
This has not been updated for over 900 days.
Is this still an issue in 1.6-rc1 or higher or is this abandoned ?
Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=24150
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Austin English austinenglish@gmail.com --- Closing.