|
4.1.2 General Network Capture ( Ethernet, protocol independent ) |
|
LIAN 98 is able to record all the data packets on the ethernet,
provided the data are available on the LAN interface of the PC running LIAN 98. This means that the PC has to be
connected direct to the same network hub as the network client ( master ) without using a switch or router. |
Structure of network frames |
|
|
|
Information about the structure of network frames see |
|
The PC must be connected to the network hub or switch before LIAN 98 will be started, otherwise
parametrization of the network in LIAN can not be done. |
![]() |
|
With the channel button ( channel 1 ...12 ) on the bottom following settings are possible : |
Local machine |
| Network adapter |
If there are several network adapters in the PC the corresponding adapter for the test must to be selected here. |
| Network protocol |
Here the protocol is not used for network capture. |
| Host name |
The name of the PC declared during the network installation is displayed here. ( No input is possible, it is only a display field. ) |
| IP address |
The IP-address allocated to the network adapter is displayed here. It can be set via
the network settings in the Windows system control. ( No input is possible, it is only a display field ! ) |
| Port number |
This port number is not used for network capture. |
Remote machine |
| Port number |
This port number is not used for network capture. |
Receiving/ Capture |
| ( Read- ) Timeout |
Recommendation : 100 msec |
|
|
![]() |
| Ethernet ( length- ) type field |
0800H ( variable ) |
| IP version |
4 or 6 ( variable ) |
| Protocol |
6 ( variable ) |
| IP address client |
IP address of the client ( Master station ). The network traffic between
this client and the server(s) will be recorded. The required stations must be indicated in the server list
and the PC must be connected with the client over the same network hub. |
| IP address server ( input field ) |
Use this field to enter the IP addresses of the servers in the server list. |
| Port number server ( input field ) |
Use this field to enter the port numbers of servers in the server list. |
|
Insert server addresses number of addresses delete insert |
Each particular server to be captured
must be inserted in the server list. LIAN 98 will use this list
to prefilter the network traffic. If no server address is inserted all
IP addresses will be captured. |
|
Monitoring filters reduce capture on particular pre-defined data records. By setting the corresponding filters a carefully directed data preselection can be achieved, which results in a reduction of the data to be analyzed later. |
![]() |
Filter released |
yes / no |
||||||||||
protocol specific filter mask |
Here monitoring can be filtered for telegram specific values in which several OR-linked filter masks can be defined for the channel.
|
||||||||||
| add | Add the next OR-element. | ||||||||||
| remove | Remove the current OR-element. |
|
With the receipt of a telegram pre-defined as start trigger, recording is started. |
![]() |
Start trigger released |
yes / no |
||||||||||
protocol specific |
Here you can define telegram specific start triggers for monitoring in which several OR-linked triggers can be defined for the channel.
|
||||||||||
| add | Adds the next OR-element. | ||||||||||
| remove | Removes the current OR-element. |
|
Monitoring can also be stopped by telegram-specific filters and/ or "stop on error" after a defined number of following records. The number of the following records is defined in the field "records after stop on error/ stop trigger" in the global parameters of the VFL settings. |
![]() |
Stop trigger released |
yes / no |
||||||||||
protocol specific |
Here you can define telegram specific stop triggers for monitoring in which several OR-linked triggers can be defined for the channel.
|
||||||||||
| add | Adds the next OR-element. | ||||||||||
| remove | Removes the current OR-element. |
|
Each alteration in the settings is displayed by an asterisk * in the caption title and will be only effective after saving. |
|
The received messages of all channels are entered binary into the archive file.
Before displaying on screen, the binary archived data are coverted to an easily readable procedure specific plaintext.
In order to optimize the representation it can be chosen between five different plaintext settings. The plaintext format
is set separately for each channel. |
![]() |
|
The screen shot above shows the network headers ( MAC-, IP-, TCP header ) and the user data of the transmission block.
The display format can be set via FMT file - Display format.
The output of each header can be suppressed, of course. |
|
Because the user data of the the general network capture are not known, no plain text display is provided and therefore the different plaintext settings are ineffective. |
| Plaintext format | |
| Format 1, 2, 3, 4, 5 |
Not used and therefore without effect |
Error checks during receive |
| per network packet |
the length of the particular headers. |
| *E: NET PACKET ! |
The captured length is not equal to the packet length. |
| *E: MAC HEADER ! |
The length of the MAC Header is incorrect or the data packet is not be interpretable. |
| *E: IPv4 HEADER ! |
The length of the IPv4 header is incorrect. |
| *E: TCP HEADER ! |
The length of the TCP header is incorrect. |
| *E: UDP HEADER ! |
The length of the UDP header is incorrect. |
| *E: ICMP HEADER ! |
The length of the ICMP header is incorrect. |
| *E: Length ! |
The frame length is incorrect. Also it could be possible that the length of the MAC, IP or TCP header is wrong. |
|
Wuerzburger Ring 39, D 91056 Erlangen |
LIAN 98 Protocol Router, Simulator and Analyzer © Copyright 2001, 2006, 2011 by MAYOR GmbH. All Rights reserved. |