gnunet-transport(1) [debian man page]

gnunet-transport(1)					      General Commands Manual					       gnunet-transport(1)

NAME

       gnunet-transport - measure and control the transport subsystem

SYNOPSIS

       gnunet-transport [OPTIONS]

DESCRIPTION

       gnunet-transport  is  a	tool  to  access  various  functions of GNUnet's transport subsystem from the command-line.  Most of these are not
       expected to be useful for end-users.  gnunet-transport can be used to evaluate the performance of the transports, force a peer  to  connect
       to another peer (if possible).  Other functions should be added in the near future.

       -b, --benchmark
	      measure  how  fast  we are receiving data (from all connections).  On exit, the data rate will be reported.  Runs until aborted with
	      CTRL-C.

       -c FILENAME, --config=FILENAME
	      configuration file to use

       -C PEER, --connect=PEER
	      peer to connect to (and to use for sending if used in conjunction with -s)

       -h, --help
	      print help page

       -i, --information
	      print information about our current connections (once)

       -m, --monitor
	      print information about our current connections (continuously)

       -L LOGLEVEL, --loglevel=LOGLEVEL
	      Change the loglevel.  Possible values for LOGLEVEL are ERROR, WARNING, INFO and DEBUG.

       -s, --send
	      transmit (dummy) traffic as quickly as possible to the peer specified with the -C option.  The rate will still  be  limited  by  the
	      quota(s)	determined  by	the  peers (ATS subsystem).  Will run until CTRL-C is pressed or until the connection to the other peer is
	      disrupted.

       -t, --test
	      test transport configuration.  With this flag, the tool will check if each  of  the  configured  transport  plugins  has	a  working
	      address.	 Plugins  that	do  not have a listen port configured will be ignored.	The test is performed with the help of an external
	      server (by default running on gnunet.org) which tries to contact the local machine.  The test can only work if the local GNUnet peer
	      is not yet running.

       -v, --version
	      print the version number

       -V, --verbose
	      be verbose

NOTES

REPORTING BUGS

       Report bugs by using mantis <https://gnunet.org/bugs/> or by sending electronic mail to <gnunet-developers@gnu.org>

SEE ALSO

       gnunet-arm(1)

GNUnet								    26 Oct 2011 					       gnunet-transport(1)

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)