Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!newsfeed.kamp.net!newsfeed.kamp.net!newsfeed.straub-nv.de!noris.net!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: Thomas Rachel Newsgroups: comp.lang.python Subject: Re: sockets: bind to external interface Date: Mon, 25 Apr 2011 23:14:22 +0200 Organization: A newly installed InterNetNews server Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.14) Gecko/20110221 SUSE/3.1.8 Thunderbird/3.1.8 In-Reply-To: Lines: 17 NNTP-Posting-Date: 25 Apr 2011 23:20:04 CEST NNTP-Posting-Host: 1f9535e7.newsspool2.arcor-online.net X-Trace: DXC=k6TdSbl;4U=^cW`WBF>WQ4@9e2K8FCa6^2FW2OLF_]FfFg8?ijeV\Q:ZI78 X-Complaints-To: usenet-abuse@arcor.de Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:3998 Am 25.04.2011 22:14 schrieb Hans Georg Schaathun: > On Tue, 26 Apr 2011 05:49:07 +1000, Chris Angelico > wrote: > : The way you talk of "the" external interface, I'm assuming this > : computer has only one. Is there a reason for not simply binding to > : INADDR_ANY aka 0.0.0.0? > > Ah. That's what I really wanted. Thanks a lot. I wonder why that > was not mentioned in the tutorial I used ... Generally, it seems better to use '' instead of '0.0.0.0' in this case in order to stay compatible with other address families, especially INET6. Thomas