1#
2# Sample configuration file for TAYGA 0.9.2
3#
4# Modify this to use your own addresses!!
5#
6
7#
8# TUN device that TAYGA will use to exchange IPv4 and IPv6 packets with the
9# kernel.  You may use any name you like, but `nat64' is recommended.
10#
11# This device may be created before starting the tayga daemon by running
12# `tayga --mktun`.  This allows routing and firewall rules to be set up prior
13# to commencement of packet translation.
14#
15# Mandatory.
16#
17tun-device nat64
18
19#
20# TAYGA's IPv4 address.  This is NOT your router's IPv4 address!  TAYGA
21# requires its own address because it acts as an IPv4 and IPv6 router, and
22# needs to be able to send ICMP messages.  TAYGA will also respond to ICMP
23# echo requests (ping) at this address.
24#
25# This address can safely be located inside the dynamic-pool prefix.
26#
27# Mandatory.
28#
29ipv4-addr 192.168.254.1
30
31#
32# TAYGA's IPv6 address.  This is NOT your router's IPv6 address!  TAYGA
33# requires its own address because it acts as an IPv4 and IPv6 router, and
34# needs to be able to send ICMP messages.  TAYGA will also respond to ICMP
35# echo requests (ping6) at this address.
36#
37# You can leave ipv6-addr unspecified and TAYGA will construct its IPv6
38# address using ipv4-addr and the NAT64 prefix.
39#
40# Optional if the NAT64 prefix is specified, otherwise mandatory.  It is also
41# mandatory if the NAT64 prefix is 64:ff9b::/96 and ipv4-addr is a private
42# (RFC1918) address.
43#
44#ipv6-addr 2001:db8:1::2
45ipv6-addr fdaa:bb:1::1
46
47#
48# The NAT64 prefix.  The IPv4 address space is mapped into the IPv6 address
49# space by prepending this prefix to the IPv4 address.  Using a /96 prefix is
50# recommended in most situations, but all lengths specified in RFC 6052 are
51# supported.
52#
53# This must be a prefix selected from your organization's IPv6 address space
54# or the Well-Known Prefix 64:ff9b::/96.  Note that using the Well-Known
55# Prefix will prohibit IPv6 hosts from contacting IPv4 hosts that have private
56# (RFC1918) addresses, per RFC 6052.
57#
58# The NAT64 prefix need not be specified if all required address mappings are
59# listed in `map' directives.  (See below.)
60#
61# Optional.
62#
63##prefix 2001:db8:1:ffff::/96
64prefix 64:ff9b::/96
65
66#
67# Dynamic pool prefix.  IPv6 hosts which send traffic through TAYGA (and do
68# not correspond to a static map or an IPv4-translatable address in the NAT64
69# prefix) will be assigned an IPv4 address from the dynamic pool.  Dynamic
70# maps are valid for 124 minutes after the last matching packet is seen.
71#
72# If no unassigned addresses remain in the dynamic pool (or no dynamic pool is
73# configured), packets from unknown IPv6 hosts will be rejected with an ICMP
74# unreachable error.
75#
76# Optional.
77#
78dynamic-pool 192.168.254.0/24
79
80#
81# Persistent data storage directory.  The dynamic.map file, which saves the
82# dynamic maps that are created from dynamic-pool, is stored in this
83# directory.  Omit if you do not need these maps to be persistent between
84# instances of TAYGA.
85#
86# Optional.
87#
88data-dir /var/spool/tayga
89
90#
91# Establishes a single-host map.  If an IPv6 host should be consistently
92# reachable at a specific IPv4 address, the mapping can be specified in a
93# `map' directive.  (IPv6 hosts numbered with an IPv4-translatable address do
94# not need map directives.)
95#
96# IPv4 addresses specified in the `map' directive can safely be located inside
97# the dynamic-pool prefix.
98#
99# Optional.
100#
101#map 192.168.5.42 2001:db8:1:4444::1
102#map 192.168.5.43 2001:db8:1:4444::2
103#map 192.168.255.2 2001:db8:1:569::143
104