Source: n3n
Section: net
Priority: optional
Maintainer: Hamish Coleman <hamish@zot.org>
Standards-Version: 4.6.0
Build-Depends:
 autoconf,
 debhelper,
 debhelper-compat (= 10),
 devscripts,
 dh-python,
 flake8,
 gcovr,
 jq,
 libcap-dev,
 libzstd-dev,
 python3,
 shellcheck,
 uncrustify,
 yamllint,

Package: n3n
Architecture: any
Depends:
 ${misc:Depends},
 ${python3:Depends},
 ${shlibs:Depends},
Conflicts: n2n
Description: Peer-to-Peer and Layer-2 VPN network daemon
 n3n 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 n3n 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, n3n moves
 P2P from application to network level.
 .
 Edge is the edge node daemon for n3n which creates a TAP interface to expose
 the n3n virtual LAN.
