The Layer 4 page shows active hosts and the connections between them.
Topics:
- What controls are available on the map?
- How do I get detailed information on a device?
- How do I create a filter to select specific flows?
- To zoom in, use mouse wheel or use the slider control on the bottom left of the screen.
- To zoom out again, use mouse wheel or use the slider control on the bottom left of the screen.
- To pan, click on the map background, hold down left mouse button and drag. Alternatively, use the arrow controls on the bottom left of the screen, or drag the view port in the overview on the top left of the screen.
- = equals
- != not equals
- ~ matches a reqular expression
- !~ does not match a regular expression
- & boolean AND
- | boolean OR
- ipsource = 10.1.1.23
- ipdestination != 10.0.0.0/24,10.0.1.0/24
- serverport = TCP:80,TCP:81,TCP:8080-8088
- sourcezone ~ research.*
- ipsource = 10.0.0.1 & ipdestination = 10.0.0.2
- ipsource = 10.0.0.1 & (sourceport = TCP:80 | destinationport = TCP:80)
- sourcezone = EXTERNAL | destinationzone = EXTERNAL
- serverzone = "Research & Development", Sales
- clientzone = 'Research & Development'
- sourcezone = Research\ \&\ Development
- serverpath = ">>Research & Development>Data Center"
What controls are available on the map?
The following operations are supported on the map:
How do I get detailed information on a device?
Hovering over an item in the map will cause it to expand to show additional information. Underlined labels on lines and nodes are links to search for additional information on the item (see Sentinel:Search>Host, Sentinel:Search>Agent/Interface and Sentinel:Search>Protocol )
How do I create a filter to select specific flows?
Change the Protocol: setting to show only links related to the selected protocol, or set to All to show all protocols. Alternatively, click on a protocol node in the map to filter on the procol.
Click on a host in the map to show only that host and its neighbors. Click on the Reset Map button to show all hosts.
The Where box is used to filter traffic queries so that only selected traffic is shown. A filter expression can be entered directly into the input box. Clicking on the OK button applies the filter. Clicking on the Clear button will remove the filter.
An easier way to construct filters is to click on the Edit button to display additional inputs used to construct the filter expression. The first input consists of a selection box containing attributes that can be compared, a selection box containing comparison operators and an input area to specify that values to be compared to the selected attribute. Clicking the Add button appends the comparison to the current filter. There are also boolean operator buttons (& and |) and bracket buttons that can be used to combine comparison expressions to form more complex filters. The filter builder only enables buttons and inputs when they are allowed in the filter expression that is being constructed. Once the desired filter has been constructed, click on the OK button to apply it.
Note: If you just want to filter on a Host or Protocol then it is easier to set the Host and Protocol options in the Filter bar, rather than constructing a Where filter.
A basic filter expression consists of the name of an attribute, an operator and a set of comma separated values. The allowed operators are:
Expressions can be combined using brackets and the boolean operators:
The following examples illustrate typical where filters:
Note: The special zone EXTERNAL refers to addresses that aren't contained in any of the CIDRs specified using File > Configure.
WARNING Care should be taken if a value in a filter expression contains any of the following special characters: (, ), &, |, !, =, ~, ",', \, comma or space. If the value contains any of these characters then the whole value string can be enclosed in single or double quotes, or the special characters can be individually escaped with a \. The following examples show different ways of using the value "Research & Development" in filters:
Note: Special characters typically occur because they are used in Zone or Group names when configuring Traffic Sentinel (see File>Configure). Care should be taken when filtering on zone, group or path attributes.