The type of packet error that caused us to perceive this as an attack.
1 - SKIP header error. e.g. this packet was not IPSec AH or IPSec ESP.
2 - SKIP Counter N error. Not currently (1/9/98) supported.
3 - SKIP Algorithm mismatch. The parameters of the VPN that this
packet belongs to does not match the VPN parameters in the SKIP
header.
4 - SKIP Authentication error. The authentication key in the offending
packet was not correct. This type of attack results in an authFailure
trap which shows up on the VPNmanager as Invalid Authentication Signature.
5 - SKIP Authentication Header error. Not supported.
6 - SKIP Encryption Header error. The packet's ESP trailer wasn't correct.
1 - SKIP header error. e.g. this packet was not IPSec AH or IPSec ESP.
2 - SKIP Counter N error. Not currently (1/9/98) supported.
3 - SKIP Algorithm mismatch. The parameters of the VPN that this
packet belongs to does not match the VPN parameters in the SKIP
header.
4 - SKIP Authentication error. The authentication key in the offending
packet was not correct. This type of attack results in an authFailure
trap which shows up on the VPNmanager as Invalid Authentication Signature.
5 - SKIP Authentication Header error. Not supported.
6 - SKIP Encryption Header error. The packet's ESP trailer wasn't correct.
Sources for this description
MIBdepot
Source file: Download vpnet.mib.txt
Related source files and packages:
Source data warning: The published IMPORTS clause omits the import of enterprises. A SHA-reviewed lookup uses an independent archived module with an explicit RFC1155-SMI import, original RFC 1155 namespace definitions and the official IANA PEN 1866 registration. Published names, imports and definitions are preserved; all supporting originals are available below.
Source data warning: The published file uses lowercase ASN.1 type identifiers. The reviewed grammar preserves their exact names, all OID assignments and every original source byte; no type or value is renamed.