ECHO: No Response From Server
This protocol anomaly triggers when it detects excessive ECHO client-to-server data that the server does not reply to. This can indicate a hung server or data tunneling over ECHO packets.
Extended Description
The presence of multiple client to Echo server transmissions with no response could indicate a network configuration error, a tunneling attempt, or an Echo server crash..
References
srx-branch-12.3
srx-19.3
srx-branch-19.3
vsrx3bsd-19.2
srx-branch-19.4
vsrx-19.4
mx-12.3
mx-19.4
vmx-19.4
mx-19.3
vsrx3bsd-19.4
srx-19.4
vsrx-12.3
vmx-19.3
vsrx-19.2
srx-12.3