Bug 213712

Summary:	net/mosh: Can't connect since FreeBSD 11
Product:	Ports & Packages	Reporter:	Ari Sovijärvi <listat2018>
Component:	Individual Port(s)	Assignee:	Ryan Steinmetz <zi>
Status:	Closed FIXED
Severity:	Affects Some People	Keywords:	needs-qa
Priority:	---	Flags:	bugzilla: maintainer-feedback? (zi)
Version:	Latest
Hardware:	Any
OS:	Any

Description Ari Sovijärvi 2016-10-22 22:06:12 UTC

Since upgrading to FreeBSD 11 from 10.3 mosh has trouble connecting to the server. Curiously it does work pretty reliably when the server has SMP, virtualized or not, but UP systems just give the error:

/usr/bin/mosh: Did not find mosh server startup message.

It seems I'm hitting a problem discussed here:
https://lists.freebsd.org/pipermail/freebsd-current/2016-August/062987.html

The thread has a mention of a patch for UP systems, but it's not clear if the patch has been added to ports.

I've tried both; building the version from latest ports and the pre-compiled version available with pkgng.

The FreeBSD version I'm using is:
FreeBSD basestar4 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu Sep 29 01:43:23 UTC 2016     root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

and it's virtualized with KVM. Mosh server appears to start when run from shell over ssh, but it can't seem to handle starting it itself.

Comment 1 Ryan Steinmetz freebsd_committer

2016-10-23 03:55:53 UTC

I've applied a patch from the mosh developers.  Can you confirm this has resolved your issue?

Comment 2 Ari Sovijärvi 2016-10-23 16:19:05 UTC

(In reply to Ryan Steinmetz from comment #1)

After recompiling with the patch in 1.2.6_1, it now seems to work reliably in UP systems as well, at least for me. 10 out 10 test connects connected, before this 1 out of 20-30 connected.