On Wed, Aug 20, 2008 at 9:07 AM, SJr <[EMAIL PROTECTED]> wrote: > Hmmmmm I had been running PyMSNt for years with the same config on my > own box and the box at work. Both had been running with actually no > <host> flag at all but an <ip> flag which was 127.0.0.1. I was on > vacation and one day it broke, possibly the CVR0 issue, it was > basically the exact same time. But the fix didn't work. I don't see > why the program needs to know the IP address to use for that, the OS > should take care of that for it, and it worked fine for years prior to > this. > I don't know that this has been settled. But it did fix my issue >
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. -- - 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 -~----------~----~----~----~------~----~------~--~---
