Great!

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Christian Biere
Sent: Sunday, April 16, 2006 7:37 PM
To: [EMAIL PROTECTED]
Subject: Re: [Gtk-gnutella-users]Re: Running gtk-gnutella as daemon

Raphael Manfredi wrote:
> Quoting Christian Biere <[EMAIL PROTECTED]> from
> ml.softs.gtk-gnutella.users:
> > No, gtk-gnutella always binds the listening sockets to the
> > unspecified address no matter whether you configure or force a
> > certain IP address.
 
> OK.  So when the IP is forced, we could bind it explicitly.
 
> However, I realized shortly after sending the message that it would
> not work when the IP address you specify is NAT'ed, because the
> local IP is going to be different.
 
> So I guess we need another option for multi-homed machines,
> specifying on which addresses to listen.

I have added an boolean option "bind_to_forced_local_ip" in current
SVN. The listening sockets only use the forced address for bind() if
this option is set too. So behind a NAT you typically would not want
to set this as bind() would always fail with the forced address.  If
the forced address is assigned to a real network interface on the
local machine, you can set this option and it will allow you to run
multiple instances of  Gtk-Gnutella (or whatever else) on the same
port but a different interface (with a different IP address).

Follow-up to gtkg-devel if any.

-- 
Christian



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Gtk-gnutella-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel

Reply via email to