GNUNET-NAT-SERVER(1) General Commands Manual GNUNET-NAT-SERVER(1)NAME
gnunet-nat-server - help GNUnet setup test network setup with NAT
SYNOPSIS
gnunet-nat-server [options] PORT
DESCRIPTION
Normal GNUnet end-users should not concern themselves with gnunet-nat-server. In fact, distributions are encouraged to consider not ship-
ping it at all. Running gnunet-nat-server's is similar to running hostlist servers: it is a special service to the community with special
requirements and no benefit to those running the service.
This program will listen on the specified PORT for incoming requests to test a peer's network connectivity. Incoming requests can ask it
to connect to a given IPv4 address (and port) using TCP or UDP and to send a 2-byte test message using the specified address. The program
can also be asked to send a "fake" ICMP response message to a given IPv4 address (for autonomous NAT traversal --- see the description in
the respective research paper).
The idea is that gnunet-nat-server will be run on some trusted hosts with unrestricted connectivity to allow GNUnet users to test their
network configuration. As written, the code allows any user on the Internet to cause the gnunet-nat-server to send 2-bytes of arbitrary
data to any TCP or UDP port at any address. We believe that this is generally harmless.
When running gnunet-nat-server, make sure to use a configuration that disables most NAT options but enables 'enable_nat_client' and sets
'internal_address' to the global IP address of your local host. Also, the gnunet-helper-nat-client should be installed locally and run
with root privileges (SUID), otherwise the gnunet-nat-server will not work properly.
Note that gnunet-nat-server could be run via gnunet-arm but typically is not. Also, the name of the host and port that gnunet-nat-server
is run on should be specified in the NATSERVER option in the [setup] section of the configuration file of hosts that are supposed to auto-
configure with this server.
OPTIONS -c FILENAME, --config=FILENAME
Use the configuration file FILENAME.
BUGS
Report bugs by using Mantis <https://gnunet.org/bugs/> or by sending electronic mail to <gnunet-developers@gnu.org>
SEE ALSO gnunet-transport(1)GNUnet 25 Feb 2012 GNUNET-NAT-SERVER(1)
Check Out this Related Man Page
GNUNET-VPN(1) General Commands Manual GNUNET-VPN(1)NAME
gnunet-vpn - manually setup a GNUnet VPN tunnel
SYNOPSIS
gnunet-vpn [options]
DESCRIPTION
gnunet-vpn can be used to manually setup a VPN tunnel via the GNUnet network. There are two main types of tunnels. Tunnels to an exit
node which routes the traffic to the global Internet, and tunnels to a node that runs a service only within GNUnet. Depending on the type
of tunnel, gnunet-vpn takes different options. The "-i" option is required for tunnels to an exit node, whereas the "-p" and "-s" options
in conjunction with either "-u" or "-t" are required for tunnels to services. For exit tunnels, both UDP and TCP traffic will be redi-
rected. For service tunnels, either UDP ("-u") or TCP ("-t") traffic will be redirected.
The tool will display the IP address for this end of the tunnel. The address can be displayed as soon as it has been allocated, or only
after ("-a") the tunnel has been created.
OPTIONS -4, --ipv4
Desired IP address on this end of the tunnel should be an IPv4 address.
-6, --ipv6
Desired IP address on this end of the tunnel should be an IPv6 address.
-a, --after-connect
Display IP address only after the tunnel is fully connected.
-c FILENAME, --config=FILENAME
Use the configuration file FILENAME.
-d SEC, --duration SEC
The mapping should be established for SEC seconds. Default is 5 minutes.
-h, --help
Print short help on options.
-i IP, --ip IP
Tunnel should be to an exit node and connect to the given IPv4 or IPv6 IP address. Note that you can specify an IPv6 address as the
target here, even in combination with "-4" (4to6) and similarly you can specify an IPv4 address in combination with "-6" (6to4).
-L LOGLEVEL, --loglevel=LOGLEVEL
Use LOGLEVEL for logging. Valid values are DEBUG, INFO, WARNING and ERROR.
-p PEERID, --peer=PEERID
Name of the peer offering the service to connect to. Cannot be used in conjunction with "-i", requires "-s".
-s NAME, --service=NAME
Name of the service running on the target peer. Cannot be used in conjunction with "-i", requires "-p".
-t, --tcp
Service runs TCP. Either "-t" or "-u" must be specified when using "-s".
-u, --udp
Service runs UDP. Either "-t" or "-u" must be specified when using "-s".
-V, --verbose
Be verbose.
-v, --version
Print GNUnet version number.
BUGS
Report bugs by using Mantis <https://gnunet.org/bugs/> or by sending electronic mail to <gnunet-developers@gnu.org>
SEE ALSO gnunet-setup(1)GNUnet 25 Feb 2012 GNUNET-VPN(1)