Hello Ole,
I'm not sure I get your question right.
The use case is being able to see NAT pool utilization and debug NAT sessions.
I think it's not a specific use case.
NAT44 ED sessions:
-------- thread 0 vpp_main: 3 sessions --------
i2o 10.255.10.100 proto icmp port 1593 fib 0
o2i 10.100.200.14 proto icmp port 16253 fib 0
external host 10.255.30.100:0
index 0
last heard 27.67
total pkts 8, total bytes 728
dynamic translation
i2o 10.255.10.100 proto udp port 45177 fib 0
o2i 10.100.200.14 proto udp port 18995 fib 0
external host 10.255.30.100:8161
index 1
last heard 32.66
total pkts 2, total bytes 106
dynamic translation
i2o 10.255.10.100 proto tcp port 59664 fib 0
o2i 10.100.200.14 proto tcp port 53893 fib 0
external host 10.255.30.100:22
index 2
last heard 36.64
total pkts 9, total bytes 635
dynamic translation
The way I see it is that there was API that worked for ED and non ED NAT modes
(except for deterministic). ED mode logic has changed but API remains the same.
It still works for non ED NAT modes and has stopped working for ED mode. I
think it's not consistent.
Thanks,
Alexander
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16352): https://lists.fd.io/g/vpp-dev/message/16352
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]
-=-=-=-=-=-=-=-=-=-=-=-
