@akamai/openapi-ts
    Preparing search index...

    Variable getLinodeConfigInterfacesResponseSchemaConst

    getLinodeConfigInterfacesResponseSchema: ZodArray<
        ZodObject<
            {
                active: ZodOptional<ZodReadonly<ZodBoolean>>;
                id: ZodOptional<ZodReadonly<ZodInt>>;
                ip_ranges: ZodOptional<ZodUnion<readonly [ZodArray<ZodString>, ZodNull]>>;
                ipam_address: ZodOptional<ZodUnion<readonly [ZodString, ZodNull]>>;
                ipv4: ZodOptional<
                    ZodObject<
                        {
                            nat_1_1: ZodUnion<
                                readonly [ZodString, ZodEnum<{ any: "any" }>, ZodNull],
                            >;
                            vpc: ZodUnion<readonly [ZodString, ZodNull]>;
                        },
                        $strip,
                    >,
                >;
                label: ZodOptional<ZodUnion<readonly [ZodString, ZodNull]>>;
                primary: ZodOptional<ZodBoolean>;
                purpose: ZodEnum<{ public: "public"; vlan: "vlan"; vpc: "vpc" }>;
                subnet_id: ZodOptional<ZodUnion<readonly [ZodInt, ZodNull]>>;
                vpc_id: ZodOptional<
                    ZodReadonly<ZodUnion<readonly [ZodReadonly<ZodInt>, ZodNull]>>,
                >;
            },
            $strip,
        >,
    > = ...

    interfaces is applicable only to legacy configuration profiles and does not apply to Linode interfaces.

    From one to three network interfaces to add to this Linode's configuration profile. The position in the array determines which of the Linode's network interfaces is configured:

    • First [0]: eth0
    • Second [1]: eth1
    • Third [2]: eth2

    When updating a Linode's legacy interfaces, each interface must be redefined. An empty interfaces array results in a default public type interface configuration only.

    If no public Interface is configured, public IP addresses are still assigned to the Linode but will not be usable without manual configuration.

    📘

    Changes to Linode Interface configurations can be enabled by rebooting the Linode.

    vpc details

    See the VPC documentation guide for its specifications and limitations.

    vlan details

    • Only Next Generation Network (NGN) data centers support VLANs. Run the List regions operation to view the capabilities of data center regions. If a VLAN is attached to your Linode and you attempt to migrate or clone it to a non-NGN data center, the migration or cloning will not initiate. If a Linode cannot be migrated or cloned because of an incompatibility, you will be prompted to select a different data center or contact support.
    • See the VLANs Overview guide to view additional specifications and limitations.

    Settings

    Member Visibility