Hi Filip,
I did try your recommendations . Updated NAT config to as below
Test Case 1
nat44 plugin enable sessions 63000
nat44 forwarding enable
set nat timeout udp 3000 tcp-established 7440 tcp-transitory 2400 icmp 600
set interface nat44 in lan
set interface nat44 out wan1
set interface nat44
As you can see from the lengthy discussion below, VPP is filling yet another
need and so is P4.
Hemant
From: hemant via p4-design
Sent: Tuesday, August 09, 2022 9:46 AM
To: 'Gergely Pongracz' ; mbu...@vmware.com;
jnfos...@cs.cornell.edu
Cc: p4-des...@lists.p4.org
Subject: RE:
Hi Ashwini,
I will look into your issue. But for reference I would advise against using
a combination of inside interface and output-feature.
OUTPUT-FEATURE or in other words output interface already contains
nat44-inside node. Output-feature does postrouting - after ip4-lookup node
decides
Hi Benoit,
Thank you for the quick work!
--
Best regards,
Atzm WATANABE
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21781): https://lists.fd.io/g/vpp-dev/message/21781
Mute This Topic: https://lists.fd.io/mt/92887834/21656
Group Owner:
Hi,
In current implementation of ikev2 plugin, it seems to keep old inbound IPsec
SA for a while after rekeying is done, and this old IPsec SA seems to be
deleted by manager process later.
But it is not deleted and remains forever if rekeying request comes again
before deleting it, because 2
