CloudLabBox
Try the free demo

Linux for network engineers lab 3 of 14

VLAN interfaces, bridges and bonds

You connect a Linux box to a real switch with an LACP bond, carry two VLANs over it, route between them and bridge a new PC into one. Then you pull a link.

Run this lab

It needs Lite: its 5 nodes are set to 5 vCPU and 2,816 MB in total. That fits the free demo too.

In your workspace: Shared, then Linux for network engineers guided labs, then 03 - VLAN interfaces bridges and bonds

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 70 minutes
Nodes need
5 vCPU, 2,816 MB
Smallest plan
Lite

The scenario

Kestrel's York depot uses LNX1 as its router. Two cables run to switch SW1, and the team wants them bonded with LACP so a cable fault doesn't stop the depot. Drivers are in VLAN 10 and the office is in VLAN 20. There's no free switch port for the new PC, H3, so it plugs straight into LNX1, and it still has to sit in VLAN 20.

DeviceInterfaceAddressRole
H1eth010.3.10.10/24VLAN 10, access port Gi0/2
H2eth010.3.20.20/24VLAN 20, access port Gi0/3
H3eth010.3.20.30/24VLAN 20, through LNX1's bridge
LNX1bond0.1010.3.10.1/24VLAN 10 gateway
LNX1bond0.20, then br2010.3.20.1/24VLAN 20 gateway
SW1Po1 (Gi0/0, Gi0/1)trunk: VLANs 10, 20, LACP active
DeviceRunsHow to log in
H1, H2, H3Alpine Linux 3.20root, no password.
SW1Cisco IOSvL2The console opens at >; enable has no password.
LNX1Alpine Linux 3.16 with iptables and iproute2Opens on a menu: press 5, then Enter, for a root shell.

What you’ll practise

  • Build an 802.3ad bond and match it to an IOS port channel
  • Create 802.1Q VLAN interfaces on a bond
  • Route between VLANs on Linux
  • Build a Linux bridge and move an address on to it
  • Test link failure and read the bond state

The tasks

  1. Start the Linux nodes
  2. Build the bond
  3. Add VLAN interfaces
  4. Route between the VLANs
  5. Bridge a new PC into VLAN 20
  6. Fail a link

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of VLAN interfaces bridges and bonds5 nodes, 5 links. Every link is listed as text below the diagram.H1H2H3SW1LNX1eth2eth0Gi0/0eth0Gi0/1eth1Gi0/2eth0Gi0/3eth0
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • SW1 Gi0/0 to LNX1 eth0
  • SW1 Gi0/1 to LNX1 eth1
  • SW1 Gi0/2 to H1 eth0
  • SW1 Gi0/3 to H2 eth0
  • LNX1 eth2 to H3 eth0
Nodes in VLAN interfaces, bridges and bonds, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
H1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
H2Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
H3Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
SW1Cisco IOSvL2viosl2-adventerprisek9-m.ssa.high_iron_202009291 vCPU, 768 MB
LNX1Alpine WAN emulatorclbalpinewanem-alpine-3-16-2-wanem1 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder Linux for network engineers guided labs.

  3. Open 03 - VLAN interfaces bridges and bonds and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More Linux for network engineers labs

All Linux for network engineers labs

Related labs in other courses

CloudLabBox is independent of Cisco, CompTIA, the Linux Foundation and the Linux Professional Institute. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.