I was mingling around with Linux Ubuntu where I had to do a VPN / VTUN connections to a certain host. So there was this problem where after I did all the settings in vtund.conf (the vtund config file) which was given to my by one of the support tech guys (I trust them..)
So now if I start the vtun connection manually, by typing this in the shell eg.
/home/user# vtund MYVPN1 192.168.100.1
This would create a task called vtund running after I ran ps -ef for the process list. A check with the ipconfig stats my connection up and connection were great.
Now the problem is…
I did a crontab job with /etc/init.d/vtun restart, or even /etc/init.d/vtun start, which I thought the vtun daemon would be able to start with init.d call, instead of running manually.
In the case of the manual vtund crashing or stopping for whatever reason, the /etc/init.d/vtun restart will help to “reset” the connection and help to re-connection, and keep the tunnel alive. But it didn’t work at all! For some reasons all efforts in starting the daemon with /etc/init.d/vtun
The solution…
After poking around (for 2 hours) and verifying alot of stuff, I’ll just list down my findings… By the way, I’m using vtun 3.0x, so do upgrade yours if its still 2.x. To check, run “man vtund”
The vtund uses these files:
/etc/vtund.conf - client vtund configurations
/etc/vtund-start.conf - Server vtund configurations (I wasn’t dealing with this)
/etc/default/vtun - The file to modify if you have this /etc/init.d/vtun problem
So after you tried your vtun connection manually, add those fields into the /etc/default/vtun, where your /etc/init.d/vtun viagra purchase will work! In this /etc/default/vtun file, theres only a few fields to fill in, where it simulates you running the manual task. Just fill in your tunnel name and host IP and it should work fine.





