Thank you. Enabling DPD is not necessary to reproduce the issue. You can use
`swanctl --list-sas` command to query SAs and see the problem.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22342): https://lists.fd.io/g/vpp-dev/message/22342
Mute
Hi Mahdi,
We haven’t ever tried DPD features with sswan plugin, so I don’t have any info.
I think we need to investigated and reproduce this memory growth issue in our
end, I will keep you posted.
regards
Kai
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
Hi Kai,
Thanks for your response. Yes your understanding is correct and
`stat_segment_connect` is called only when querying SAs. This query does not
occur unless: 1) you ask for SA status and 2) before sending DPD messages. I'm
afraid using 5.9.6 version did not change anything. May I ask if
Hi Mahdi,
Thank you for report your discovery in vpp_sswan, unfortunately we haven't see
this memory growth issue in our end.
If my understanding is correct, the stat_segment_connect function should be
called only if you want to see how many packets and bytes were processed by
each SA, and the
Hi,
I used the plugin resided in `extras/vpp_sswan` on both 5.9.8 and 5.8.2
Strongswan versions. All functionalities are working great but after Child SAs
are established, there's a constant memory growth in charon process( Reaching
from 20MB RSS to 46MB RSS in 4 days, but this growth is
