Opened at 2009-12-12T16:09:44Z

Closed at 2013-05-27T17:31:33Z

Last modified at 2013-05-27T17:36:05Z

#854 closed defect (duplicate)

what to do when you can't find any IP address for yourself

Reported by: zooko Owned by:
Priority: major Milestone: undecided
Component: code-network Version: 1.5.0
Keywords: usability iputil transparency Cc:
Launchpad Bug:

Description (last modified by zooko)

In #853 a user on Windows had changed their PATH so that there was no route.exe. This causes Tahoe-LAFS 1.5.0-r1408 to emit an unhelpful error message and call os.abort(). I've written a unit test to simulate this condition, but now I'm not sure what Tahoe-LAFS ought to do in this case:

  1. Emit a help error message like "Hey you have no IP address" and then os.abort()
  2. Go ahead and start up. You don't necessarily need an IP address to operate as a Tahoe-LAFS client or server!

Change History (5)

comment:1 Changed at 2009-12-13T04:09:04Z by davidsarah

  • Keywords usability added

comment:2 Changed at 2009-12-20T20:43:34Z by davidsarah

Emit a helpful warning and then start up?

comment:3 Changed at 2011-05-29T15:36:22Z by davidsarah

#1381 would touch the same code, so it would probably be a good idea to fix this at the same time, if we can agree on what to do.

Last edited at 2011-05-29T15:36:31Z by davidsarah (previous) (diff)

comment:4 Changed at 2013-05-27T17:31:33Z by zooko

  • Description modified (diff)
  • Resolution set to duplicate
  • Status changed from new to closed

Superceded by #1988.

comment:5 Changed at 2013-05-27T17:36:05Z by zooko

  • Keywords iputil transparency added
Note: See TracTickets for help on using tickets.