L7 module: Difference between revisions

Jump to navigation Jump to search

L7 module (view source)

Revision as of 14:21, 5 May 2020

5 bytes removed ,  5 May 2020
no edit summary
No edit summary
No edit summary
Line 4: Line 4:
This allows to track or filter specific IP or IP subnets or specific ports.
This allows to track or filter specific IP or IP subnets or specific ports.


 
== Web statistics ==
 
=== L7 protocols ===
'''Web statistics'''
 
'''L7 protocols'''


A history graph sits on top of the page containing the top 10 protocols that created the most traffic.
A history graph sits on top of the page containing the top 10 protocols that created the most traffic.
Line 28: Line 25:




'''Statistics for protocol'''
=== Statistics for protocol ===


These detail view page show statistics for a specific protocol.
These detail view page show statistics for a specific protocol.
Line 45: Line 42:




'''IPs'''
=== IPs ===


In this tab there is a table listing all IP addresses that have sent or received traffic of that particular protocol.  
In this tab there is a table listing all IP addresses that have sent or received traffic of that particular protocol.  
Line 67: Line 64:




'''Layer 3 QoS'''
=== Layer 3 QoS ===


For layer 3 IP differentiated services codepoint (DSCP) are displayed in a table with traffic counters, a history graph of traffic over time and a PCAP button for that certain DSCP value.
For layer 3 IP differentiated services codepoint (DSCP) are displayed in a table with traffic counters, a history graph of traffic over time and a PCAP button for that certain DSCP value.
Line 73: Line 70:




'''Layer 2 QoS'''
=== Layer 2 QoS ===


For layer 2 VLAN priority code points and MPLS traffic classes are analysed and displayed in a table with traffic counters, a history graph of traffic over time and a PCAP button that certain QoS tag.
For layer 2 VLAN priority code points and MPLS traffic classes are analysed and displayed in a table with traffic counters, a history graph of traffic over time and a PCAP button that certain QoS tag.
Line 80: Line 77:




'''Configuration'''
== Configuration ==


The configuration tab allows to define additional custom protocols. Based on IP addresses or subnets or port ranges, up to 128 different custom protocols may be defined which are shown as regular layer 7 protocols in the statistics described in the previous sections.
The configuration tab allows to define additional custom protocols. Based on IP addresses or subnets or port ranges, up to 128 different custom protocols may be defined which are shown as regular layer 7 protocols in the statistics described in the previous sections.
Line 88: Line 85:


* Name: this is the identifier used in all statistics and layer 7 specific filters. An unique name must be chosen.
* Name: this is the identifier used in all statistics and layer 7 specific filters. An unique name must be chosen.
* Description: the description is purely informational and is shown in the detailed statistics for that protocol.
* Description: the description is purely informational and is shown in the detailed statistics for that protocol. This field can be used for a detailed description what kind of traffic the protocol covers.
:This field can be used for a detailed description what kind of traffic the protocol covers.
* Layer 4 protocol: The protocol may match any IP traffic but also can be limited to just TCP or UDP traffic. For performance it is recommended to choose either option if this is applicable as only part of the traffic need to be checked against the other matching rules.
* Layer 4 protocol: The protocol may match any IP traffic but also can be limited to just TCP or UDP traffic.
* IPs: An IP address can be entered or a subnet using the subnet size parameter. The source and destination IP address of a network packet is used to match the list of IP addresses.  
:For performance it is recommended to choose either option if this is applicable as only part of the traffic need to be checked against the other matching rules.
* IPs: An IP address can be entered or a subnet using the subnet size parameter.  
:The source and destination IP address of a network packet is used to match the list of IP addresses.  
 
:Example values are:
:Example values are:
:– 1.2.3.4
:* 1.2.3.4
 
::meaning exactly the IP 1.2.3.4
:meaning exactly the IP 1.2.3.4
:* 1.2.3.0/24
:– 1.2.3.0/24
::this matches any IP between 1.2.3.0 and 1.2.3.255
 
:this matches any IP between 1.2.3.0 and 1.2.3.255
:It is possible to use IPv4 or IPv6 addresses.
:It is possible to use IPv4 or IPv6 addresses.
:Up to 16 IP addresses may be used so that at least one item on the list must match.
:Up to 16 IP addresses may be used so that at least one item on the list must match.
* Ports: TCP or UDP ports may be used to match traffic. The source and the destination port is used to match the list of ports. Individual ports or port ranges can be used.  
* Ports: TCP or UDP ports may be used to match traffic. The source and the destination port is used to match the list of ports. Individual ports or port ranges can be used.  
:Example values are:
:Example values are:
:– 80
:* 80
 
::meaning exactly port 80
:meaning exactly port 80
:* 100-200
:– 100-200
::matches any port between 100 and 200
 
:matches any port between 100 and 200
:Up to 16 ports or port ranges may be defined.
:Up to 16 ports or port ranges may be defined.


Line 121: Line 108:




'''Web interface'''
=== Web interface ===


The following actions are possible in the configuration tab:
The following actions are possible in the configuration tab:
Ralf
546

edits

Retrieved from "https://allegro-packets.com/wiki/Special:MobileDiff/2634"

Navigation menu