Troubleshooting guide

Appendix A: State Tables for VPN-1/FireWall-1 4.0 Specific services tables
Advanced Technical Reference Guide 4.1 • June 2000 168
Example
attributes: refresh, expires 900
<c073cd1f, 000005e3, c7cb47c6, 000006bf, 000000006;
The h323_tracer_table table uses the following format:
<source IP address, source port, destination IP address, destination port, IP protocol; expecting, data length,
direction; time left/total time>
The data length field is the length of the data in bytes. The direction field is either 0 (incoming) or 1 (outgoing).
The expecting field is interpreted using the following table:
Expecting value Description
1 AL_EXPECT_INITIAL_HEADER
2 AL_EXPECT_HEADER
3 AL_EXPECT_MSG
4 AL_IN_HEADER
5 AL_IN_MSG
6 AL_IN_INITIAL_HEADER
7 AL_OUT_OF_SYNC
wf_connections table
The wf_connections table holds a list of win-frame connections (win-frame is a x-server for windows). This
table is similar to the “pending” tables but holds only win-frame related information.
Example
attributes: refresh, expires 3600, sync
<c0a81f01, 00000684, c073cd85, 000005d6, 00000001; 0005a594; 3599/3600>
The wf_connections table uses the following format:
<source IP address, source port, destination IP address, destination port, IP protocol, connection direction;
sequence number; time left/total time>
The connection direction field is either 1 (for a connection from the client to the win-frame server) or 2 (for a
connection from the server to the client). The sequence number field is the sequence number of the first packet
in each direction. (client to server or server to client)
rtsp_tab table
The rtsp_tab table saves data regarding the RealTime Streaming Protocol (used by RealAudio).
Example
attributes: refresh sync expires 60
<c073cd2c, 0000057e, c0a80c01, 0000022a, 00000006; 0000061f; 53/60>
The rtsp_tab table uses the following format:
<source IP address, source port, destination IP address, destination port, IP protocol; UDP client port; time
left/total time>