https://bugs.winehq.org/show_bug.cgi?id=35831
--- Comment #24 from Bruno Jesus 00cpxxx@gmail.com --- Created attachment 51132 --> https://bugs.winehq.org/attachment.cgi?id=51132 try to get the right IP for the interface
Please try the attached hack, it's meant to prove the theory that the problem is related to the interface IP. Get a +winsock with it, there must be a line like:
trace:winsock:WS_bind socket 01b4, ptr 0x2434c48 { family AF_INET, address 192.168.0.190, port 2300 }, length 16 trace:winsock:interface_bind Socket 01b4 bound to interface index 3 trace:winsock:WS_getsockname socket 01b4, ptr 0x2434c48, len 00000010 trace:winsock:WS_getsockname RESTORING ORIGINAL UDP BOUND SOCKET trace:winsock:WS_getsockname => { family AF_INET, address 192.168.0.190, port 2300 }
Not like:
trace:winsock:WS_bind socket 01b4, ptr 0x2434c48 { family AF_INET, address 192.168.0.190, port 2300 }, length 16 trace:winsock:interface_bind Socket 01b4 bound to interface index 3 trace:winsock:WS_getsockname socket 01b4, ptr 0x2434c48, len 00000010 trace:winsock:WS_getsockname => { family AF_INET, address 0.0.0.0, port 2300 }
Naturally the IP values will be different =)