> For the complete documentation index, see [llms.txt](https://docs.onum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onum.com/the-workspace/pipelines/actions/transformation/field-transformation/field-transformation-operations/networking/fang-ip-address.md).

# Fang IP address

## Description

This operation takes an invalid IPv4 or IPv6 address and 'fangs' it, meaning the IP becomes valid.

***

## Data types

These are the input/output expected data types for this operation:

### Input data

![](/files/lPHCVhp93aYrWgLIlhNp) - IP addresses you want to fang.

{% hint style="info" %}
**Input format**

The input IP addresses must follow the format given in the output results of the [Defang IP Address](/the-workspace/pipelines/actions/transformation/field-transformation/field-transformation-operations/networking/defang-ip-address.md) operation, that is, dots replaced by brackets (for example, `192[.]168[.]1[.]1`)
{% endhint %}

### Output data

![](/files/3itBmKrRqasWlG3dGBlS) - Valid IP addresses.

***

## Example

Suppose you want to **fang** a series of events that represent **IP addresses**:

1. In your Pipeline, open the required [Action](/the-workspace/pipelines/actions.md) configuration and select the input **Field**.
2. In the **Operation** field, choose **Fang IP Address**.
3. Give your **Output field** a name and click **Save**. The IP addresses in your input field will be made valid. For example:

```
Input data - "192[.]168[.]1[.]1"

Output data - "192.168.1.1"
```

{% hint style="info" %}
You can try out operations with specific values using the **Input** field above the operation. You can enter the value in the example above and check the result in the **Output** field.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.onum.com/the-workspace/pipelines/actions/transformation/field-transformation/field-transformation-operations/networking/fang-ip-address.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.