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)
Check Out this Related Man Page
SHOREWALL6-TUNNELS(5) [FIXME: manual] SHOREWALL6-TUNNELS(5) NAME
tunnels - Shorewall6 VPN definition file SYNOPSIS
/etc/shorewall6/tunnels DESCRIPTION
The tunnels file is used to define rules for encapsulated (usually encrypted) traffic to pass between the Shorewall6 system and a remote gateway. Traffic flowing through the tunnel is handled using the normal zone/policy/rule mechanism. See http://www.shorewall.net/VPNBasics.html for details. The columns in the file are as follows (where the column name is followed by a different name in parentheses, the different name is used in the alternate specification syntax). TYPE - {ipsec[:{noah|ah}]|ipsecnat|gre|l2tp|pptpclient|pptpserver|{openvpn|openvpnclient|openvpnserver}[:{tcp|udp}][:port]|generic:protocol[:port]} Types are as follows: ipsec - IPv6 IPSEC ipsecnat - IPv6 IPSEC with NAT Traversal (UDP port 4500 encapsulation) gre - Generalized Routing Encapsulation (Protocol 47) l2tp - Layer 2 Tunneling Protocol (UDP port 1701) openvpn - OpenVPN in point-to-point mode openvpnclient - OpenVPN client runs on the firewall openvpnserver - OpenVPN server runs on the firewall generic - Other tunnel type If the type is ipsec, it may be followed by :ah to indicate that the Authentication Headers protocol (51) is used by the tunnel (the default is :noah which means that protocol 51 is not used). NAT traversal is only supported with ESP (protocol 50) so ipsecnat tunnels don't allow the ah option (ipsecnat:noah may be specified but is redundant). If type is openvpn, openvpnclient or openvpnserver it may optionally be followed by ":" and tcp or udp to specify the protocol to be used. If not specified, udp is assumed. Note: At this writing, OpenVPN does not support IPv6. If type is openvpn, openvpnclient or openvpnserver it may optionally be followed by ":" and the port number used by the tunnel. if no ":" and port number are included, then the default port of 1194 will be used. . Where both the protocol and port are specified, the protocol must be given first (e.g., openvpn:tcp:4444). If type is generic, it must be followed by ":" and a protocol name (from /etc/protocols) or a protocol number. If the protocol is tcp or udp (6 or 17), then it may optionally be followed by ":" and a port number. ZONE - zone The zone of the physical interface through which tunnel traffic passes. This is normally your internet zone. GATEWAY(S) (gateway or gateways) - address-or-range [ , ... ] The IP address of the remote tunnel gateway. If the remote gateway has no fixed address (Road Warrior) then specify the gateway as ::/0. May be specified as a network address and if your kernel and ip6tables include iprange match support then IP address ranges are also allowed. Beginning with Shorewall 4.5.3, a list of addresses or ranges may be given. Exclusion (shorewall6-exclusion[1] (5) ) is not supported. GATEWAY ZONE(S) (gateway_zone or gateway_zones) - [zone[,zone]...] Optional. If the gateway system specified in the third column is a standalone host then this column should contain a comma-separated list of the names of the zones that the host might be in. This column only applies to IPSEC tunnels where it enables ISAKMP traffic to flow through the tunnel to the remote gateway(s). EXAMPLE
Example 1: IPSec tunnel. The remote gateway is 2001:cec792b4:1::44. The tunnel does not use the AH protocol #TYPE ZONE GATEWAY ipsec:noah net 2002:cec792b4:1::44 Example 2: Road Warrior (LapTop that may connect from anywhere) where the "gw" zone is used to represent the remote LapTop #TYPE ZONE GATEWAY GATEWAY ZONES ipsec net ::/0 gw Example 3: Host 2001:cec792b4:1::44 is a standalone system connected via an ipsec tunnel to the firewall system. The host is in zone gw. #TYPE ZONE GATEWAY GATEWAY ZONES ipsec net 2001:cec792b4:1::44 gw Example 4: OPENVPN tunnel. The remote gateway is 2001:cec792b4:1::44 and openvpn uses port 7777. #TYPE ZONE GATEWAY GATEWAY ZONES openvpn:7777 net 2001:cec792b4:1::44 Example 8: You have a tunnel that is not one of the supported types. Your tunnel uses UDP port 4444. The other end of the tunnel is 2001:cec792b4:1::44. #TYPE ZONE GATEWAY GATEWAY ZONES generic:udp:4444 net 2001:cec792b4:1::44 FILES
/etc/shorewall6/tunnels SEE ALSO
http://shorewall.net/configuration_file_basics.htm#Pairs shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5), shorewall6-maclist(5), shoewall6-netmap(5),shorewall6-params(5), shorewall6-policy(5), shorewall6-providers(5), shorewall6-rtrules(5), shorewall6-routestopped(5), shorewall6-rules(5), shorewall6.conf(5), shorewall6-secmarks(5), shorewall6-tcclasses(5), shorewall6-tcdevices(5), shorewall6-tcrules(5), shorewall6-tos(5), shorewall6-zones(5) NOTES
1. shorewall6-exclusion http://www.shorewall.net/manpages6/shorewall6-exclusion.html [FIXME: source] 06/28/2012 SHOREWALL6-TUNNELS(5)