You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of today, ntopng allows users to choose what IP (PRE/POST) NAT are used in the GUI.
Today we keep one or the other and had to choose "Use Post-Nat Destination IPv4 Addresses and Ports" or "Use Post-Nat Source IPv4 Addresses and Ports" to replace those values in ntopng preferences even if nProbe is sending over all of:
--- [225][Len 4] %POST_NAT_SRC_IPV4_ADDR %postNatSourceIPv4Address Post Nat Source IPv4 Address
--- [226][Len 4] %POST_NAT_DST_IPV4_ADDR %postNatDestinationIPv4Address Post Nat Destination IPv4 Address
--- [227][Len 2] %POST_NAPT_SRC_TRANSPORT_PORT %postNaptSourceTransportPort Post Napt Source Transport Port
--- [228][Len 2] %POST_NAPT_DST_TRANSPORT_PORT %postNaptDestinationTransportPort Post Napt Destination Transport Port .
This ticket is to request to store both in ClickHouse and Elastic and perform searches on both PRE/POST fields
The text was updated successfully, but these errors were encountered:
As of today, ntopng allows users to choose what IP (PRE/POST) NAT are used in the GUI.
Today we keep one or the other and had to choose "Use Post-Nat Destination IPv4 Addresses and Ports" or "Use Post-Nat Source IPv4 Addresses and Ports" to replace those values in ntopng preferences even if nProbe is sending over all of:
This ticket is to request to store both in ClickHouse and Elastic and perform searches on both PRE/POST fields
The text was updated successfully, but these errors were encountered: