packages/ipv6/tayga/files, branch master

tayga: move to net

2025-07-24T13:33:18Z

* moving to net to align with similar package jool Signed-off-by: Goetz Goerisch

tayga: add options for static mapping

2024-09-03T18:53:08Z

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

tayga: allow more flexible routing

2015-02-10T02:34:10Z

In some scenarios (e.g. 464xlat) it is desirable to not route the mapped prefix to tayga's interface. This adds an option 'noroutes' which, when set to 1, will prevent such routes from being added. Signed-off-by: Nils Schneider

tayga: Add Netifd support

2014-06-23T14:25:05Z

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

tayga: import from oldpackages

2014-06-23T13:44:35Z

Signed-off-by: Ondrej Caletka