Florent Xicluna <florent.xicl...@gmail.com> added the comment: Something like 127.42.42.42 might be more reliable, because it does not depend on the LAN configuration, only on the local loopback settings. It is in 127.0.0.0/8 but not in 127.0.0.0/32. Tested OK here.
127.0.0.0/8 - This block is assigned for use as the Internet host loopback address. A datagram sent by a higher-level protocol to an address anywhere within this block loops back inside the host. This is ordinarily implemented using only 127.0.0.1/32 for loopback. As described in [RFC1122], Section 3.2.1.3, addresses within the entire 127.0.0.0/8 block do not legitimately appear on any network anywhere. http://tools.ietf.org/html/rfc5735#section-3 ---------- title: test_timeout failure when system on IPv4 10.0.x.x subnet -> test_timeout failure when system on IPv4 10.x.x.x subnet _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15285> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com