witch without assigning its ports to specific VLANs, all the devices will be in VLAN 1. Port 8 Port 9 Port 10 Port 11 Port 12 Port 13 Port 14 Port 15 VLAN 20 VLAN 30 VLAN 40 VLAN 10 VLAN 10 VLAN 20 Port 0 Port 1 Port 2 Port 3 Port 4 Port 5 Port 6 Port 7 Figure 4-1. VLANs on a switch Frames cannot leave the VLANs from which they originate. This means that in the example configuration, Jack can communicate with Jill, and Bill can communicate with Ted, but Bill and Ted cannot communicate with Jack or Jill in any way. For a packet on a layer-2 switch to cross from one VLAN to another, an outside router must be attached to each of the VLANs to be routed. Figure 4-2 shows an external router connecting VLAN 20 with VLAN 40. Assuming a proper configuration on the router, Bill will now be able to communicate with Jill, but neither workstation will show any indication that they reside on the same physical switch. Port 8 Port 9 Port 10 Port 11 Port 12 Port 13 Port 14 Port 15 VLAN 20 VLAN 30 VLAN 40 VLAN 10 VLAN 10 VLAN 20 Port 0 Port 1 Port 2 Port 3 Port 4 Port 5 Port 6 Port 7 Figure 4-2. External routing between VLANs When expanding a network using VLANs, the same limitations apply. If you con- nect another switch to a port that is configured for VLAN 20, the new switch will be able to forward frames only to or from VLAN 20. If you wanted to connect two switches, each containing four VLANs, you would need four links between the switches: one for each VLAN. A solution to this problem is to deploy trunks between switches. Trunks are links that carry frames for more than one VLAN. Figure 4-3 shows two switches connected with a trunk. Jack is connected to VLAN 20 on Switch B, and Diane is connected to VLAN 20 on Switch A. Because there is a trunk connecting these two switches together, assuming the trunk is allowed to carry traffic for all configured VLANs, Jack will be able to communicate with Diane. Notice that the ports to which the trunk is connected are not assigned VLANs. These ports are trunk ports, and as such, do not 