On Mon, Apr 14, 2008 at 11:04:52PM +0200, Kai Blin wrote:
Binding to a specific address is the only easy way of detecting
which interface an UDP packet was received on since recvfrom() only
gives source address, not destination. Listening on 0.0.0.0 would
make impossible to tell which
On Mon, 14 Apr 2008, Kai Blin wrote:
On Monday 14 April 2008 18:42:26 Paul Chitescu wrote:
Binding to a specific address is the only easy way of detecting which
interface an UDP packet was received on since recvfrom() only gives source
address, not destination. Listening on 0.0.0.0 would make
Hi,
nitpick:
+/* Trying to bind to the default hots interface,
using
Typo in word 'host'?
--
Kirill
On Mon, Apr 14, 2008 at 04:05:23PM +0200, Kai Blin wrote:
Hi Kai, et all,
+static const char magic_loopback_addr[] = {127, 12, 34, 56};
in the past wine used to work quite well with the ip-address configured
using the places in the windows registry (msdn or something similar kept
an howto for
On Mon, 14 Apr 2008, Christoph Frick wrote:
On Mon, Apr 14, 2008 at 04:05:23PM +0200, Kai Blin wrote:
Hi Kai, et all,
+static const char magic_loopback_addr[] = {127, 12, 34, 56};
in the past wine used to work quite well with the ip-address configured
using the places in the windows
On Monday 14 April 2008 18:30:40 Kirill K. Smirnov wrote:
Hi,
nitpick:
+/* Trying to bind to the default hots interface,
Thanks for the catch, revised patch sent.
Cheers,
Kai
--
Kai Blin
WorldForge developer http://www.worldforge.org/
Wine developer
On Monday 14 April 2008 18:42:26 Paul Chitescu wrote:
Binding to a specific address is the only easy way of detecting which
interface an UDP packet was received on since recvfrom() only gives source
address, not destination. Listening on 0.0.0.0 would make impossible to
tell which interface a
