Hi Jon, > I have a few questions in the MAP-E/MAP-T area. > > First the easy one: > > In the src/plugin/map/map.h file, there is a #include <map/map_dpo.h>. > That works fine in the source tree and the source-tree-based builds. > However, once installed on a system where out-of-tree builds take place, > It makes for an odd system-level include path because the "vpp_plugins" piece > is missing. Can we change that to '#include <vpp_plugins/map/map_dpo.h>”?
I have an in motion change to remove map_dpo.h and replace it with MAP as an input feature. If you can’t wait for that, feel free to do the include fix. > And second, are there plans somewhere already in-motion to add an API > interface to the MAP-E/T configuration parameters? They are already > available and configurable by the vppctl CLI, but not via the API. Would > anyone be interested in a patch to refactor that parameter handling to allow > API access to those parameters too? Yes. I’m cleaning that up now too. > Finally, are there any known issues/bugs in the MAP-E/MAP-T packet-handling? MAP-E is more tested than MAP-T. But I’m doing quite a bit of work on it now. Both are feature complete, also around the more complex areas of fragmentation handling and ICMP error relaying. What’s your time line? Feel free to contact me off-list with more details. On my todo list is: - MSS clamping - TX == RX loopback forwarding (By-pass lookup/rewrite on transmit) - Types in API - MAP-T checksum improvements - More performance work Cheers, Ole
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11323): https://lists.fd.io/g/vpp-dev/message/11323 Mute This Topic: https://lists.fd.io/mt/28244962/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
