RFC7915 supports translation of multicast packets, but does not specify how addresses should be translated. As such, Tayga will not allow translation of multicast packets, as there is no standard format.
We could allow multicast packets to be translated if the following conditions are met:
- The source address is a unicast address and can be translated using existing rules
- The destination address is a multicast address and can be translated using a
map entry (not dynamic-pool and not rfc6052)
- Both the v4 and v6 addresses in the map entry are multicast addresses (we are not converting multicast to unicast)
Note that the link-local multicast scope (224.0.0.0/24 and ff02::/16) cannot be translated because the ttl will be decremented by Tayga. If this is a problem for you, you will need to mangle the packet to increment the TTL in kernel prior to Tayga.
RFC7915 supports translation of multicast packets, but does not specify how addresses should be translated. As such, Tayga will not allow translation of multicast packets, as there is no standard format.
We could allow multicast packets to be translated if the following conditions are met:
mapentry (not dynamic-pool and not rfc6052)Note that the link-local multicast scope (224.0.0.0/24 and ff02::/16) cannot be translated because the ttl will be decremented by Tayga. If this is a problem for you, you will need to mangle the packet to increment the TTL in kernel prior to Tayga.