Within Cloud Manager, VLANs are created and managed only by attaching them to Linodes. They are not managed independently. You can attach a VLAN when creating a new Linode or when editing an existing Linode.

• Attaching a VLAN When Creating a Linode
• Attaching a VLAN to an Existing Linode

This guide covers implementing both of these methods using Cloud Manager.

Attaching a VLAN when creating a Linode

1. On the top left of Cloud Manager, click Create and select Linode.

2. Fill out all desired configuration options in the form that appears, until reaching the Networking section. See the Creating a Linode guide for more information.

   📘

   VLANs are not available in all regions. If the Attach a VLAN section isn't visible, see the Availability section on the VLANs Overview page.

3. Within the Network Connection section, select VLAN.

4. If the VLAN already exists, it can be selected from the drop down list. If the VLAN doesn't yet exist,enter a label, and the VLAN will be created automatically when you create the Linode.

5. Optionally enter the IPv4 address you wish to assign to the VLAN's network interface on this machine. The IP address should be unique to avoid conflicts in the case other machines share the same address. If this field is left blank, the Linode will not be able to communicate with other Linodes on that VLAN until one of the following is true:

   • An IPAM address is added to the eth1 interface within the Linode's Configuration Profile
   • An IP address is manually assigned to the network interface within the Linode's internal configuration files.

   See the Assigning an IPAM Address section on the Get Started guide for more information about IPAM and examples of valid IPAM addresses.

6. Complete the create form with any additional add-ons and settings you'd like to use. Then click the Create Linode button.

By default, the public IP address (and, if added, the private IP address) of the Linode is configured on the eth0 network interface. The VLAN, if one was attached, is configured on the eth1 network interface. Configuration profile network interfaces can be removed or modified by editing the Configuration Profile. You can delete or add Linode interfaces, but you can't modify them. Learn more.

Attaching a VLAN to an existing Linode

1. Within Cloud Manager, click the Linodes link in the sidebar and select a Linode.

2. Follow the steps in the table based on whether your Linode uses configuration profile interfaces or Linode interfaces.

6. Enter the Label of the VLAN or select an existing VLAN from the drop down menu. If a custom label is entered and the VLAN does not yet exist, it is automatically created.

7. Optionally enter an IP (IPAM) Address. If this field is left blank, the Linode will not be able to communicate with other Linodes on that VLAN until an IP address is manually assigned to the network interface within the Linode's internal configuration files.

   See the Assigning an IPAM Address section of the Get Started guide for more information about IPAM and examples of valid IPAM addresses.

8. Follow the steps in the table based on whether your Linode uses configuration profile interfaces or Linode interfaces.

Testing connectivity

Once a VLAN has been attached to more than one Linode, verify that you can communicate between those Linodes over the VLAN's private network.

1. If the Linode has a public network configured, connect to it via SSH. See Setting Up and Securing a Linode > Connect to the Linode.

   ssh username@192.0.2.1
   

   If the Linode does not have a public network configured, connect to it via Lish by following the steps in the Using the Lish Console guide.

2. Ping another Linode within the VLAN's private network using the IPAM address assigned to it.

   ping 10.0.0.1
   

   The output should display ICMP packets successfully transmitted and received from this Linode to the secondary Linode in the private network.

   Output

   PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
   64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.733 ms
   64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.294 ms
   ^C
   --- 10.0.0.1 ping statistics ---
   2 packets transmitted, 2 received, 0% packet loss, time 18ms
   rtt min/avg/max/mdev = 0.294/0.513/0.733/0.220 ms