Wanguard 6.2 User Guide
Configuration » Components » Packet Sensor
Packet Sensor Troubleshooting
✔
Look for warnings or errors produced by the Packet Sensor in the event log (details on page 69).
✔
Ensure that you have correctly configured the Packet Sensor. Each configuration field is described in
depth in this chapter.
✔
The event log error “
License key not compatible with the existing server”
can be fixed by sending the
string from Configuration » Servers » [Packet Sensor server] » Hardware Key to sales@andrisoft.com.
✔
Make sure that the sniffing interface is up:
ip link show <interface_usually_eth1_or_p1p2>
✔
Ensure that you have correctly configured the switch/TAP to send packets to the server on the
configured interface.
✔
Verify whether the server is receiving packets through the configured interface:
tcpdump -i <interface_usually_eth1_or_p1p2> -n -c 100
✔
When
IP Validation
is not disabled, make sure that the selected IP Zone contains all your subnets.
✔
If the CPU usage of the Packet Sensor is too high, set the
Top Generator
parameter to “Basic”, install
PF_RING or Netmap to enable multi-threading, or use a network adapter that allows distributing Packet
Sensors over multiple CPU cores.
✔
To troubleshoot Sensor graph or IP graph issues, follow the Graphs Troubleshooting guide from page 22.
✔
For PF_RING-related issues, contact ntop.org. To increase the maximum number of PF_RING programs
from 64 to 256, increase the MAX_NUM_RING_SOCKETS defined in kernel/linux/pf_ring.h and
recompile the pf_ring kernel module.
✔
Make sure you are running the latest version of the software.
- 41 -
Summary of Contents for wanguard 6.2
Page 1: ......