On Thu, 19 Dec 2013, Tim Watts wrote:
> With respect to the suggestion of "proxy all network connections to the
> server" - I'm not sure if I fully understand this.
>
> Not having actually worked with containers is probably limiting my
> understanding, so I must apologise if the following seems st
On 18/12/13 18:52, Keith Winstein wrote:
> Thanks, Tim. Our tentative thoughts on this are to create "slosh" as a
> separate program that will fork a lightweight Linux container (with
> unshare()) in a new network namespace with a TUN device, and gracefully
> proxy all the network connections initi
Thanks, Tim. Our tentative thoughts on this are to create "slosh" as a
separate program that will fork a lightweight Linux container (with
unshare()) in a new network namespace with a TUN device, and gracefully
proxy all the network connections initiated from within the container to
the server, doi
Hi,
Firstly I would like to say I love mosh. It really solves the problem of
working with a laptop on the train tethered via 3G where the connection
is up and down like a yoyo and my client IP changes randomly.
I would like to offer 2 "wishlist" items to the Mosh 2013 Ideas List:
https://docs.
