http://bugs.winehq.org/show_bug.cgi?id=17432
Summary: Lan hosting/listening not working in warcraft iii. Product: Wine Version: 1.1.14 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: whellmundv@gmail.com
I thought warcraft was one game that ran as fluent as if it was native, or so I thought then. Today I've found myself experimenting for the second time how running this masterpiece from wine prevents me from enjoying a nice lan game with my friends, using both macintosh and windows systems.
I don't know why, but I guess that is the reason for which I encounter myself writing this, at this precise moment: I think you will help me solve this--I believe, uncommon--problem.
Please let me know which information do I need to post here, because I know not with accuracy.
http://bugs.winehq.org/show_bug.cgi?id=17432
--- Comment #1 from Austin English austinenglish@gmail.com 2009-02-17 01:19:38 --- Dupe of bug 9787?
http://bugs.winehq.org/show_bug.cgi?id=17432
Damjan Jovanovic damjan.jov@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |damjan.jov@gmail.com Ever Confirmed|0 |1
--- Comment #2 from Damjan Jovanovic damjan.jov@gmail.com 2009-07-04 07:16:51 --- I've seen this too sometimes, time for detailed testing.
Ubuntu 9.04 + self compiled Wine 1.1.25, versus Windows Vista. Gigabit LAN crossover cable between the 2 machines. Firewalls off. Ping and TCP connections tested in both directions and work.
WARNING: this is a long post, the summary is at the bottom.
====================== Unpatched Wine hosting ====================== If Vista is already in the "Local Area Network" screen when Wine starts hosting, the game can't be seen in Vista. However if you go back to the main screen, then to "Local Area Network" screen again you can see the game, but trying to join it gives "Unable to join the specified game. Please try again or select a different game".
Same thing happens if Vista only tries to enter the "Local Area Network" screen after Wine starts hosting.
The following FIXMEs appear in the Wine terminal when you start hosting, whether you try to join Wine's game or not:
fixme:winsock:WSAIoctl unsupported WS_IOCTL cmd (9800000c) fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {b5367df1-cbac-11cf-95ca-00805f48a192}: stub fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {b5367df2-cbac-11cf-95ca-00805f48a192}: stub fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {b5367df0-cbac-11cf-95ca-00805f48a192}: stub
====================== Unpatched Wine joining ====================== Wine sees the game (even if already in the "Local Area Network" screen), successfully joins, and plays!
Same FIXMEs from before though - maybe they don't break anything?
==================== Patched Wine hosting ==================== With the patch from bug #9787 applied to Wine, Vista only sees the game when first entering the "Local Area Network" screen like before, but this time it can join and plays fine!
This time there is only this FIXME: fixme:winsock:WSAIoctl unsupported WS_IOCTL cmd (9800000c)
So maybe it's the other FIXMEs that break it (too), not just bug #9787?
==================== Patched Wine joining ==================== With the patch from bug #9787 applied to Wine, Wine can see the game, does join and plays fine!
Also only this FIXME: fixme:winsock:WSAIoctl unsupported WS_IOCTL cmd (9800000c)
======================== Visibility investigation ======================== Why does Vista only see new games when entering the "Local Area Network" screen?
Tried switching off my 3G card on Linux so I only have 1 network interface => didn't help.
tcpdump and Wireshark seem to not capture a single packet. Maybe some networking problem that stops packets from being generated in the first place?
In a +winsock trace we see this getting tried every few seconds:
trace:winsock:WSASendTo socket 216c, wsabuf 0x33f528, nbufs 1, flags 0, to 0x33fb70, tolen 16, ovl (nil), func (nil) trace:winsock:WSASendTo fd=22, options=0 warn:winsock:wsaErrno errno 101, (Network is unreachable). warn:winsock:WSASendTo -> ERROR 10051
Adding some more tracing to the WSASendTo call we see where it's trying to send: trace:winsock:WSASendTo to = 255.255.255.255
$ ping 255.255.255.255 connect: Network is unreachable
So what if we add a route to that network?
$ sudo route add -net 255.255.255.255 netmask 255.255.255.255 dev eth0
and to check:
$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 255.255.255.255 0.0.0.0 255.255.255.255 UH 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
Vista now sees Wine hosted games made while already in the "Local Area Network" screen just fine!
================== Other known issues ================== Don't even try to play this over WiFi - it doesn't work on Vista itself half the time (some people can't listen/join, etc.). Also firewalls often break this game (among almost everything else :-) so they were off for my test.
======= Summary ======= 2 problems here:
1. Windows can only see Wine hosted games when it re-enters the "Local Area Network" screen. - Need to route 255.255.255.255/32 to the local LAN in Linux
2. Windows can't connect to visible Wine hosted games. - Unclear, the patch for #9787 fixes it, but it could also be Wine's lack of support for the SIO_GET_EXTENSION_FUNCTION_POINTER ioctl or something else.
Someone care to test these workarounds with a Mac?
http://bugs.winehq.org/show_bug.cgi?id=17432
Josh M sykopomp@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sykopomp@gmail.com
--- Comment #3 from Josh M sykopomp@gmail.com 2009-09-01 16:45:22 --- I have a similar problem. I managed to get the game to connect to a Vista machine -once-, but for the most part, it's pretty consistently been failing to join. I didn't catch at the time whether there was anything particularly different in the approach, though.
One thing I noticed is that when trying to join a game over LAN using one of those lan emulators, the emulator keeps complaining about a TCP error and resetting.
All the usual suspects have been taken care of (version, weird patches, firewalls, router issues). This has happened on WC3 1.21 and 1.23, with both wine 1.0.1 and 1.1.27.
http://bugs.winehq.org/show_bug.cgi?id=17432
Mike Kaplinskiy mike.kaplinskiy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mike.kaplinskiy@gmail.com
--- Comment #4 from Mike Kaplinskiy mike.kaplinskiy@gmail.com 2009-09-01 20:42:32 --- bug 9787 deals with AcceptEx - a function that is used by WC3 to accept a connection. The reason you see those failed WSAIoctl's is because that is the way to call the function (it's considered an "extension" and you can't call it directly). This will prevent you from hosting games (ie that failed to connect error). This function does not do anything other than accept a new connection.
The failing broadcast is a different problem.
http://bugs.winehq.org/show_bug.cgi?id=17432
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |9787
http://bugs.winehq.org/show_bug.cgi?id=17432
Florian Klink flokli@flokli.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |flokli@flokli.de
--- Comment #5 from Florian Klink flokli@flokli.de 2010-10-01 11:37:21 CDT --- I can confirm that the commit cf72f406ec7cdfebbd5135ede6e45547ca82dae0 at least fixed hosting (and joining) wc3 games in a only-linux environment.
No crashes/splits occured when playing.
Really great work done by Mike!
http://bugs.winehq.org/show_bug.cgi?id=17432
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh@gmail.com
--- Comment #6 from Jerome Leclanche adys.wh@gmail.com 2010-10-01 12:15:58 CDT --- This can be closed as fixed then?
http://bugs.winehq.org/show_bug.cgi?id=17432
--- Comment #7 from Florian Klink flokli@flokli.de 2010-10-01 16:20:33 CDT --- I think there should be some more testing with win & mac systems to make sure it works with them in combination, too...
http://bugs.winehq.org/show_bug.cgi?id=17432
Bug 17432 depends on bug 9787, which changed state.
Bug 9787 Summary: Warcraft3 Battle.net Doesn't work (Needs AcceptEx) http://bugs.winehq.org/show_bug.cgi?id=9787
What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
http://bugs.winehq.org/show_bug.cgi?id=17432
Erich Hoover ehoover@mines.edu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ehoover@mines.edu
--- Comment #8 from Erich Hoover ehoover@mines.edu 2011-10-27 13:45:12 CDT --- Is this bug still valid? There's been a lot of networking work since anyone last commented here.
http://bugs.winehq.org/show_bug.cgi?id=17432
--- Comment #9 from Austin English austinenglish@gmail.com 2013-11-13 16:51:28 CST --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.6 or newer) wine? If so, please attach the terminal output in 1.7.6 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=17432
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |ABANDONED
--- Comment #10 from Austin English austinenglish@gmail.com --- Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=17432
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org