[tahoe-lafs-trac-stream] [tahoe-lafs] #1935: bad behavior when localhost is down

[tahoe-lafs]

#1935: bad behavior when localhost is down
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  code-    |    Version:  1.9.2
  network                |   Keywords:  loopback localhost network error
   Resolution:           |  unix
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Old 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.

New 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.

--

Comment (by zooko):

 See #1988.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1935#comment:2>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage