http://www.ntop.org/n2n/ n2n is a layer-two peer-to-peer virtual private network (VPN) which allows users to exploit features typical of P2P applications at network instead of application level. This means that users can gain native IP visibility (e.g. two PCs belonging to the same n2n network can ping each other) and be reachable with the same network IP address regardless of the network where they currently belong. In a nutshell, as OpenVPN moved SSL from application (e.g. used to implement the https protocol) to network protocol, n2n moves P2P from application to network level. Reproducible: Always
Created attachment 183893 [details] n2n-9999.ebuild
Reassigning to maintainer-wanted.
I have init script and config file template written. Reply if you're intersted.
can't hurt have them here, can it? please attach. thanks
Created attachment 220151 [details] /etc/init.d/n2n
Created attachment 220153 [details] /etc/conf.d/n2n.example Example configuration file. Real config file name shoud match pattern n2n.*, so, for example, config file n2n.foo will be used when calling /etc/init.d/n2n.foo.
Comment on attachment 220151 [details] /etc/init.d/n2n Do not use directly. Create symlink to it for each particular configuration (n2n tun interface), for example: /etc/init.d/n2n.mynetwork.
Comment on attachment 220151 [details] /etc/init.d/n2n This is the "edge" script. Supernode script, I think, will be very similar.
hi the ebuild did not worked for me it seems, that the svn repository has slightly different structure here is the patch for the ebuild --- n2n-9999.ebuild.orig 2010-08-25 10:07:03.000000000 +0200 +++ n2n-9999.ebuild 2010-08-25 10:05:12.000000000 +0200 @@ -4,7 +4,7 @@ inherit subversion -ESVN_REPO_URI="https://svn.ntop.org/svn/ntop/trunk/n2n" +ESVN_REPO_URI="https://svn.ntop.org/svn/ntop/trunk/n2n/n2n_v2" ESVN_PROJECT="n2n" DESCRIPTION="A layer-two peer-to-peer virtual private network (VPN)"
