http://bugs.winehq.org/show_bug.cgi?id=33008
--- Comment #16 from Erich Hoover erich.e.hoover@gmail.com --- (In reply to facoptere from comment #15)
(copied from https://github.com/mirrors/wine/issues/8 )
I just updated my Debian and compiled latest wine version. What I can reproduce with Wine version 1.7.16-91-ged51082 : 1/ on Linux 3.13-1, an UDP server does not bind the IP address specified, but binds 0.0.0.0. 2/ on the same machine, but if the IP address is a virtual one (eth0:1 for example), Wine works properly and binds the IP address specified. 3/ there is no issue whatsoever with Linux kernel 2.6.32-5 for example.
Hi facoptere, this is intentional behavior to allow broadcast packets on sockets that are "bound" to a specific interface (broadcast packets only work when binding to 0.0.0.0). The new code will set a kernel option (not available on old kernels) that sets the packet to go out through the interface associated with the specified address. There's also a packet filter to only accept packets that come in through (or are destined for) the provided address. Could you give more detail on the specific problem you are running into?