Hi Ameen Please read first ./src/plugins/nat/nat44-ed/nat44_ed_doc.rst
Yes, running `nat44 enable` will fail because the correct command as you have copy-pasted in your email is `nat44 plugin enable`. Also please avoid using `nat44 forwarding enable` if you are not sure what it exactly does in nat44-ed implementation. Please read the docs first. That being said, now about the map, the map is implemented in its own plugin and it isn't part of NAT44-ED. So basically if I understand correctly you are trying to pass communication through the IPv6 network. Do you specifically need map-e to cowork with nat or could you use a different solution to translate over 66 (have a look into nat66/nat64). Long time ago there was support for olderver versions of nat plugin to cowork with MAP implementation in VPP. I am pretty sure the NAT44-EI plugin at least maintains some part of the functionality. I can't say though how nat44-ed integrates with MAP nowadays. It would require testing. You can configure port allocation in nat44-ei that "limits for MAP-E CE port choice based on PSID". `vpp# nat44 ei addr-port-assignment-alg map-e psid 10 psid-offset 6 psid-len` Also refer to https://wiki.fd.io/view/VPP/NAT oudtated docs! Be aware that functionality of the old obsolete plugin called SNAT was divided into separate plugins. So information in the doc that mentions NAT44 / NAT64 etc. is referring to SNAT features which nowadays are their own plugins contained in their respective sub folders of src/plugins/nat . I would encourage you to test it with both nat44-ed and nat44-ei plugins. If there are any nat configuration/translation related issues I will gladly help. Best regards, Filip Varga ne 6. 11. 2022 o 21:24 Ameen Al-Azzawi <ameen.azz...@gmail.com> napísal(a): > Hallo Filip, > > > > Thanks in advance for your cooperation. > > Just a heads up. > > I have installed it again on ubuntu 22.04 (coz it has better support with > VPP apparently). > > I have VPP version 22.10 here. > > I found VPP documentation regarding MAP-E and MAP-T: - > > https://wiki.fd.io/view/VPP/Configure_an_LW46_(MAP-E)_Terminator > > > > The question is, Is VPP used only as MAP-BR router? or also as MAP-CE? > > And how to configure it? Coz the Dooku is not very clear honestly. > > > Take your time and good night :) > > > Regards > > Ameen > > On Sat, Nov 5, 2022 at 10:28 PM Filip Varga <filipvarg...@gmail.com> > wrote: > >> Hi Ameen, >> >> I will look into it and let you know. >> >> Best regards, >> Filip Varga >> >> >> so 5. 11. 2022 o 13:13 Ameen Al-Azzawi <ameen.azz...@gmail.com> >> napísal(a): >> >>> Hello Filip, >>> >>> I saw your reply to one of the MAP-related topics. >>> >>> >>> I am trying to build the topology of MAP-E and MAP-T IPv6 transition >>> technology. >>> >>> I am starting with MAP-E (IETF RFC- 7597). >>> >>> >>> >>> Please see attached pic of my Topology. >>> >>> I am trying to build “MAP-CE” and “MAP-BR” machines using VPP. >>> >>> Is It possible? >>> >>> On both MAP-CE and MAP-BR machines, I have successfully installed VPP >>> (v20.09) >>> >>> All machines are CentOS-7 VMs. >>> >>> On MAP-CE machine, I have used below startup configuration: - >>> >>> >>> >>> unix { >>> >>> nodaemon >>> >>> log /var/log/vpp/vpp.log >>> >>> interactive >>> >>> full-coredump >>> >>> cli-listen /run/vpp/cli.sock >>> >>> poll-sleep-usec 100 >>> >>> startup-config setup.tmpl >>> >>> gid vpp >>> >>> } >>> >>> api-trace { on } >>> >>> api-segment { gid vpp } >>> >>> socksvr { default } >>> >>> dpdk { >>> >>> log-level debug >>> >>> dev default { >>> >>> num-rx-desc 512 >>> >>> num-tx-desc 512 >>> >>> } >>> >>> >>> >>> dev 0000:07:12.6 { >>> >>> name ens34 >>> >>> } >>> >>> dev 0000:07:13.0 { >>> >>> name ens35 >>> >>> } >>> >>> uio-driver vfio-pci >>> >>> } >>> >>> cpu {} >>> >>> # memory { >>> >>> # main-heap-size 1G >>> >>> # main-heap-page-size 1G >>> >>> # default-hugepage-size 1G >>> >>> # } >>> >>> logging { >>> >>> default-log-level debug >>> >>> default-syslog-log-level debug >>> >>> } >>> >>> >>> >>> plugins { >>> >>> plugin dpdk_plugin.so { enable } >>> >>> plugin dhcp_plugin.so { enable } >>> >>> plugin nat_plugin.so { enable } >>> >>> plugin nat44_plugin.so { enable } >>> >>> plugin nat44_ei_plugin.so { enable } >>> >>> plugin cnat_plugin.so { enable } >>> >>> plugin ping_plugin.so { enable } >>> >>> plugin det44_plugin.so { enable } >>> >>> plugin map_plugin.so { enable } >>> >>> plugin dns_plugin.so { enable } >>> >>> plugin tracedump_plugin.so { enable } >>> >>> } >>> >>> >>> >>> >>> >>> As for networking commands, I intend to use the followings: - >>> >>> nat44 plugin enable sessions 63000 >>> >>> nat44 forwarding enable >>> >>> set nat timeout udp 3000 tcp-established 7440 tcp-transitory 2400 icmp >>> 600 >>> >>> set interface nat44 out ens35 output-feature >>> >>> nat44 add static mapping tcp local 10.0.0.2 5000 external 203.0.113.1 >>> 1050 >>> >>> nat44 add interface address ens35 >>> >>> >>> However, inside VPP (I mean after entering vppctl) >>> >>> I got the error below: - >>> >>> >>> >>> vpp# nat44 enable >>> >>> nat44: unknown input `enable' >>> >>> -- >>> >>> How can I add the tunneling commands to my configuration so that MAP-CE >>> functions as NAT44 + encapsulator. >>> >>> Last question, instead of static mapping, can I implement dynamic >>> mapping? >>> >>> What is missing? >>> >>> >>> >>> Kind Regards >>> >>> Ameen >>> >>> >>> >>
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22168): https://lists.fd.io/g/vpp-dev/message/22168 Mute This Topic: https://lists.fd.io/mt/94825188/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] -=-=-=-=-=-=-=-=-=-=-=-
