New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect half-way destination address shown for port-forwarded ASA flows #1398
Comments
Implemented as a preference under Interfaces: As you can see now (by using the pcap provided) both src and dst ips and ports are those in the post-nat:
New builds will be available tomorrow. |
Somehow I do not see (post-NAT data) it at least for WAN->LAN connections. I provided LAN->LAN example, it is possible that it is different, or the fix does not work. Will follow up with more data. |
I tested with the pcap provided and it works. Remember that you have to upgrade nprobe as well, not just ntopng. If you experience some other issues, please make sure to provide a pcap so I can reproduce |
Ok. Will be able to do tests and captures next weekend (I hope). |
Please see pcap and screenshots here . There're 4 flows there:
|
P.S. Re-did all tests with second switch ( |
Re-tested on v.3.1.170928 with same (first on, second off) and reverse (first off, second on) switches position. Same results. |
everything looks correct here as well. The destination address is overridden with its post-nat 10.xxx IP address as specified in the settings. |
also this is consistent with the expected behavior as you can see from the screen capture. For the sake of completeness, here is the nprobe configuration I have used to to the tests:
|
It is working on your screenshots, but not in my system. But I didn't change nprobe conf/command line, only ntopng settings (didn't realize I should). Will come back after testing with -T. |
I've added 3 more lines to
Problems with IP-addresses are gone, but traffic values are now completely wrong: right now Top Local Talkers contains 405.52 Mbit/s in the first line (on a 100 Mbit/s interface), Top Remote Destinations 4.05 kbit/s, and Top Application Traffic is two digits kbits. Looks like some of the field values are taken from wrong places. Do you know what I'm doing wrong and/or how can I verify correctness of template used? |
try to remove --flow-version as well. Apart from the throughput values that you mentioned, are the total values of bytes and packets correct? |
Removing --flow-version did not help. When I list specific flows, their Total Bytes value looks correct. |
Please see 2017-08-09.pcap.gz. It includes just two flows. First flow (533847104) is shown for comparison, it has no port forwarding and does not cause problems. Second flow (533847166) utilizes port-forwarding. Here's information about it as decoded by Wireshark:
Here port 22 of ASA address
83.69.211.186
is forwarded to port 22 of internal host10.6.77.241
. For this kind of flows ntopng currently shows83.69.211.186
as destination. This is incorrect, the destination is actually10.6.77.241
, and83.69.211.186
is just an ASA's address where connection is routed.Thus, in place of
DstAddr
thePost NAT Destination IPv4 Address
field must be used. Likewise for port in place ofDstPort
thePost NAPT Destination Transport Port
must be used (they can be different depending on port forwarding rules).The text was updated successfully, but these errors were encountered: