[mosh-devel] Mosh for PC to remote raspberry Pi

[Keith Winstein]

Hello Kris,

Could you point me to the instructions you're following?

The typical use of Mosh just involves typing "mosh <name-of-server>" on the
client, or typing the name of server into the Mosh Chrome app. It doesn't
involve running anything on the server (other than installing mosh in the
first place).

For debugging purposes, it is possible to run the "mosh-server" and
"mosh-client" programs separately (as described on http://mosh.mit.edu),
but in normal use you would just run "mosh," or the Chrome app, on the
client, and it takes care of starting the server. (Just like with SSH, how
you might run "ssh server" on the client.)

If you do want to run mosh-server separately, the command is "mosh-server"
with a dash in the middle.

-Keith

On Thu, Sep 3, 2015 at 8:04 PM, Kris Mclean <kris at mcleanautomation.com.au>
wrote:

> We normally SSH from a PC (using the Chrome browser SecureShell app) into
> a Rpi via wifi on a home network. Recently we got the Pi working on a 3G
> dongle & noticed that SSH to the Pi (now outside the home network) no
> longer worked.
>
> We installed mosh for chrome on the PC & mosh for Debian on the PI. The
> instructions said to run mosh server on the Pi to get a key, IP etc for the
> form the Chrome mosh wants filled in. But mosh server on the Pi responds
> with;
> /usr/bin/mosh: Could not resolve hostname server
> ssh_exchange_indentification: Connection closed by remote host
> /usr/bin/mosh: Did not find remote IP address (is SSH ProxyCommand
> disabled?)
>
> The Pi definitely has a connection;
>
> ppp0      Link encap:Point-to-Point Protocol
>          inet addr:10.178.192.20  P-t-P:10.64.64.64  Mask:255.255.255.255
>          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>          RX packets:574 errors:78 dropped:0 overruns:0 frame:0
>          TX packets:552 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:3
>          RX bytes:128723 (125.7 KiB)  TX bytes:277499 (270.9 KiB)
> and ping google.com works. So just wondering what we could try next?
> Rgds. Kris Mc(mcleanautomation.com.au)
>
> _______________________________________________
> mosh-devel mailing list
> mosh-devel at mit.edu
> http://mailman.mit.edu/mailman/listinfo/mosh-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/mosh-devel/attachments/20150903/6b1b1c06/attachment.html