http://bugs.winehq.org/show_bug.cgi?id=33008
--- Comment #3 from decimusmaximus@seznam.cz 2013-02-19 13:07:30 CST --- Sorry for bad "Importance" value, I thought that this bug is critical, because all applications using specific IP (interface) binding will not work. In my case I had to downgrade to Wine 1.5.6 (version available from openSuse 12.2 repository)
You said that Wine 1.5.6 does not have implementation for specific IP binding, but it works correctly there. It does not work in Wine 1.5.24
There is nothing in console, no error (fixme etc) message.
As I have mentioned above, I can just check it via "netstat --listening":
Tested again on another system (openSuse), there is NAT (masquerade) from B to A, simple test application created. Interface A, IP 10.0.0.1 Interface B, IP 192.168.0.1 TestApp: Binding (UDP) is set to 10.0.0.1:999
netstat shows: Wine 1.5.6: 10.0.0.1:999 Wine 1.5.24: 0.0.0.0:999
It could look that it is not problem, but it is critical issue on systems with NAT. Wine 1.5.24 problem: although it is saying 0.0.0.0, app does not receive any data from 192.168.0.1 interface (somehow internally blocked in Wine?). From app point of view it looks ok, data are received only from 10.0.0.x, but system can see that it is listening on all addresses (0.0.0.0) and traffic from 192.168.0.x with target 10.0.0.1 is not NATed, but directly sent to 0.0.0.0:999 - however data from 192.168.0.x are blocked. So clients in 192.168.0.x network are not able to connect to app.