Hi, everyone!

In order to create (keep) VPN tunnel to HQ office, only when it needs, I wrote this open source daemon (MIT Licensed):
https://github.com/root4root/tuninetd

tuninetd can be used in any situation, where we need to monitor network activity and react to it. Very simple solution, but quite powerful, because of opportunity to create your own "business logic" with external script.

I would like to hear some opinions about it! I should, probably, posted in "Networking" forum, but not sure is it appropriate there.

WOW, thank you so much! I was just circling back around to VPN technology in my learning queue.
I will check it out and spread the word.

Hi!
I read readme.md , I don't use VPN often, but tell me if I'm right. Let's say that I've got my home PC and I'm connecting to office. Your daemon will setup connection via internet if my PC want send some data? And then after some time of idle will disconnect?
And what if some packet want to go from office to me? For example someone want to access to my local share?

By the way, have you got some tips for accessing mdb file via internet (it is on Slackware server with Samba)? I was thinking about VPN.

sixerjman, thank you! =)

jareklakman,
Exactly right, but actual work to connect/disconnect performs via script, that tuninetd will execute. In fact, this daemon is simply event generator (like a crond, but very own way).

Usually, side that wants to exchange data must initialize VPN connection. So, you should deploy some kind of VPN server on your PC to do so. Anyway, you have to have public IP address, at least.
The short answer is: I don't think tuninetd might help you, it this case. The easiest way - keep connection permanent alive, which is opposite goal.

Yes, probably tunneling (VPN) is a most appropriate for described situation. =) I can't say more precisely, it depends...