Axel: FYI, we were able to reproduce your bug (it was also triggered by a long one-way MIT network outage today). The issue comes down to a bad interaction where the client and server both think the other guy is trying to DOS them and start ignoring each other's packets. Working on a fix, but just wanted to let you know we figured this one out. Thanks again for the report.
Cheers, Keith On Mon, Dec 31, 2012 at 11:50 AM, Keith Winstein <kei...@mit.edu> wrote: > On Mon, 31 Dec 2012, Axel Beckert wrote: > >> Hi, >> >> On Mon, Dec 31, 2012 at 01:36:56AM -0500, Keith Winstein wrote: >>> On Mon, Dec 31, 2012 at 12:47 AM, Axel Beckert <a...@deuxchevaux.org> wrote: >>>> It looks like the data sent from the client is not (correctly) >>>> received on the server side. >>> >>> Do you think you could reproduce this? It would be wonderful to >>> capture what the server thinks is happening (i.e. the debugging output >>> of mosh-server new -v). >> >> I've now started two mosh sessions with --server="most-server new -v" >> to the host where already three confused mosh sessions are running in >> the hope that I can reporduce it there most likely. (I though can't >> promise anything.) > > It just goes to standard error, so you probably want something like > > mosh hostname --server='mosh-server new -v 2>/tmp/moshlog.txt' > > Thanks, hope it happens again! > > -Keith > _______________________________________________ > mosh-devel mailing list > mosh-devel@mit.edu > http://mailman.mit.edu/mailman/listinfo/mosh-devel _______________________________________________ mosh-devel mailing list mosh-devel@mit.edu http://mailman.mit.edu/mailman/listinfo/mosh-devel