vtundfix | ensure uptime of Virtual Tunnel
kandi X-RAY | vtundfix Summary
kandi X-RAY | vtundfix Summary
vtundfix is a Shell library. vtundfix has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.
Vtundfix is a service written in bash to keep Vtund up and running. Occasionally, the tunnel between Rutgers LCSR and CBIM would go down for an unknown reason and would require a manual restart. Vtundfix is a general solution which detects if any component of the tunnel (bridge/vlan/tap interfaces, processes) is not working, and fixes the problem that is detected. Vtundctl is a control script that merges the commands and init commands of Vtund and Vtundfix. Usage of Vtundctl can be found in subsection Using Vtundfix and Vtundctl.
Vtundfix is a service written in bash to keep Vtund up and running. Occasionally, the tunnel between Rutgers LCSR and CBIM would go down for an unknown reason and would require a manual restart. Vtundfix is a general solution which detects if any component of the tunnel (bridge/vlan/tap interfaces, processes) is not working, and fixes the problem that is detected. Vtundctl is a control script that merges the commands and init commands of Vtund and Vtundfix. Usage of Vtundctl can be found in subsection Using Vtundfix and Vtundctl.
Support
Quality
Security
License
Reuse
Support
vtundfix has a low active ecosystem.
It has 2 star(s) with 1 fork(s). There are 1 watchers for this library.
It had no major release in the last 6 months.
vtundfix has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of vtundfix is current.
Quality
vtundfix has no bugs reported.
Security
vtundfix has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
vtundfix is licensed under the MIT License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
vtundfix releases are not available. You will need to build from source code and install.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of vtundfix
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of vtundfix
vtundfix Key Features
No Key Features are available at this moment for vtundfix.
vtundfix Examples and Code Snippets
No Code Snippets are available at this moment for vtundfix.
Community Discussions
No Community Discussions are available at this moment for vtundfix.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install vtundfix
Vtundfix needs to be installed on both the Vtund server and client machines. Download or pull a copy of this repo and just run make. make install will put all of the files in the correct locations.
In order for Vtundfix to work, create the vtundfix user on each machine and set it up to SSH into the vtundfix user on the other machine without the password prompt. Do the following commands on both machines.
If a linux machine can't start any new processes because there are too many processes running, processes start to die randomly. If the parent process of Vtundfix is ever killed, the children die and there will be nothing to check and make sure that the Vtund tunnels are up and running. Vtundfix comes with a small script, /usr/local/vtundfix/vtundfix_cron, that restarts Vtundfix if it should be running. Although this step might seem optional, it is recommended for the longevity of the program. The cron script is by default already set up when you untar vtundfix.tgz and the script is set to run every 5 minutes. When you untar, you should restart the cron daemon. /etc/init.d/crond stop /etc/init.d/crond start. If you want to change how often the script runs or remove it, the crontab file is located in /usr/local/vtundfix/vtundfix_crontab and is linked from /etc/cron.d/vtundfix.
In order for Vtundfix to work, create the vtundfix user on each machine and set it up to SSH into the vtundfix user on the other machine without the password prompt. Do the following commands on both machines.
If a linux machine can't start any new processes because there are too many processes running, processes start to die randomly. If the parent process of Vtundfix is ever killed, the children die and there will be nothing to check and make sure that the Vtund tunnels are up and running. Vtundfix comes with a small script, /usr/local/vtundfix/vtundfix_cron, that restarts Vtundfix if it should be running. Although this step might seem optional, it is recommended for the longevity of the program. The cron script is by default already set up when you untar vtundfix.tgz and the script is set to run every 5 minutes. When you untar, you should restart the cron daemon. /etc/init.d/crond stop /etc/init.d/crond start. If you want to change how often the script runs or remove it, the crontab file is located in /usr/local/vtundfix/vtundfix_crontab and is linked from /etc/cron.d/vtundfix.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
