On Wed, Jun 8, 2016 at 7:55 PM, john hood <cg...@glup.org> wrote: > Yeah, would you open a GitHub issue?
Will do. > > I tried my two Macs, and it breaks for me, but differently: they get > link-local IPv6 addresses from mDNS, requiring an interface identifier, > so mosh-client doesn't know where to send packets. > > I'm wondering how you're getting global IPv6 addresses from mDNS, even > though both your client and server are on the same local network. > Judging by the hostnames you're using and the IPv6 address, this is a > corporate OS X install on $yourverylargecompany's network. > > Yes, good guess. :-) I think it's relatively common to have a global v6 address allocated to a system which is RFC1918 in v4 these days. > If the server involved has regular DNS A/AAAA records, does that work > with Mosh? > I verified I see the same behavior moshing into systems with both global A/AAAA records, running an older version of mosh server (mosh 1.2.4a). So it seems it isn't dependent on mDNS, just an old server running on a dual stack server. I'll write up the bug. > > regards, > > --jh > > On 6/8/16 9:37 PM, John Hood wrote: > > Er, that's an interesting bug, it should work for either v4 or v6. I'll > > check mDNS tonight. > > > > regards, > > > > --jh > > > > On 06/08/2016 19:54, Bryce Bockman wrote: > >> I installed the OS X binary version (gotten from > >> < > https://github.com/mobile-shell/mosh/releases/download/mosh-1.2.5.95rc1/mosh-1.2.5.95rc1.pkg > > > https://github.com/mobile-shell/mosh/releases/download/mosh-1.2.5.95rc1/mosh-1.2.5.95rc1.pkg > ). > >> The install went fine, and I was able to mosh into an older server > >> running on stock Ubuntu 14.04. > >> > >> Found an interesting bug/feature, likely due to ipv6 related changes. > >> I often use mDNS name resolution. When moshing from the release > >> candidate to the older server mentioned above using mDNS target I get > >> the following: > >> > >> bb@bb-mac:~$ mosh beb-dev01.local > >> > >> mosh-server: Bad IP address (2606:b400:605:d0a0:dacb:8aff:fe69:7a71) > >> > >> Usage: mosh-server new [-s] [-v] [-i LOCALADDR] [-p PORT[:PORT2]] [-c > >> COLORS] [-l NAME=VALUE] [-- COMMAND...] > >> > >> Connection to beb-dev01.local closed. > >> > >> /usr/local/bin/mosh: Did not find mosh server startup message. > >> > >> bb@bb-mac:~$ > >> > >> > >> Note that mDNS resolves either v4 or v6 addresses: > >> > >> > >> bbockman@bbockman-mac:~$ ping6 beb-dev01.local > >> > >> PING6(56=40+8+8 bytes) 2606:b400:605:d0a0:16b1:c8ff:fe00:5da0 --> > >> 2606:b400:605:d0a0:dacb:8aff:fe69:7a71 > >> > >> 16 bytes from 2606:b400:605:d0a0:dacb:8aff:fe69:7a71, icmp_seq=0 > >> hlim=64 time=0.549 ms > >> > >> bbockman@bbockman-mac:~$ ping beb-dev01.local > >> > >> PING beb-dev01.local (10.145.137.58): 56 data bytes > >> > >> 64 bytes from 10.145.137.58 <http://10.145.137.58>: icmp_seq=0 ttl=64 > >> time=0.359 ms > >> > >> > >> If I explicitely mosh using the v4 address things work (mosh > >> 10.145.137.58). > >> > >> Not sure the extent of the behavior. e.g. Would the same behavior be > >> seen with an older server that has a AAAA record with newer client or > >> not. Should open an issue on github? > >> > >> > >> > >> On Wed, Jun 8, 2016 at 12:44 PM, Keith Winstein <kei...@mit.edu > >> <mailto:kei...@mit.edu>> wrote: > >> > >> Thanks all who have tested the mosh 1.2.6 release candidate so far. > >> > >> We're still looking for a postive ACK that somebody has > >> successfully tested the release candidate on: > >> > >> - Fedora > >> - OS X binary .pkg > >> ( > https://github.com/mobile-shell/mosh/releases/download/untagged-0d43a0f73825e9952677/mosh-1.2.5.95rc1.pkg > ) > >> - OS X compiling from source > >> > >> Thanks all, > >> Keith > >> > >> On Sun, Jun 5, 2016 at 8:39 PM, Richard Woodbury > >> <<mailto:rpwoo...@mybox.org>rpwoo...@mybox.org> wrote: > >> > >> I have confirmed that the RC builds and runs OK in Mosh for > >> Chrome. > >> > >> On Thu, Jun 2, 2016 at 11:47 PM Richard Woodbury > >> <<mailto:rpwoo...@mybox.org>rpwoo...@mybox.org> wrote: > >> > >> Hi, Keith. I don't have predictable time right now, but as > >> I can, I'll look into this for Mosh for Chrome. I did > >> manage to do a quick "smoke test" build, but I'm getting a > >> bunch of protobuf link errors. I'll need to do more > >> investigation, which may include bringing in a newer NaCl > >> SDK so I can also get newer libraries from naclports. > >> Hopefully I'll find time in the next day or two. > >> > >> I can add that it builds OK on the Raspberry Pi (ARM, > >> Raspbian), and the performance improvement makes a > >> /huge/ difference! mosh-server used to take most of the > >> CPU for busy output or large window size and was notably > >> sluggish, depending on local echo to be usable. Now the > >> CPU usage is in the noise, and it responds wonderfully. > >> > >> > >> On Mon, May 30, 2016 at 3:34 AM Keith Winstein > >> <<mailto:kei...@mit.edu>kei...@mit.edu> wrote: > >> > >> Hi folks, > >> > >> Could you please send in some positive testing reports > >> on the Mosh 1.2.6 release candidate? > >> > >> It would be great to have an independent "looks good" > >> from at least the following platforms before we cut > >> the release: > >> > >> - Fedora > >> - the OS X binary .pkg > >> - OS X compiling from source > >> - OpenBSD > >> - FreeBSD > >> - NetBSD > >> - Chrome > >> > >> Thanks, > >> Keith > >> > >> On Wed, May 25, 2016 at 8:56 PM, john hood > >> <<mailto:cg...@glup.org>cg...@glup.org> wrote: > >> > >> Hi all, > >> > >> We're happy to announce the upcoming release of > >> Mosh 1.2.6, and are > >> calling for testing on Mosh 1.2.5.95rc1. The > >> release has picked up > >> some minor new features in the year since the last > >> release such as > >> better IPv6 support and tools to handle orphaned > >> sessions. However, > >> it's also seen significant improvements in > >> performance, testing, and > >> portability. > >> > >> The Changelog for this release: > >> > >> * New features: > >> * Add Travis CI builds for Linux and Mac. > >> (Anders Kaseorg, others) > >> * Add a --local option to run without ssh. > >> (John Hood) > >> * Mosh now returns exitstatus reflecting > >> connection success. > >> (John Hood) > >> * Add a end-to-end test suite and many tests. > >> (John Hood) > >> * Implement timeouts and signals to help > >> address orphaned sessions. > >> (John Hood) > >> * Major rework of Mosh's display > >> differencing/rendering > >> code with much improved performance for slow > >> machines. (John Hood) > >> * Implement ANSI back/forward tab (CSI CBT, > >> CSI CHT). > >> (John Hood) > >> * Do not start user shell until network > >> session starts. > >> (John Hood) > >> * Add options for more flexible specification > >> of IPv4/IPv6 > >> hostname resolution. (John Hood) > >> * Improved bash completion. (Steve Dignam, > >> HIGUCHI Yuta) > >> * Add options for different methods of > >> resolving the remote host > >> address, allowing operation without > >> SshProxyCommand. (John Hood) > >> > >> * Platform support: > >> * Add configurable support for Apple Common > >> Crypto and > >> Nettle, in place of OpenSSL. Implement > >> base64 locally. > >> (John Hood) > >> * Workaround Cygwin select() bug. (John Hood) > >> * Updates to Debian packaging. (Anders > >> Kaseorg, Keith Winstein) > >> * Workaround a glibc-2.22 issue causing > >> segfaults on Debian Sid. > >> (John Hood with help from many others) > >> * Prefer c++ to g++, for systems like FreeBSD > >> where g++ is not usable. > >> (John Hood) > >> * Fixes for Illumos Hipster 20151003. (John > Hood) > >> * Disable -Werror for protobuf code, to > >> resolve a new gcc6 warning. > >> (John Hood) > >> * Link test for -fstack-protector-all on an > >> embedded platform. > >> (Baruch Siach) > >> * Resolve issue with bswap64() on > >> FreeBSD-CURRENT with libc++-3.8.0. > >> (John Hood) > >> * Fix issue with RECVTOS error message on > >> client on FreeBSD. > >> (John Hood) > >> > >> * Bug fixes: > >> * Remove an assertion causing aborts on > >> Unicode fallback found by > >> fuzzing with afl. (Keith Winstein) > >> * Fix a server hang with XON/XOFF on BSD > >> systems. (John Hood) > >> * Fix a typeahead-prediction bug that caused > >> display corruption on > >> urxvt. (John Hood) > >> > >> Source code is available as > >> << > https://github.com/mobile-shell/mosh/releases/download/untagged-0d43a0f73825e9952677/mosh-1.2.5.95rc1.tar.gz > > > https://github.com/mobile-shell/mosh/releases/download/untagged-0d43a0f73825e9952677/mosh-1.2.5.95rc1.tar.gz > >. > >> The SHA256 sum for this file is > >> > a2697c41cfc8c92dc7a743dd101849a7a508c6986b24d6f44711d8533d18fcf5 > >> > >> One standalone OS X package is available: > >> > >> * > >> << > https://github.com/mobile-shell/mosh/releases/download/untagged-0d43a0f73825e9952677/mosh-1.2.5.95rc1.pkg > > > https://github.com/mobile-shell/mosh/releases/download/untagged-0d43a0f73825e9952677/mosh-1.2.5.95rc1.pkg > > > >> is an i386/x86_64 build for OS X 10.9 and higher. > >> The SHA256 sum for > >> this file is > >> > 48a56d83d0ef655d38e0ea596fd9cac98c0dc433cb5356205d26748350d47e6c > >> > >> (If you are using a package system such as > >> MacPorts or Homebrew, I > >> recommend using that, though.) > >> > >> As always, Ubuntu PPA builds of the latest source > >> are available at > >> ppa:keithw/mosh. > >> > >> Packagers, please note that Mosh has some minor > >> dependency changes: Perl > >> is now required to be >= 5.14, but IO::Socket > >> modules are no longer > >> required. If anybody needs to package for older > >> versions of Perl, talk > >> to me and I'll probably bring something into the > >> release. Also, if > >> anyone needs an OS X package for 10.8 or lower, > >> please contact me. > >> > >> Your testing is very unlikely to prove Mosh to be > >> free of bugs, but your > >> testing will help us make 1.2.6 a better release. > >> Please report any > >> issues you find on Github, and we can be found on > >> IRC at > >> <irc://irc.freenode.net/mosh > >> <http://irc.freenode.net/mosh>>. > >> > >> Looking ahead, we expect Mosh 1.3 to be a feature > >> release, bringing > >> significant new functionality. SSH agent > >> forwarding is high on the list. > >> > >> The Mosh team thanks you for your help. > >> > >> --John Hood > >> > >> > >> _______________________________________________ > >> > >> mosh-devel mailing list > >> mosh-devel@mit.edu <mailto:mosh-devel@mit.edu> > >> http://mailman.mit.edu/mailman/listinfo/mosh-devel > >> > >> > >> > >> > >> _______________________________________________ > >> mosh-devel mailing list > >> mosh-devel@mit.edu <mailto: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 > > > >
_______________________________________________ mosh-devel mailing list mosh-devel@mit.edu http://mailman.mit.edu/mailman/listinfo/mosh-devel
