> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/python/vm-autoscaling/models/nicfirewallrule.md).

# NicFirewallRule

## Properties

| Name                   | Type    | Description                                                                                                                                                                          | Notes       |
| ---------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------- |
| **name**               | **str** | The name of the firewall rule.                                                                                                                                                       | \[optional] |
| **protocol**           | **str** | The protocol for the rule. The property cannot be modified after its creation (not allowed in update requests).                                                                      |             |
| **source\_mac**        | **str** | Only traffic originating from the respective MAC address is permitted. Valid format: 'aa:bb:cc:dd:ee:ff'. The value 'null' allows traffic from any MAC address.                      | \[optional] |
| **source\_ip**         | **str** | Only traffic originating from the respective IPv4 address is permitted. The value 'null' allows traffic from any IP address.                                                         | \[optional] |
| **target\_ip**         | **str** | If the target NIC has multiple IP addresses, only the traffic directed to the respective IP address of the NIC is allowed. The value 'null' allows traffic to any target IP address. | \[optional] |
| **icmp\_code**         | **int** | Sets the allowed code (from 0 to 254) when ICMP protocol is selected. The value 'null'' allows all codes.                                                                            | \[optional] |
| **icmp\_type**         | **int** | Sets the allowed type (from 0 to 254) if the protocol ICMP is selected. The value 'null' allows all types.                                                                           | \[optional] |
| **port\_range\_start** | **int** | Sets the initial range of the allowed port (from 1 to 65535) if the protocol TCP or UDP is selected. The value 'null' for 'portRangeStart' and 'portRangeEnd' allows all ports.      | \[optional] |
| **port\_range\_end**   | **int** | Sets the end range of the allowed port (from 1 to 65535) if the protocol TCP or UDP is selected. The value 'null' for 'portRangeStart' and 'portRangeEnd' allows all ports.          | \[optional] |
| **type**               | **str** | The firewall rule type. If not specified, the default value 'INGRESS' is used.                                                                                                       | \[optional] |


---

# 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.ionos.com/cloud/python/vm-autoscaling/models/nicfirewallrule.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.