546
edits
Path measurement: Difference between revisions
no edit summary
m (→Two-Way-Latency: language improvements) |
No edit summary |
||
| Line 60: | Line 60: | ||
* '''Account latency also per IP connection''': Enabling this option will let the path measurement also store the latency for each individual IP connection, which of course increases the memory usage. | * '''Account latency also per IP connection''': Enabling this option will let the path measurement also store the latency for each individual IP connection, which of course increases the memory usage. | ||
* '''Enable NAT mode''' (Firmware >= 4.3): This feature will enable support for Network-Address-Translation setup (typical for firewalls or internet uplink routers). | * '''Enable NAT mode''' (Firmware >= 4.3): This feature will enable support for Network-Address-Translation setup (typical for firewalls or internet uplink routers). | ||
** ''' | ** '''NAT Private subnet/mask:''' This value describes the internal IP addresses that gets translated into an external IP address. An example value is "192.168.1.0/24" if all internal devices uses IP addresses in the range 192.168.1.0-192.168.1.255. | ||
** '''NAT | ** '''NAT Public subnet/mask:''' This value defines the external IP address that internal IPs of the private subnet are translated to. It can also be an IP subnet (for example, if multiple external IP addresses are used). An example value is "10.1.2.3" if the NAT router is using the external IP 10.1.2.3 and all its internal clients are visible under this IP. | ||
** '''Account unmatched flows:''' This option allows to monitor also connections there are not seen on the other measurement side. This is useful to see blocked connections in firewall setups. | ** '''Account unmatched flows:''' This option allows to monitor also connections there are not seen on the other measurement side. This is useful to see blocked connections in firewall setups. | ||