Does anybody have any tips on implementing SIIT-DC? There is just slightly more than no documentation about it online, and the one VPP page that mentions it was last updated 6 years ago.
So far I have translation working in one direction. The v4 packets get
rewritten correctly and arrive at the v6 host, and the host replies.
However, the v6 packets arrive back at the border relay and just get
dropped (or forwarded to the default route, depending on it's mood)
because they don't seem to match a mapping rule in the other
direction.
Looking at the traces in wireshark I can see that the packets are
processed through the ip6-map-t node, but then they just fall through
to ip6-lookup.
This is the syntax I eventually settled on after much trial and error.
comment { Configure SIIT-DC: 172.16.32.5 -> 2600:8804:5800:301f::5 }
comment { ipv4 src rewritten into 64:ff9b::/96 }
map add domain ip4-pfx 172.16.32.5/32 ip6-pfx
2600:8804:5800:301f::5/128 ip6-src 64:ff9b::/96
comment { Enable Map-T on IPv4 and IPv6 interfaces }
map interface vmxnet3-0/b/0/0 map-t
map interface vmxnet3-0/13/0/0 map-t
I've tried a bunch of combinations of options trying to map in the
reverse direction without success. I've attached a trace pcap filtered
for one specific translation if anyone wants to take a look at it.
Thanks!
Landy
siit-dc-troubleshooting.pcap
Description: Binary data
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22619): https://lists.fd.io/g/vpp-dev/message/22619 Mute This Topic: https://lists.fd.io/mt/97184982/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
