In my case, using 2 workers configed in startup.conf when using“set nat worker 0”, it works well; when using “set nat worker 1”, the problem appeared just like using default nat workers config ;
发件人: <lihongli...@360.cn> 日期: 2017年12月24日 星期日 下午10:40 收件人: "Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco)" <matfa...@cisco.com> 抄送: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> 主题: Re: The performance problem of NAT plugin I found that if use one working thread, the problem have resolved; I think this is cause by multi-thread , the respond packets pass to other threads; 在 2017年12月21日，下午9:23，Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) <matfa...@cisco.com<mailto:matfa...@cisco.com>> 写道： Hi, There are processed some packets in both NAT directions (in2out and out2in) so some packets pass NAT plugin. Do you see some packets on interfaces? Matus
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
