On Tuesday 08 September 2009 08:40:39 pm Zooko O'Whielacronx wrote: > On Tue, Sep 8, 2009 at 6:27 AM, Shawn Willden<[email protected]> wrote: > > Any idea what the problem might be? What can I do to get more visibility > > into what connections Tahoe is attempting to make (and failing)? > > I'll try to address your second question. :-) Wireshark is an > excellent tool, and not too hard to learn to use (if you aren't > already familiar with it).
I am very familiar with it. I was hoping for something a little higher-level, but I can use tcpdump to build a packet log on one of the machines that's failing to connect, download it to my machine and then use wireshark to analyze it. > I think wireshark might > also be able to do a MITM attack on your SSL connections for you (if > you provide it with the private key), but I'm not sure, and in any > case that would be overkill for this purpose. Yeah, it can, and I've done that. > http://allmydata.org/trac/tahoe/browser/docs/logging.txt Not sure how I missed that when I looked through the docs today. Thanks. > Oh, and I guess the very first thing to do would be to look in your > incidents directory and examine any incident files you find therein. > They are (as far as I know) clean of secrets so you can attach them to > a ticket and ask others to look at them too. There are no incidents. I looked there first thing. Thanks, Shawn. _______________________________________________ tahoe-dev mailing list [email protected] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
