Package: tayga Version: 0.9.2-10 Severity: normal Dear Maintainer,
The map directive no longer works. I use tayga as a clat for 464xlat and the attached config shows that setup. The addresses and routes are configured separately via iproute2. The tayga interface in my setup gets assigned 192.0.0.2 and the default IPv4 route pointed out that interface. I have a map setup so that traffic entering tayga from 192.0.0.2 gets mapped to 2001:db8::cafe however in a recent update this goes ignored. Instead outbound packets originate from an address created by combining the prefix with the v4 origin, in this case 2001:db8:64:ff9b::192.0.0.2. The last good version is 0.9.2-8, something in -9 broke this setup. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.11.0 (SMP w/32 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages tayga depends on: ii init-system-helpers 1.67 ii libc6 2.40-2 ii sysvinit-utils [lsb-base] 3.10-2 tayga recommends no packages. tayga suggests no packages. -- Configuration Files: /etc/default/tayga changed: CONFIGURE_IFACE="no" CONFIGURE_NAT44="no" DAEMON_OPTS="" IPV4_TUN_ADDR="" IPV6_TUN_ADDR="" /etc/tayga.conf changed: tun-device clat ipv4-addr 192.0.0.1 prefix 2001:db8:64:ff9b::/96 map 192.0.0.2 2001:db8::cafe -- no debconf information
