The commit adds options for static mapping, which is essential for
464xlat(clat) usage. But be noted that routes and firewall rules have
to be configured manually, for now.
To use tayga as clat/nat46:
0. specify $ipv4_addr, $prefix, $map_{ipv4,ipv6} properly, and
set $noroutes to 1 to prevent creating routes for nat64
1. add custom IPv4 routes to tayga, possibly with a reasonable metric
for default route
2. add a SNAT firewall rule for processing IPv4 traffic destined for
tayga
3. add firewall rules to allow FORWARD traffic between tayga and WAN6
4. add a $map_ipv6 route to tayga for guiding return traffic
Signed-off-by: Hung-I Wang <whygowe@gmail.com>
fix Makefile chmod (644)
replace MD5SUM with HASH
add PKG_MIRROR_HASH when PKG_SOURCE_PROTO:=git
(PKG_SOURCE_PROTO:=svn tarballs are not reproducible for now)
Signed-off-by: Etienne Champetier <champetier.etienne@gmail.com>
This patch integrates tayga with netifd. Parametres are nearly same as
with the older scripts. Support for static mapping of IPv4<=>IPv6 addresses
is missing. Example configuration:
config interface 'nat64'
option proto 'tayga'
option prefix 64:ff9b::/96
option dynamic_pool 10.128.0.0/24
option ipv4_addr 10.128.0.1 #address of the TAYGA itself
option ipv6_addr 2001:470:5990::64
option ipaddr 192.168.1.1 #optional address of TUN interface
option ip6addr 2001:db8::1
Signed-off-by: Ondrej Caletka <ondrej@caletka.cz>
Rosen Penev
Hung-I Wang
Eike Ritter
Etienne Champetier
Steven Barth
Nicolas Thill
Ian Leonard
Ondřej Caletka