> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/detection-models/library/informational/ip_options_abuse.md).

# ip\_options\_abuse

Explanation This Netography Fusion Portal event looks for ICMP messages of type 12 (Parameter Problem). Routers will emit these messages when they receive a malformed packet that they cannot route. Th

**Explanation**

This Netography Fusion Portal event looks for ICMP messages of type 12 (Parameter Problem). Routers will emit these messages when they receive a malformed packet that they cannot route. The presence of these messages usually indicates a networking problem, although in some circumstances the presence of these messages could be an indicator of malicious activity.

**What to Look For**

The source address of associated flows will be the IP of the networking device that emitted the ICMP message. The destination address will be the source address of the malformed packet that the networking device received. Examine network connectivity between the source and destination for connectivity issues, and examine the system at the destination address for configuration or security problems.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fusion.vectra.ai/detection-models/library/informational/ip_options_abuse.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
