[Bug 13474] Network sockets: Unable to create two server sockets in the same wine session

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=13474





--- Comment #8 from yiourkas <yiourkas at gmail.com>  2008-05-28 04:55:55 ---
another note:
Ok, concerning winsock, **I think** this is an issue.

Concerning warcraft, and to whoever wants to play in battle.net and see ALL the
player's messages:

a) You cannot be the host of the game. Warcraft creates a server socket on port
6112 (used by war3) when creating the game (there is a procedure to register
the game to battle.net's servers). Then closes the ssocket and attempts to
create another one for the players to connect.

b) Firewall port 6112, for example remove NAT on your router and you will be
able to see other player's messages.

What I 've figured about battle.net is that, except from the host of the game,
everyone else having port 6112 exposed can act as a backup host. Again, what I
think happens is that every backup host tries to open a server socket and
connect with all other players (this looks like a fully connected graph of up
to 12 nodes if all nodes have port 6112 exposed). If you explicitly deny being
a backup host (by firewalling port 6112), warcraft uses only one client socket
to connect to the main game host.


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.