start to list relevant cases in man page, document current limitations

diff --git a/doc/man/gnunet-nat.1 b/doc/man/gnunet-nat.1
index 14b8e1509c365859e1a9c6245575d7a959899301..484537eb03fad879df60d5f59967e0189e9c718f 100644 (file)
--- a/doc/man/gnunet-nat.1
+++ b/doc/man/gnunet-nat.1
@@ -62,6 +62,45 @@ Write configuration to configuration file, useful in combination with autoconfig
 .IP "\-W,  \-\-watch"
 Watch for connection reversal requests.  
 
+.SH EXAMPLES
+.PP
+
+\fBBasic examples\fR
+
+We are bound to "0.0.0.0:8080" on UDP and want to obtain all applicable IP addresses (BUG: sometimes upnpc fails to create mapping, cause unclear):
+
+  # gnunet-nat -i 0.0.0.0:8080 -u
+
+We are bound to "::0" on port 8080 on TCP and want to obtain all applicable IP addresses:
+
+  # gnunet-nat -i '[::0]':8080 -t
+
+We are bound to "127.0.0.1:8080" on UDP and want to obtain all applicable IP addresses (BUG: currently fails, also gives IPs from other interfaces in output!):
+
+  # gnunet-nat -i 127.0.0.1:8080 -u
+
+\fBICMP-based NAT traversal:\fR
+
+Watch for connection reversal request:
+
+  # gnunet-nat FIXME
+
+Initiate connection reversal request:
+
+  # gnunet-nat FIXME
+
+\fBSTUN-based XXX:\fR
+
+XXX:
+
+  # gnunet-nat FIXME -s
+
+\fBAutomatic configuration:\fR
+
+Probe and write result to configuration:
+
+  # gnunet-nat -aw
+  
 
 .SH BUGS
 Report bugs by using Mantis <https://gnunet.org/bugs/> or by sending electronic mail to <gnunet\-developers@gnu.org>