ED NAT no longer has “user” concept and it doesn’t differentiate one session from another. (So technically the API works just fine). Even if we wanted to recreate that information it means to build a hash of “users” on the fly for API purpose, do the dump and then throw it away. I don’t see any other way to guarantee that there are no duplicates in the dump even if we didn’t care for numbers like number of sessions or so…
Thanks, Klement > On 12 May 2020, at 15:56, Alexander Chernavin via lists.fd.io > <achernavin=netgate....@lists.fd.io> wrote: > > Klement, > > I would prefer the existing API working. > > I expect millions of sessions and it's clear that dumping them all is a > blocker but during debug, there are not so many of them. > > Thanks, > Alexander
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16345): https://lists.fd.io/g/vpp-dev/message/16345 Mute This Topic: https://lists.fd.io/mt/74156168/21656 Mute #nat44: https://lists.fd.io/mk?hashtag=nat44&subid=1480452 Mute #nat: https://lists.fd.io/mk?hashtag=nat&subid=1480452 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
