Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!goblin2!goblin.stu.neva.ru!newsfeed1.swip.net!uio.no!nntp.uib.no!svn.schaathun.net!not-for-mail From: Hans Georg Schaathun Newsgroups: comp.lang.python Subject: Re: sockets: bind to external interface Date: Mon, 25 Apr 2011 21:14:51 +0100 Organization: University of Bergen Lines: 17 Message-ID: References: NNTP-Posting-Host: vannskorpion.bccs.uib.no X-Trace: toralf.uib.no 1303762354 76229 129.177.20.20 (25 Apr 2011 20:12:34 GMT) X-Complaints-To: abuse@uib.no NNTP-Posting-Date: 25 Apr 2011 20:12:34 GMT User-Agent: slrn/pre1.0.0-18 (Linux) Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:3993 On Tue, 26 Apr 2011 05:49:07 +1000, Chris Angelico wrote: : You can run 'ifconfig' without being root, so there must be a way. At : very worst, parse ifconfig's output. Of course, but I am not sure that's simpler than the manual solution. Especially since there is more than one version of ifconfig ... : 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 ... -- :-- Hans Georg