gnunet-namestore(1) [debian man page]
GNUNET-NAMESTORE(1) General Commands Manual GNUNET-NAMESTORE(1) NAME
gnunet-namestore - manipulate GNUnet zones SYNOPSIS
gnunet-namestore [options]-zZONEFILE DESCRIPTION
gnunet-namestore can be used to create and manipulate a GNS zone. OPTIONS
-a, --add Desired operation is adding a record -c FILENAME, --config=FILENAME Use the configuration file FILENAME. -d, --delete Desired operation is deleting a record -D, --display Desired operation is listing of matching records -e TIME, --expiration=TIME Specifies expiration time of record to add; format is relative time, i.e "1 h" or "7 d 30 m". Supported units are "ms", "s", "min" or "minutes", "h" (hours), "d" (days) and "a" (years). -h, --help Print short help on options. -L LOGLEVEL, --loglevel=LOGLEVEL Use LOGLEVEL for logging. Valid values are DEBUG, INFO, WARNING and ERROR. -n NAME, --name=NAME Name of the record to add/delete/display -t TYPE, --type=TYPE Type of the record to add/delete/display (i.e. "A", "AAAA", "NS", "PKEY", "MX" etc.) -v, --version Print GNUnet version number. -V VALUE, --value=VALUE Value to store or remove from the GNS zone. Specific format depends on the record type. A records expect a dotted decimal IPv4 address, AAAA records an IPv6 address, PKEY a public key in GNUnet's printable format, and CNAME and NS records should be a domain name. -z FILENAME, --zonekey=FILENAME Specifies the filename with the private key for the zone (mandatory option) BUGS
Report bugs by using Mantis <https://gnunet.org/bugs/> or by sending electronic mail to <gnunet-developers@gnu.org> SEE ALSO
gnunet-gns(1) GNUnet Mar 5, 2012 GNUNET-NAMESTORE(1)
Check Out this Related Man Page
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)