Package: pyro Version: 1:3.14-1.1 Severity: important Dear Maintainer,
a standard Debian installation has an entry with 127.0.0.1 for hostname in /etc/hosts. When pyro nameserver daemon starts, it resolves hostname, gets 127.0.0.1 and binds to the loopback interface. The troubleshooting section of pyro documentation says: "Probable cause: incorrect DNS config, or the server's host name resolves to 127.0.0.1, for instance because the hosts file contains an invalid entry. only "localhost" is allowed resolve to 127.0.0.1 ! " http://irmen.home.xs4all.nl/pyro3/troubleshooting.html#connection_problems_involving_localhost.2BAC8-127.0.0.1 But this is wrong. It is not a misconfiguration when hostname resolves to 127.0.0.1 on local machine. This is standard Debian behaviour! Instead the pyro nameserver should bind to ALL interfaces that have a broadcast address. You can determine them with netifaces module. Also socket has the ability to bind to all interfaces with an empty host string. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pyro depends on: ii python 2.7.3~rc2-1 ii python-support 1.0.15 pyro recommends no packages. Versions of packages pyro suggests: pn pyro-doc <none> pn pyro-gui <none> -- no debconf information _______________________________________________ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
