|GNUNET-NAT(1)||General Commands Manual||GNUNET-NAT(1)|
DESCRIPTION¶This tool allows testing various NAT traversal functions, as well as attempting auto-configuration.
- Assume that the service is (locally) bound to ADDRESS.
- Use the configuration file FILENAME.
- Assume that ADDRESS is the globally visible address of the peer.
- Assuming we are listening at ADDRESS for connection reversal requests.
- Ask the peer at ADDRESS for connection reversal, using the local address for the target address of the reversal.
- Name of section in configuration file to use for additional options.
- Enable processing of STUN requests. Will try to read UDP packets from the bind address and handle the packets if they are STUN packets. Will only work with UDP.
- Use TCP.
- Use UDP.
- Watch for connection reversal requests.
# gnunet-nat -i 0.0.0.0:8080 -u
We are bound to "0.0.0.0:8080" on UDP and want to obtain all applicable IP addresses.
# gnunet-nat -i '[::0]':8080 -t
We are bound to "::0" on port 8080 on TCP and want to obtain all applicable IP addresses.
# gnunet-nat -i 127.0.0.1:8080 -u
We are bound to "127.0.0.1:8080" on UDP and want to obtain all applicable IP addresses:
ICMP-based NAT traversal¶
# gnunet-nat -Wt -i 192.168.178.12:8080
Watch for connection reversal request (you must be bound to NAT range or to wildcard, 0.0.0.0), only works for IPv4:
# gnunet-nat -t -r 22.214.171.124:8080 -i 126.96.36.199:8080
# gnunet-nat -t -r 188.8.131.52:8080 -i 0.0.0.0:8080
Initiate connection reversal request from peer at external IPv4 address 184.108.40.206, and let the kernel fill in whatever IPv4 address we happen to have:
Manual hole punching¶
# gnunet-nat -t -p AUTO:8080
Assume manually punched NAT, but determine external IP automatically:
# gnunet-nat FIXME -s
The full documentation for gnunet is maintained as a Texinfo manual. If the info(1) and gnunet programs are properly installed at your site, the command
should give you access to the complete handbook,
will give you access to a tutorial for developers.
BUGS¶Report bugs by using https://bugs.gnunet.org or by sending electronic mail to <firstname.lastname@example.org>.
|October 26, 2018||Linux 4.19.0-14-amd64|