Hey all, This project has come back to the top of the pile, and I still don't have a solution.
I spent some time reading the source code for the map implementation, and while I can generally follow along I'm no C programmer. That said, it looks to me like the part that fails for me is the ip6_map_get_domain function call in line 532 of https://vpp.flirble.org/stable-2106/d8/d3f/ip6__map__t_8c_source.html. The behavior is such that we take the (!d0) branch to vnet_feature_next and exit ip6_map_t. Working backward from there, it would seem that my source ip6 address isn't found in ip6_src_prefix_tbl, and it looks to me like an entry is added to that table in map_create_domain when I configure the domain the first place, so it seems to me that my configuration should just work, but I'm guessing I'm missing something in my configuration. Or there's some bug that this python programmer is missing while trying to read C. Any help getting this working would be greatly appreciated! -Landy On Thu, Feb 23, 2023 at 9:34 AM Landy Bible <la...@ljb2of3.net> wrote: > > 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
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22772): https://lists.fd.io/g/vpp-dev/message/22772 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] -=-=-=-=-=-=-=-=-=-=-=-
