1,775
edits
Settings: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 255: | Line 255: | ||
decrease the time difference by which packets are stored out of their real order in the packet ring buffer but | decrease the time difference by which packets are stored out of their real order in the packet ring buffer but | ||
it may also decrease the performance of the packet ring buffer. | it may also decrease the performance of the packet ring buffer. | ||
'''Data retention timeout''' | '''Data retention timeout''' | ||
When this timeout is set to a value greater than 0, data will be removed from the system after the given number of minutes. | |||
This means that entities like IPs, which have been inactive for longer than the timeout, will be removed. | |||
History graph data for entities that are still active will be truncated to cover only the given timespan while the absolute values for the whole runtime will be retained. When a packet ring buffer is active, packets which are older than the timeout will be discarded. | |||
'''L3 tunnel mode''' | '''L3 tunnel mode''' | ||
If L3 tunnel mode is enabled for an interface this interface will only process packets encapsulated in GRE or GRE+ERSPAN and targeted for the configured IP address. All other packets received on that interface will be discarded. | |||
The system will process the packets as if only the inner encapsulated packet is seen and any traffic captures will only contain the encapsulated packet. | |||
An interface with L3 tunnel mode enabled will respond to ARP requests and to ICMP echo requests so it is possible to use ping to verify that the interface is reachable under the configured IP address. | |||
Currently only IPv4 L3 tunnels are supported. | |||
It must be noted that if the system is running in bridge packet processing mode any links with an interface configured for L3 tunnel mode will not forward traffic. | |||