That&#x27;s cool. Another way is to localtunnel to TCP forward to endhost in your config (ie two SSH connections, the first to the jump host, the second through the jump host, without agent forwarding), but that gets tedious fast without scripting support, especially if you want to use different portnums to avoid conflicts. ControlMaster would be a good choice to multiplex multiple connections to the same box.<p>&gt; I believe that your solution requires things to be on different subnets to isolate them, with separate jump hosts for each subnet, correct? Here, I only need one sshmux for everyone.<p>Right, we&#x27;re automating the .ssh&#x2F;authorized_keys (and sudoers) right now (<a href="https:&#x2F;&#x2F;github.com&#x2F;userify&#x2F;shim&#x2F;blob&#x2F;master&#x2F;shim.py" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;userify&#x2F;shim&#x2F;blob&#x2F;master&#x2F;shim.py</a>), so you can set it up however you like, as long as those boxes can get to either Userify for key updates, or your on-premises Userify server(s). Only one jumpbox is needed across any network, depending on how you prefer to lockdown your network. (The HOWTO refers to EC2, but it can be built anywhere, exactly the same way.)<p>sshmux looks like an interesting project, and love the simplicity. Wonder if Userify might automate the ProxyCommand setup! Seems really useful.<p>&gt; Good luck with Userify!<p>Thanks! We have 350 companies on the platform right now and growing fast, and Userify Enterprise (on-premise) is in beta at several large enterprises as well.<p>BTW, joushou, we&#x27;re looking for brilliant SSH and golang hackers.. ping me if you get bored :)