A hint: This file contains one or more very long lines, so maybe it is better readable using the pure text view mode that shows the contents as wrapped lines within the browser window.
Read about Configuration Files as they might come in handy – especially, but not limited to, if edges or supernodes shall be run as a service (see below) or in case of bulk automated parameter generation for mass deployment.
edge can also be run as a service instead of cli:
/etc/n2n/edge.conf
with your custom options. See
/etc/n2n/edge.conf.sample
.sudo systemctl start edge
sudo systemctl enable edge
You can run multiple edge service instances by creating
/etc/n2n/edge-instance1.conf
and starting it with
sudo systemctl start edge@instance1
.
You might be interested to learn some details about Communities and understand how to limit supernodes' services to only a specified set of communities.
It is available a special community which provides interconnection between supernodes. Details about how it works and how you can use it are available in Federation.
The TAP Configuration Guide contains hints on various settings that can be applied to the virtual network device, including IPv6 addresses as well as notes on MTU and on how to draw IP addresses from DHCP servers.
Reaching a remote network or tunneling all the internet traffic via
n2n are two common tasks which require a proper routing setup. n2n
supports routing needs providing options for packet forwarding
(-r
) including broadcasts (-E
) as well as
temporarily modifying the routing table (-n
). Details can
be found in the Routing document.
It is possible to drop or accept specific packet transmit over edge
network interface by rules. Rules can be specify by
(-R rule_str
) multiple times. Details can be found in the
Traffic Restrictions.