Right, I'm attaching a script I was working on when I was looking at this a few weeks ago. Fair warning, it might not be in 100% working condition right now.
On Fri, Mar 28, 2014 at 3:08 PM, David Seaward <dseaward...@gmail.com>wrote: > Ah, this is more complicated than I thought :D > > I thought it was going to be one of: > > a) mosh-client - ssh - ssh - mosh-server > > ...where "ssh - ssh" may be some kind of transparent hop, or > > b) mosh-client - mosh-? - mosh-? - mosh-server > > ...with funky configuration on the hops. > > > On Fri, Mar 28, 2014 at 5:04 PM, Mark Stillwell <mark...@fortawesome.org> > wrote: > > > >> 1. Use a UDP packet repeater. > >> > >> http://serverfault.com/questions/390916/mosh-tunnel-via-proxy > >> suggests stone. I'm wondering whether socat or netcat could be > >> used as well. But such a tool needs to be installed on the > >> gateway. So, I'm suggesting a second solution: > > > > > > I've tried this with both socat and stone, using one of these tools to go > > from udp to tcp, then forwarding the tcp connection with ssh, then > > translating back from tcp to udp on the other side of the connection. It > > works great for 10-15 seconds, then mosh invariably freezes up and > starts to > > complain about tampering. > > > > Based on debug output from stone, I think that mosh tries to send some > udp > > packets that are too big to fit into a single tcp packet within the ssh > > tunnel, and somehow when ssh puts everything back together on the other > end > > it must not do it perfectly, triggering mosh's alarm bells. > > > > -- > > Mark Lee Stillwell > > mark...@fortawesome.org > > > > _______________________________________________ > > mosh-users mailing list > > mosh-users@mit.edu > > http://mailman.mit.edu/mailman/listinfo/mosh-users > > > -- Mark Lee Stillwell mark...@fortawesome.org
cfmosh2.sh
Description: Bourne shell script
_______________________________________________ mosh-users mailing list mosh-users@mit.edu http://mailman.mit.edu/mailman/listinfo/mosh-users
