<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
1. Use a UDP packet repeater.<br>
<br>
<a href="http://serverfault.com/questions/390916/mosh-tunnel-via-proxy" target="_blank">http://serverfault.com/questions/390916/mosh-tunnel-via-proxy</a><br>
suggests stone. I'm wondering whether socat or netcat could be<br>
used as well. But such a tool needs to be installed on the<br>
gateway. So, I'm suggesting a second solution:<br></blockquote><br>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. <br>
<br>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.<br>
</div><br>-- <br><div>Mark Lee Stillwell</div><a href="mailto:marklee@fortawesome.org" target="_blank">marklee@fortawesome.org</a>
</div></div>