Legacy Inter-VLAN Routing

In this article we will discuss Legacy Inter-VLAN Routing, will make brief discussion on Legacy Inter-VLAN Routing, In last article we discuss about Introduction to What is Inter-VLAN Routing?

Historically, the first solution for inter-VLAN routing relied on routers with multiple physical interfaces. Each interface had to be connected to a separate network and configured with a distinct subnet.

In this legacy approach, inter-VLAN routing is performed by connecting different physical router interfaces to different physical switch ports. The switch ports connected to the router are placed in access mode and each physical interface is assigned to a different VLAN. Each router interface can then accept traffic from the VLAN associated with the switch interface that it is connected to, and traffic can be routed to the other VLANs connected to the other interfaces.

1. PC1 on VLAN 10 is communicating with PC3 on VLAN 30 through router R1.

2. PC1 and PC3 are on different VLANs and have IPv4 addresses on different subnets.

3. Router R1 has a separate interface configured for each of the VLANs.

4. PC1 sends unicast traffic destined for PC3 to switch S2 on VLAN 10, where it is then forwarded out the trunk interface to switch S1.

5. Switch S1 then forwards the unicast traffic through its interface F0/3 to interface G0/0 on router R1.

6. The router routes the unicast traffic through its interface G0/1, which is connected to VLAN 30.

7. The router forwards the unicast traffic to switch S1 on VLAN 30.

8. Switch S1 then forwards the unicast traffic to switch S2 through the active trunk link, after which switch S2 can then forward the unicast traffic to PC3 on VLAN 30.

In this example, the router was configured with two separate physical interfaces to interact with the different VLANs and perform the routing.

Note: This method of inter-VLAN routing is not efficient and is generally no longer implemented in switched networks. It is shown in this course for explanation purposes only.

Add a Comment

Your email address will not be published. Required fields are marked *