On Wed, Aug 20, 2008 at 11:16 AM, Norman Rasmussen <[EMAIL PROTECTED]>wrote:
> I'm not entirely sure what the logic behind the change was, but I'm better > it was because in an environment where you want to run multiple instance of > the transport on a machine with many ip addresses, you'd want to give each > transport it's own outgoing IP address (to remove any problems over too many > connections per IP address). > > The default value for host should be 0.0.0.0 (and not 127.0.0.1), that way > it'll bind to whatever outgoing address the OS wants to assign > Hrmm, after more investigation host is used for two things: - bind address for outgoing connections, - announced address for file transfers (jabber socks5 connections) So if you're running behind NAT, then you basically _have_ to use a dns name for the host value, because if you put in a public natted address, then outgoing connections won't work, and if you put in a private IP, then file transfers will only work for clients on the same network (which might be desired I guess). -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "py-transports" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/py-transports?hl=en -~----------~----~----~----~------~----~------~--~---
