Getting Started

Why Version 2

  • Better encryption. n2n-v1 has a weak security model. We have tried to improve the model without adding complexity to configuration.
    • Added AES 256 bit encryption to the TwoFish? offering.
    • Added space for many more standard operations.
    • Added space for user-defined custom compression/encryption etc.
    • Key leakage prevention by use of packet nonces.
    • Optional scheduled key roll-over via key schedule files.
  • Optional compression and encryption. We know it slows down n2n, so some users turn off encryption and compression. In n2n-v1 this breaks compatibility with other n2n users. In n2n-v2 compression and encryption can be turned off without breaking compatibility and without having to rebuild a special version of n2n.
  • Roll you own transform. The same feature that allows compression and encryption to be optional also allows users to build their own data transforms without losing compatibility with the rest of the n2n community. This is to encourage sharing of new and useful schemes.
  • Redundant Supernodes. Many have asked for a way to add multiple supernodes; now it is here. N2n-v2 allows edge to specify multiple supernodes in case the primary fails. But this is only the start. Federated supernodes bring an interconnected mesh of supernodes which can introduce edges which are registered to different supernodes.
  • Management of n2n. Many have asked for a way to find out what is going on inside edge or supernode. N2n-v2 adds some features to support this. Edge and supernode provide a UDP listening socket on 127.0.0.1 so you can get info from your local edge and supernode.
  • Supernode authentication. Some have asked for a way to authenticate edges registering with supernodes. The n2n-v2 protocol has been expanded to support this authentication. This feature is not yet implemented.
  • Improved DHCP Support. DHCP, particularly under windows has been a problem. n2n_v2 adds a new dhcp keyword to the command line and better handling of interface address changes. Windows netsh DHCP support is now implemented.

Packages

User contributed packages for various operating systems are available here:

 http://n2n.ntop.org/packages/n2n_v2

Design Details