Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Tree [r4] /
History



File Date Author Commit
certfiles 2010-07-26 shre86 [r1] First check-in of simple-vpn code to sourceforg...
certgen 2010-08-04 shre86 [r4] Updated license in all the code files.
common 2010-07-26 shre86 [r1] First check-in of simple-vpn code to sourceforg...
confgen 2010-08-04 shre86 [r4] Updated license in all the code files.
License.txt 2010-07-26 shre86 [r3] Updated license.
Makefile 2010-07-26 shre86 [r1] First check-in of simple-vpn code to sourceforg...
README 2010-07-26 shre86 [r2] Updated with link to tech-report
sample.vpnconf 2010-07-26 shre86 [r1] First check-in of simple-vpn code to sourceforg...
test.vpnconf 2010-07-26 shre86 [r1] First check-in of simple-vpn code to sourceforg...

Read Me

Author: Shreyas Srivatsan

For complete details of the project please take a look at
https://mice.cs.columbia.edu/getTechreport.php?techreportID=1433

Usage:
To generate conf files run make FILE=<simple-vpn conf fname>
Sample: make FILE=test.vpnconf

make build - Builds the SIMPLE-VPN configuration generator.
make conf FILE=<simple-vpn conf name> - Runs the simple-vpn configuration generation.
make cert - Generates the certificates used by the configuration generation if 
    the authentication token generation option is specified.
make clean - Removes the current vpn configuration files.
make distclean - Removes all configuration files, certificates and all binaries 
    generated during VPN conf file generation creation.

Directions:
A sample configuration file 'sample.vpnconf'is present that explains the grammar. 
A detailed description of the grammar and the SIMPLE-VPN process is present in the 
SIMPLE-VPN manual and paper.

SIMPLE-VPN generates a file topology.png that displays the topology of the 
configuration generated to help understand the correctness of the configration. 
The double circle corresponds to gateway nodes and the ovals correspond to 
nodes/subnets.

SIMPLE-VPN generates the respective configuration files and certificates in the 
following directory structure. 

configuration_files* -> vpn_name -> node_name -> conf files, certificates etc.
configuration_files* -> install-script.sh

The install-script.sh can be used to install the certificates and conf files
in the appropriate locations on the destination systems. It 
assumes that you have root priveleges at the target node.
It expects a root key that is authorized for easy copying of the configuration 
files. If not it will prompt for a root password while copying the conf
files and certificates to each system.