# NicProperties ## Properties | Name | Type | Description | Notes | | ------------------ | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | | **deviceNumber** | **number** | The Logical Unit Number (LUN) of the storage volume. Null if this NIC was created using Cloud API and no DCD changes were performed on the Datacenter. | \[optional] \[readonly] \[default to undefined] | | **dhcp** | **boolean** | Indicates if the NIC will reserve an IP using DHCP. | \[optional] \[default to true] | | **dhcpv6** | **boolean** | Indicates if the NIC will receive an IPv6 using DHCP. It can be set to 'true' or 'false' only if this NIC is connected to an IPv6 enabled LAN. | \[optional] \[default to undefined] | | **firewallActive** | **boolean** | Activate or deactivate the firewall. By default, an active firewall without any defined rules will block all incoming network traffic except for the firewall rules that explicitly allows certain protocols, IP addresses and ports. | \[optional] \[default to undefined] | | **firewallType** | **string** | The type of firewall rules that will be allowed on the NIC. If not specified, the default INGRESS value is used. | \[optional] \[default to undefined] | | **ips** | **Array\** | Collection of IP addresses, assigned to the NIC. Explicitly assigned public IPs need to come from reserved IP blocks. Passing value null or empty array will assign an IP address automatically. | \[optional] \[default to undefined] | | **ipv6CidrBlock** | **string** | If this NIC is connected to an IPv6 enabled LAN then this property contains the /80 IPv6 CIDR block of the NIC. If you leave this property 'null' when adding a NIC to an IPv6-enabled LAN, then an IPv6 CIDR block will automatically be assigned to the NIC, but you can also specify an /80 IPv6 CIDR block for the NIC on your own, which must be inside the /64 IPv6 CIDR block of the LAN and unique. This value can only be set, if the LAN already has an IPv6 CIDR block assigned. An IPv6-enabled LAN is limited to a maximum of 65,536 NICs. | \[optional] \[default to undefined] | | **ipv6Ips** | **Array\** | If this NIC is connected to an IPv6 enabled LAN then this property contains the IPv6 IP addresses of the NIC. The maximum number of IPv6 IP addresses per NIC is 50, if you need more, contact support. If you leave this property 'null' when adding a NIC, when changing the NIC's IPv6 CIDR block, when changing the LAN's IPv6 CIDR block or when moving the NIC to a different IPv6 enabled LAN, then we will automatically assign the same number of IPv6 addresses which you had before from the NICs new CIDR block. If you leave this property 'null' while not changing the CIDR block, the IPv6 IP addresses won't be changed either. You can also provide your own self choosen IPv6 addresses, which then must be inside the IPv6 CIDR block of this NIC. | \[optional] \[default to undefined] | | **lan** | **number** | The LAN ID the NIC will be on. If the LAN ID does not exist, it will be implicitly created. | \[default to undefined] | | **mac** | **string** | The MAC address of the NIC. | \[optional] \[readonly] \[default to undefined] | | **name** | **string** | The name of the resource. | \[optional] \[default to undefined] | | **pciSlot** | **number** | The PCI slot number for the NIC. | \[optional] \[readonly] \[default to undefined] | --- # Agent Instructions: 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: ``` GET https://docs.ionos.com/nodejs-sdk/models/nicproperties.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.