gnunet-vpn(1) [debian 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)

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

NAME

       gnunet-directory - display directories

SYNOPSIS

       gnunet-directory [OPTIONS] (FILENAME)*

DESCRIPTION

       gnunet-directory  lists the contents of one or more GNUnet directories.	A GNUnet directory is a binary file that contains a list of GNUnet
       file-sharing URIs and meta data.  The names of the directory files must be passed as command-line arguments to gnunet-directory.

       -c FILENAME, --config=FILENAME
	      configuration file to use (useless option since gnunet-directory does not really depend on any configuration options)

       -h, --help
	      print help page

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

       -v, --version
	      print the version number

NOTES

       A GNUnet directory is a file containing a list of GNUnet URIs and meta data.  The keys can point to files, other directories  or  files	in
       namespaces.   In  other	words,	a GNUnet directory is similar to UNIX directories.  The difference to tar and zip is that GNUnet directory
       does not contain the actual files (except if they are really small, in which case they may be inlined), just symbolic (links),  similar	to
       directories with symbolic links in UNIX filesystems.  The benefit is that the individual files can be retrieved separately (if desired) and
       if some of the files are inserted to another node in GNUnet, this just increases their availability but does not produce useless duplicates
       (for  example,  it  is a better idea to publish a collection of pictures or compressed sound files using a GNUnet directory instead of pro-
       cessing them with archivers such as tar or zip first).  Directories can contain arbitrary meta data for each file.

       If a directory has missing blocks (for example, some blocks failed to download), GNUnet is typically able  to  retrieve	information  about
       other files in the directory.  Files in a GNUnet directory have no particular order; the GNUnet code that generates a directory can reorder
       the entries in order to better fit the information about files into blocks of 32k.  Respecting 32k boundaries where possible makes it  eas-
       ier for gnunet-directory (and other tools) to recover information from partially downloaded directory files.

       At the moment, directories can be created by gnunet-fs-gtk and gnunet-publish.  Just like ordinary files, a directory can be published in a
       namespace.

       GNUnet directories use the (unregistered) mimetype application/gnunet-directory.  They can show up among normal search results.	The direc-
       tory file can be downloaded to disk by gnunet-download(1) for later processing or be handled more directly by gnunet-fs-gtk(1).

REPORTING BUGS

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

SEE ALSO

       gnunet-fs-gtk(1), gnunet-publish(1), gnunet-search(1), gnunet-download(1)

GNUnet								    25 Feb 2012 					       gnunet-directory(1)