Opened at 2013-03-20T21:21:56Z
Last modified at 2015-03-27T10:47:44Z
#1935 new defect
bad behavior when localhost is down — at Initial Version
| Reported by: | warner | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | undecided |
| Component: | code-network | Version: | 1.9.2 |
| Keywords: | loopback localhost network error unix iputil transparency | Cc: | |
| Launchpad Bug: |
Description
User "amospalla" on IRC had problems setting up an introducer and a node on the same box (they reported that the node started, and the web ui was visible, but it could not connect to the introducer). The problem turned out to be that their loopback interface (lo, usually bound to 127.0.0.1) was disabled or unconfigured, leaving only en0 (which had some 192-net private address). The node created a furl with functional connection hints (I think telnetting to the 192-net address worked). But the node never reported connecting to the introducer. They were using "debian 7.0".
We don't know exactly what happened, but it sounds like something might accidentally depend upon having 127.0.0.1 be functional. I'd like to reproduce this on my linux box by doing "ifconfig lo down" and see what happens.
