User`s guide

LOC-SYN-SND Local TCP Traffic A Local-Out TCP session is initiated by
sending a SYN packet.
LOC-SYN-RCV Local TCP Traffic A Local-In TCP session is initiated by
receiving a SYN packet.
LOC-FIN-WAIT1 Local TCP Traffic An established local TCP session started the
close process by sending a FIN packet.
LOC-FIN-WAIT2 Local TCP Traffic A local TCP session in the FIN-WAIT1 state
received an ACK for the FIN packet.
LOC-TIME-WAIT Local TCP Traffic A local TCP session in the FIN-WAIT1 or in
the FIN-WAIT2 state received a FIN packet.
LOC-CLOSE Local TCP Traffic An established local TCP session is closed.
LOC-CLOSE-WAIT Local TCP Traffic An established local TCP session received a
FIN packet.
LOC-LAST-ACK Local TCP Traffic Application holding an established TCP
socket responded to a received FIN by
closing the socket. A FIN is sent in return.
LOC-LISTEN Local TCP Traffic A local socket awaits connection request
(SYN packets).
LOC-CLOSING Local TCP Traffic A local socket in the FIN_WAIT1 state
received a FIN packet.
LOC-FINISH Local TCP Traffic A local TCP socket was removed from the
internal socket list.
Viewing Logs
From the tab, there are a number of log files that you can view to monitor and troubleshoot the Barracuda Firewall:LOGS
Firewall Log
HTTP Log
Network Log
VPN Log
Service Log
Authentication Log
HTTP Log Codes Overview
TCP Codes
ERR Codes
For all of these logs, click for a description of the information on the page.Help
Firewall Log
The Firewall Log displays firewall activity such as rules that have been executed and traffic that has been dropped. It lists all connections on the
Barracuda Firewall. You can filter the log by criteria such as a source IP address or network, or the time that the connections occurred.
HTTP Log
The HTTP Log displays the activities of the Barracuda Firewall's HTTP proxy. There are several codes in the log. For details on these codes, see
the section.HTTP Log Codes Overview
Network Log
Use the Network Log to investigate why network configuration changes are not working properly or cannot be activated.
The messages in the Network Log might explain the problem. If not, check the network configuration again for any problems or conflicts.