Hi!
Man, I love this tool! Never heard about it, but when I started researching my new little project, it immediately surfarced! Really really cool!
What I'm setting up is a Raspberry Pi 3 as WLAN Access Point, where all clients that want to appear as coming from the remote IP-adress only needs to connect to that special AP.
However I wonder what is the recommended setup for a "permanent VPN" that comes up when this Raspi VPN AP boots. I guess it needs to be started as a service (init.d?). Or maybe from cron, refer to my next point about reconnects? Also the ssh-keys must be open, and specified. I also guess we should start ssh with "keep-alive" packets, to avoid any stateful element along my way to tear down the TCP connection.
Is there a recommended way for such a permanent setup, or a recommended guide?
But the important point is this: Can sshuttle itself do reconnect if it determines that the SSH connection has gone down? Or are there some other smart way to accomplish this? I was thinking about making a watchdog-thing that send a request once per minute, and if that didn't go through for e.g. 5 minutes, restarted the sshuttle.
But such a setup always requires lots of tweaking to get right, I feel. One must watch out for starting hundreds of instances, thus kill any existing upon restart, do some sane logging to enable debugging etc etc. So if this could be handled by the tool itself, that would be kick ass
Ideas?
Thanks a bunch for this tool, and for any replies! ;-)
Endre.