SlideShare a Scribd company logo
5
Most read
6
Most read
14
Most read
Affiliated with GTU
A Open-Ended Problem Report on
VLAN on packet tracer (Mesh topology)
Prepared as a part of the requirements for the subject of
Data Communication and Networking (2171008)
BE IV, Semester VII
(ELECTRONICS AND TELECOMMUNICATION)
Submitted by: -
1. Prasiddh Makadiya 130080112029
2. Apar Trivedi 130080112057
3. Vatsal Bodiwala 140083112002
PROF. Anish Vahora
(Faculty Guide)
PROF. MEHUL B SHAH
(Head of the Department)
Academic year
(2016-2017)
GUJARAT TECHNOLOGICALUNIVERSITY
BIRLA VISHWAKARMA MAHAVIDYALAYA
Virtual Local Area Networks (VLAN):-
In a traditional LAN, workstations are connected to each other by means of a hub or a repeater.
These devices propagate any incoming data throughout the network. However, if two people
attempt to send information at the same time, a collision will occur and all the transmitted data
will be lost. Once the collision has occurred, it will continue to be propagated throughout the
network by hubs and repeaters. The original information will therefore need to be resent after
waiting for the collision to be resolved, thereby incurring a significant wastage of time and
resources. To prevent collisions from traveling through all the workstations in the network, a
bridge or a switch can be used. These devices will not forward collisions, but will allow
broadcasts (to every user in the network) and multicasts (to a pre-specified group of users) to
pass through. A router may be used to prevent broadcasts and multicasts from traveling through
the network.
The workstations, hubs, and repeaters together form a LAN segment. A LAN segment is also
known as a collision domain since collisions remain within the segment. The area within which
broadcasts and multicasts are confined is called a broadcast domain or LAN. Thus a LAN can
consist of one or more LAN segments. Defining broadcast and collision domains in a LAN
depends on how the workstations, hubs, switches, and routers are physically connected together.
This means that everyone on a LAN must be located in the same area (see Figure1).
Figure 1: Physical view of a LAN
VLAN's allow a network manager to logically segment a LAN into different broadcast domains
(see Figure2). Since this is a logical segmentation and not a physical one, workstations do not
have to be physically located together. Users on different floors of the same building, or even in
different buildings can now belong to the same LAN.
Physical View
Logical View
Figure 2: Physical and logical view of a VLAN.
VLAN's also allow broadcast domains to be defined without using routers. Bridging software is
used instead to define which workstations are to be included in the broadcast domain. Routers
would only have to be used to communicate between two VLAN's.
Mesh topology
A network setup where each computer and network device is interconnected with one another,
allowing for most transmissions to be distributed, even if one of the connections go down. This
topology is not commonly used for most computer networks as it is difficult and expensive to
have redundant connection to every computer. However, this topology is commonly used for
wireless networks. Below is a visual example of a simple computer setup on a network using a
mesh topology.
A mesh topology can be a full mesh topology or a partially connected mesh topology.
In a full mesh topology, every computer in the network has a connection to each of the other
computers in that network. The number of connections in this network can be calculated using
the following formula (n is the number of computers in the network): n(n-1)/2
In a partially connected mesh topology, at least two of the computers in the network have
connections to multiple other computers in that network. This is a cheaper way to build a
network that has some redundancy in the event one of the primary computers or connections in
the network were to be down.
Description:-
In this Open-Ended Problem we have design VLAN on Cicso packet Tracer. Switch0, Switch1,
Switch2, Switch3 and Switch4 are connected in mesh topology. Three PCs are connected with
every switch 0-4. In this problem VLAN is design on based on its IP address. If last pair in
dotted decimal formal IP address is odd then it is in VLAN 3 named ‘Odd’. If last pair in dotted
decimal formal IP address is even then it is in VLAN 2 named ‘Even’.
VLAN 2 (Even) VLAN 3 (Odd)
192.168.0.2 192.168.0.1
192.168.0.4 192.168.0.3
192.168.0.6 192.168.0.5
192.168.0.8 192.168.0.7
192.168.0.10 192.168.0.9
192.168.0.12 192.168.0.11
192.168.0.14 192.168.0.13
192.168.0.15
Switch0 Switch1 Switch2 Switch3 Switch4
192.168.0.1 192.168.0.4 192.168.0.7 192.168.0.10 192.168.0.13
192.168.0.2 192.168.0.5 192.168.0.8 192.168.0.11 192.168.0.14
192.168.0.3 192.168.0.6 192.168.0.9 192.168.0.12 192.168.0.15
VLAN on packet tracer (Mesh topology)
Command in switch0 Command Line Interface (CLI) :-
Switch>en
Switch#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#vlan 2
Switch(config-vlan)#name even
Switch(config-vlan)#exit
Switch(config)#vlan 3
Switch(config-vlan)#name odd
Switch(config-vlan)#exit
Switch(config)#interface fa0/1
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 3
Switch(config-if)#exit
Switch(config)#interface fa0/2
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 2
Switch(config-if)#exit
Switch(config)#interface fa0/3
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 3
Switch(config-if)#exit
Switch(config)#end
Switch#
Switch#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#interface fa 0/4
Switch(config-if)#switchport mode trunk
Switch(config-if)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up
Switch>en
Switch#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#interface fa 0/5
Switch(config-if)#switchport mode trunk
Switch(config-if)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up
%LINK-5-CHANGED: Interface FastEthernet0/6, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up
%LINK-5-CHANGED: Interface FastEthernet0/7, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up
Command in switch1 Command Line Interface (CLI) :-
Switch>
Switch>en
Switch#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#vlan 2
Switch(config-vlan)#name even
Switch(config-vlan)#exit
Switch(config)#vlan 3
Switch(config-vlan)#name odd
Switch(config-vlan)#exit
Switch(config)#interface fa 0/1
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 2
Switch(config-if)#exit
Switch(config)#interface fa 0/2
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 3
Switch(config-if)#exit
Switch(config)#interface fa 0/3
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 2
Switch(config-if)#exit
Switch(config)#end
Switch#
%SYS-5-CONFIG_I: Configured from console by console
Switch#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#interface fa 0/4
Switch(config-if)#switchport mode trunk
Switch(config-if)#interface fa 0/4
Switch(config-if)#switchport mode trunk
Switch(config-if)#
%LINK-5-CHANGED: Interface FastEthernet0/5, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up
%LINK-5-CHANGED: Interface FastEthernet0/6, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up
%LINK-5-CHANGED: Interface FastEthernet0/7, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up
Command in switch2 Command Line Interface (CLI)
Switch>en
Switch#
Switch#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#vlan 2
Switch(config-vlan)#name even
Switch(config-vlan)#e
Switch(config)#vlan 3
Switch(config-vlan)#name odd
Switch(config-vlan)#e
Switch(config)#interface fa 0/1
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 3
Switch(config-if)#e
Switch(config)#end
Switch#
%SYS-5-CONFIG_I: Configured from console by console
Switch#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#interface fa 0/2
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 2
Switch(config-if)#e
Switch(config)#
Switch(config)#
Switch(config)#interface fa 0/3
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 3
Switch(config-if)#
Switch(config-if)#e
Switch(config)#
Switch(config)#
Switch(config)#interface fa 0/4
Switch(config-if)#switchport mode trunk
Switch(config-if)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up
%LINK-5-CHANGED: Interface FastEthernet0/5, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up
%LINK-5-CHANGED: Interface FastEthernet0/5, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down
%LINK-5-CHANGED: Interface FastEthernet0/5, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up
%LINK-5-CHANGED: Interface FastEthernet0/6, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up
%LINK-5-CHANGED: Interface FastEthernet0/7, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
Command in switch3 Command Line Interface (CLI)
Switch>en
Switch#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#vlan 2
Switch(config-vlan)#name even
Switch(config-vlan)#e
Switch(config)#vlan 3
Switch(config-vlan)#name odd
Switch(config-vlan)#e
Switch(config)#interface fa 0/1
Switch(config-if)#
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 2
Switch(config-if)#e
Switch(config)#interface fa 0/2
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 3
Switch(config-if)#e
Switch(config)#interface fa 0/3
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 2
Switch(config-if)#e
Switch(config)#interface fa 0/4
Switch(config-if)#switchport mode trunk
Switch(config-if)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up
Switch(config-if)#e
Switch(config)#interface fa 0/5
Switch(config-if)#switchport mode trunk
Switch(config-if)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up
Switch(config-if)#interface fa 0/6
Switch(config-if)#switchport mode trunk
Switch(config-if)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up
Switch(config-if)#interface fa 0/5
Switch(config-if)#switchport mode trunk
Switch(config-if)#e
Switch(config)#interface fa 0/6
Switch(config-if)#switchport mode trunk
Switch(config-if)#e
Switch(config)#interface fa 0/7
Switch(config-if)#switchport mode trunk
Switch(config-if)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
Command in switch4 Command Line Interface (CLI)
Switch>
Switch>en
Switch#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#vlan 2
Switch(config-vlan)#name even
Switch(config-vlan)#e
Switch(config)#vlan 3
Switch(config-vlan)#name odd
Switch(config-vlan)#e
Switch(config)#interface fa 0/1
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 3
Switch(config-if)#e
Switch(config)#interface fa 0/2
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 2
Switch(config-if)#e
Switch(config)#interface fa 0/3
Switch(config-if)#switchport mode access
Switch(config-if)#switchport access vlan 3
Switch(config-if)#e
Switch(config)#interface fa 0/4
Switch(config-if)#switchport mode trunk
Switch(config-if)#e
Switch(config)#interface fa 0/5
Switch(config-if)#switchport mode trunk
Switch(config-if)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up
Switch(config-if)#e
Switch(config)#interface fa 0/6
Switch(config-if)#switchport mode trunk
Switch(config-if)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up
Switch(config-if)#e
Switch(config)#
Switch(config)#interface fa 0/7
Switch(config-if)#switchport mode trunk
Switch(config-if)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
OUTPUT :-
Packet Tracer PC Command Line 1.0
PC>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=128
Reply from 192.168.0.1: bytes=32 time=0ms TTL=128
Reply from 192.168.0.1: bytes=32 time=20ms TTL=128
Reply from 192.168.0.1: bytes=32 time=0ms TTL=128
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 20ms, Average = 5ms
PC>ping 192.168.0.2
Pinging 192.168.0.2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
PC>ping 192.168.0.3
Pinging 192.168.0.3 with 32 bytes of data:
Reply from 192.168.0.3: bytes=32 time=11ms TTL=128
Reply from 192.168.0.3: bytes=32 time=0ms TTL=128
Reply from 192.168.0.3: bytes=32 time=1ms TTL=128
Reply from 192.168.0.3: bytes=32 time=0ms TTL=128
Ping statistics for 192.168.0.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 11ms, Average = 3ms
PC>ping 192.168.0.4
Pinging 192.168.0.4 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.4:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
PC>ping 192.168.0.5
Pinging 192.168.0.5 with 32 bytes of data:
Reply from 192.168.0.5: bytes=32 time=1ms TTL=128
Reply from 192.168.0.5: bytes=32 time=1ms TTL=128
Reply from 192.168.0.5: bytes=32 time=1ms TTL=128
Reply from 192.168.0.5: bytes=32 time=0ms TTL=128
Ping statistics for 192.168.0.5:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
PC>ping 192.168.0.6
Pinging 192.168.0.6 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.6:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
PC>ping 192.168.0.7
Pinging 192.168.0.7 with 32 bytes of data:
Reply from 192.168.0.7: bytes=32 time=11ms TTL=128
Reply from 192.168.0.7: bytes=32 time=1ms TTL=128
Reply from 192.168.0.7: bytes=32 time=0ms TTL=128
Reply from 192.168.0.7: bytes=32 time=0ms TTL=128
Ping statistics for 192.168.0.7:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 11ms, Average = 3ms
PC>ping 192.168.0.8
Pinging 192.168.0.8 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.8:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
PC>ping 192.168.0.9
Pinging 192.168.0.9 with 32 bytes of data:
Reply from 192.168.0.9: bytes=32 time=1ms TTL=128
Reply from 192.168.0.9: bytes=32 time=0ms TTL=128
Reply from 192.168.0.9: bytes=32 time=0ms TTL=128
Reply from 192.168.0.9: bytes=32 time=0ms TTL=128
Ping statistics for 192.168.0.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
PC>ping 192.168.0.10
Pinging 192.168.0.10 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.10:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
PC>ping 192.168.0.11
Pinging 192.168.0.11 with 32 bytes of data:
Reply from 192.168.0.11: bytes=32 time=11ms TTL=128
Reply from 192.168.0.11: bytes=32 time=0ms TTL=128
Reply from 192.168.0.11: bytes=32 time=0ms TTL=128
Reply from 192.168.0.11: bytes=32 time=0ms TTL=128
Ping statistics for 192.168.0.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 11ms, Average = 2ms
PC>ping 192.168.0.12
Pinging 192.168.0.12 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.12:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
PC>ping 192.168.0.13
Pinging 192.168.0.13 with 32 bytes of data:
Reply from 192.168.0.13: bytes=32 time=2ms TTL=128
Reply from 192.168.0.13: bytes=32 time=0ms TTL=128
Reply from 192.168.0.13: bytes=32 time=0ms TTL=128
Reply from 192.168.0.13: bytes=32 time=0ms TTL=128
Ping statistics for 192.168.0.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 0ms
PC>ping 192.168.0.14
Pinging 192.168.0.14 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.14:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
CONCLUSION:
Thus, we have designed Virtual LAN and it’s connection.

More Related Content

PDF
Switching
PPTX
PPTX
PDF
IEEE 802.11a Physical Layer Simulation
PPTX
Basic switching concepts and configuration
PPT
Switching units
PDF
STP (spanning tree protocol)
PPT
22 Network Layer_Delivery_forwarding_and_Routing
Switching
IEEE 802.11a Physical Layer Simulation
Basic switching concepts and configuration
Switching units
STP (spanning tree protocol)
22 Network Layer_Delivery_forwarding_and_Routing

What's hot (19)

PDF
Cisco discovery drs ent module 3 - v.4 in english.
PDF
Data communication lab manual
PPT
第15讲 Stp
DOCX
Packet Tracer: Cisco, Spanning tree protocol
PPT
Network switching
PPTX
Vlans and inter vlan routing
PDF
Ccna 3-discovery-4-0-module-6-100-
PPTX
Media Access Layer
PPT
Layer 2 switching fundamentals(networking)
DOCX
Packet Tracer: WAN, point to point links.
PPT
Chapter 13
PDF
Day 4 LAYER 2 SWITCHING
PDF
Spanning tree protocol (stp)
PPTX
Spanning tree protocol
PPTX
Unit 3 - Data Link Layer - Part B
PDF
Multicast address
PPTX
Spanning Tree Protocol (STP)
PPT
4d routing
PDF
Cisco discovery drs ent module 3 - v.4 in english.
Data communication lab manual
第15讲 Stp
Packet Tracer: Cisco, Spanning tree protocol
Network switching
Vlans and inter vlan routing
Ccna 3-discovery-4-0-module-6-100-
Media Access Layer
Layer 2 switching fundamentals(networking)
Packet Tracer: WAN, point to point links.
Chapter 13
Day 4 LAYER 2 SWITCHING
Spanning tree protocol (stp)
Spanning tree protocol
Unit 3 - Data Link Layer - Part B
Multicast address
Spanning Tree Protocol (STP)
4d routing
Ad

Viewers also liked (20)

PPT
Vlan
PPTX
How to make a simple application on packet tracer
PPT
Packet tracer
PPTX
PDF
At8000 s configurando vla_ns
PPT
Expl sw chapter_06_inter_vlan
PPT
1 networking devices 2014
PPT
Inter-Vlan Routeando
PPT
Vlan configuration in medium sized network
PPTX
DOCX
Vlan Types
PPT
Day 14.2 inter vlan
PDF
Provider ethernet vlan cross connect
PDF
Vlan
PPT
What is a VLAN?
PPTX
Networking
PPT
Vlans
Vlan
How to make a simple application on packet tracer
Packet tracer
At8000 s configurando vla_ns
Expl sw chapter_06_inter_vlan
1 networking devices 2014
Inter-Vlan Routeando
Vlan configuration in medium sized network
Vlan Types
Day 14.2 inter vlan
Provider ethernet vlan cross connect
Vlan
What is a VLAN?
Networking
Vlans
Ad

Similar to VLAN on packet Tracer (20)

PPT
Layer2-vlans
PPTX
Presentation
PPTX
Presentation
PPT
layer2-network-design.ppt
PDF
PPTX
Vla ns
PPT
layer2-network-design.ppt
PPT
mod8-VLANs.ppt
PPTX
VLAN (Virtual Local Area Network) Full details.pptx
PPTX
Presentation on ccna
PPTX
Presentation on ccna
PDF
Networking
PPT
Mod8 vlans
PDF
Vlan.pdf
PPT
VLAN Virtual Area Network ,Switch,Ethernet ,VIkram Snehi
PPT
Chapter 1 Switch Network Device (1).ppt
PDF
Uccn1003 -may10_-_lect03a_-_lan_design_issues
DOCX
Network virtualization beyond vla ns-part1
PDF
Config vlans
Layer2-vlans
Presentation
Presentation
layer2-network-design.ppt
Vla ns
layer2-network-design.ppt
mod8-VLANs.ppt
VLAN (Virtual Local Area Network) Full details.pptx
Presentation on ccna
Presentation on ccna
Networking
Mod8 vlans
Vlan.pdf
VLAN Virtual Area Network ,Switch,Ethernet ,VIkram Snehi
Chapter 1 Switch Network Device (1).ppt
Uccn1003 -may10_-_lect03a_-_lan_design_issues
Network virtualization beyond vla ns-part1
Config vlans

More from BIRLA VISHVAKARMA MAHAVIDYALAY (14)

PDF
VLAN ON PACKET TRACER
PDF
VLAN ON PACKET TRACER
PPTX
Stepper motor interfacing
PPTX
DOCX
Gujarat technological universit1
PPTX
Arithmetic and logical instructions
PPTX
PPTX
DOCX
Automatic room light controller with bidirectional visitor counter
PPT
Automaticroomlightcontroller[1]
VLAN ON PACKET TRACER
VLAN ON PACKET TRACER
Stepper motor interfacing
Gujarat technological universit1
Arithmetic and logical instructions
Automatic room light controller with bidirectional visitor counter
Automaticroomlightcontroller[1]

Recently uploaded (20)

PDF
Digital Logic Computer Design lecture notes
PPTX
CYBER-CRIMES AND SECURITY A guide to understanding
PPTX
Geodesy 1.pptx...............................................
PPTX
additive manufacturing of ss316l using mig welding
PPTX
IOT PPTs Week 10 Lecture Material.pptx of NPTEL Smart Cities contd
PDF
keyrequirementskkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk
PPTX
Foundation to blockchain - A guide to Blockchain Tech
PPTX
MET 305 2019 SCHEME MODULE 2 COMPLETE.pptx
PPTX
UNIT-1 - COAL BASED THERMAL POWER PLANTS
PPTX
Recipes for Real Time Voice AI WebRTC, SLMs and Open Source Software.pptx
PPTX
CH1 Production IntroductoryConcepts.pptx
PDF
PRIZ Academy - 9 Windows Thinking Where to Invest Today to Win Tomorrow.pdf
PPTX
MCN 401 KTU-2019-PPE KITS-MODULE 2.pptx
PPTX
FINAL REVIEW FOR COPD DIANOSIS FOR PULMONARY DISEASE.pptx
PDF
July 2025 - Top 10 Read Articles in International Journal of Software Enginee...
PDF
Operating System & Kernel Study Guide-1 - converted.pdf
PDF
PPT on Performance Review to get promotions
PDF
composite construction of structures.pdf
PPTX
OOP with Java - Java Introduction (Basics)
PDF
Evaluating the Democratization of the Turkish Armed Forces from a Normative P...
Digital Logic Computer Design lecture notes
CYBER-CRIMES AND SECURITY A guide to understanding
Geodesy 1.pptx...............................................
additive manufacturing of ss316l using mig welding
IOT PPTs Week 10 Lecture Material.pptx of NPTEL Smart Cities contd
keyrequirementskkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk
Foundation to blockchain - A guide to Blockchain Tech
MET 305 2019 SCHEME MODULE 2 COMPLETE.pptx
UNIT-1 - COAL BASED THERMAL POWER PLANTS
Recipes for Real Time Voice AI WebRTC, SLMs and Open Source Software.pptx
CH1 Production IntroductoryConcepts.pptx
PRIZ Academy - 9 Windows Thinking Where to Invest Today to Win Tomorrow.pdf
MCN 401 KTU-2019-PPE KITS-MODULE 2.pptx
FINAL REVIEW FOR COPD DIANOSIS FOR PULMONARY DISEASE.pptx
July 2025 - Top 10 Read Articles in International Journal of Software Enginee...
Operating System & Kernel Study Guide-1 - converted.pdf
PPT on Performance Review to get promotions
composite construction of structures.pdf
OOP with Java - Java Introduction (Basics)
Evaluating the Democratization of the Turkish Armed Forces from a Normative P...

VLAN on packet Tracer

  • 1. Affiliated with GTU A Open-Ended Problem Report on VLAN on packet tracer (Mesh topology) Prepared as a part of the requirements for the subject of Data Communication and Networking (2171008) BE IV, Semester VII (ELECTRONICS AND TELECOMMUNICATION) Submitted by: - 1. Prasiddh Makadiya 130080112029 2. Apar Trivedi 130080112057 3. Vatsal Bodiwala 140083112002 PROF. Anish Vahora (Faculty Guide) PROF. MEHUL B SHAH (Head of the Department) Academic year (2016-2017) GUJARAT TECHNOLOGICALUNIVERSITY BIRLA VISHWAKARMA MAHAVIDYALAYA
  • 2. Virtual Local Area Networks (VLAN):- In a traditional LAN, workstations are connected to each other by means of a hub or a repeater. These devices propagate any incoming data throughout the network. However, if two people attempt to send information at the same time, a collision will occur and all the transmitted data will be lost. Once the collision has occurred, it will continue to be propagated throughout the network by hubs and repeaters. The original information will therefore need to be resent after waiting for the collision to be resolved, thereby incurring a significant wastage of time and resources. To prevent collisions from traveling through all the workstations in the network, a bridge or a switch can be used. These devices will not forward collisions, but will allow broadcasts (to every user in the network) and multicasts (to a pre-specified group of users) to pass through. A router may be used to prevent broadcasts and multicasts from traveling through the network. The workstations, hubs, and repeaters together form a LAN segment. A LAN segment is also known as a collision domain since collisions remain within the segment. The area within which broadcasts and multicasts are confined is called a broadcast domain or LAN. Thus a LAN can consist of one or more LAN segments. Defining broadcast and collision domains in a LAN depends on how the workstations, hubs, switches, and routers are physically connected together. This means that everyone on a LAN must be located in the same area (see Figure1). Figure 1: Physical view of a LAN VLAN's allow a network manager to logically segment a LAN into different broadcast domains (see Figure2). Since this is a logical segmentation and not a physical one, workstations do not
  • 3. have to be physically located together. Users on different floors of the same building, or even in different buildings can now belong to the same LAN. Physical View Logical View Figure 2: Physical and logical view of a VLAN. VLAN's also allow broadcast domains to be defined without using routers. Bridging software is used instead to define which workstations are to be included in the broadcast domain. Routers would only have to be used to communicate between two VLAN's.
  • 4. Mesh topology A network setup where each computer and network device is interconnected with one another, allowing for most transmissions to be distributed, even if one of the connections go down. This topology is not commonly used for most computer networks as it is difficult and expensive to have redundant connection to every computer. However, this topology is commonly used for wireless networks. Below is a visual example of a simple computer setup on a network using a mesh topology. A mesh topology can be a full mesh topology or a partially connected mesh topology. In a full mesh topology, every computer in the network has a connection to each of the other computers in that network. The number of connections in this network can be calculated using the following formula (n is the number of computers in the network): n(n-1)/2 In a partially connected mesh topology, at least two of the computers in the network have connections to multiple other computers in that network. This is a cheaper way to build a network that has some redundancy in the event one of the primary computers or connections in the network were to be down. Description:- In this Open-Ended Problem we have design VLAN on Cicso packet Tracer. Switch0, Switch1, Switch2, Switch3 and Switch4 are connected in mesh topology. Three PCs are connected with every switch 0-4. In this problem VLAN is design on based on its IP address. If last pair in dotted decimal formal IP address is odd then it is in VLAN 3 named ‘Odd’. If last pair in dotted decimal formal IP address is even then it is in VLAN 2 named ‘Even’.
  • 5. VLAN 2 (Even) VLAN 3 (Odd) 192.168.0.2 192.168.0.1 192.168.0.4 192.168.0.3 192.168.0.6 192.168.0.5 192.168.0.8 192.168.0.7 192.168.0.10 192.168.0.9 192.168.0.12 192.168.0.11 192.168.0.14 192.168.0.13 192.168.0.15 Switch0 Switch1 Switch2 Switch3 Switch4 192.168.0.1 192.168.0.4 192.168.0.7 192.168.0.10 192.168.0.13 192.168.0.2 192.168.0.5 192.168.0.8 192.168.0.11 192.168.0.14 192.168.0.3 192.168.0.6 192.168.0.9 192.168.0.12 192.168.0.15 VLAN on packet tracer (Mesh topology)
  • 6. Command in switch0 Command Line Interface (CLI) :- Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#exit Switch(config)#vlan 3 Switch(config-vlan)#name odd Switch(config-vlan)#exit Switch(config)#interface fa0/1 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#exit Switch(config)#interface fa0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#exit Switch(config)#interface fa0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#exit Switch(config)#end Switch# Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up
  • 7. Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#interface fa 0/5 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/6, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up Command in switch1 Command Line Interface (CLI) :- Switch> Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#exit Switch(config)#vlan 3 Switch(config-vlan)#name odd Switch(config-vlan)#exit Switch(config)#interface fa 0/1
  • 8. Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#exit Switch(config)#interface fa 0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#exit Switch(config)#interface fa 0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#exit Switch(config)#end Switch# %SYS-5-CONFIG_I: Configured from console by console Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINK-5-CHANGED: Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/6, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
  • 9. %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up Command in switch2 Command Line Interface (CLI) Switch>en Switch# Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#e Switch(config)#vlan 3 Switch(config-vlan)#name odd Switch(config-vlan)#e Switch(config)#interface fa 0/1 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#e Switch(config)#end Switch# %SYS-5-CONFIG_I: Configured from console by console Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# Switch(config)# Switch(config)# Switch(config)#interface fa 0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#e Switch(config)#
  • 10. Switch(config)# Switch(config)#interface fa 0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)# Switch(config-if)#e Switch(config)# Switch(config)# Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINK-5-CHANGED: Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/6, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
  • 11. Command in switch3 Command Line Interface (CLI) Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#e Switch(config)#vlan 3 Switch(config-vlan)#name odd Switch(config-vlan)#e Switch(config)#interface fa 0/1 Switch(config-if)# Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#e Switch(config)#interface fa 0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#e Switch(config)#interface fa 0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#e Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up Switch(config-if)#e Switch(config)#interface fa 0/5 Switch(config-if)#switchport mode trunk
  • 12. Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up Switch(config-if)#interface fa 0/6 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up Switch(config-if)#interface fa 0/5 Switch(config-if)#switchport mode trunk Switch(config-if)#e Switch(config)#interface fa 0/6 Switch(config-if)#switchport mode trunk Switch(config-if)#e Switch(config)#interface fa 0/7 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up Command in switch4 Command Line Interface (CLI) Switch> Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#e Switch(config)#vlan 3
  • 13. Switch(config-vlan)#name odd Switch(config-vlan)#e Switch(config)#interface fa 0/1 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#e Switch(config)#interface fa 0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#e Switch(config)#interface fa 0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#e Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)#e Switch(config)#interface fa 0/5 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up Switch(config-if)#e Switch(config)#interface fa 0/6 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up Switch(config-if)#e Switch(config)# Switch(config)#interface fa 0/7
  • 14. Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up OUTPUT :- Packet Tracer PC Command Line 1.0 PC>ping 192.168.0.1 Pinging 192.168.0.1 with 32 bytes of data: Reply from 192.168.0.1: bytes=32 time=1ms TTL=128 Reply from 192.168.0.1: bytes=32 time=0ms TTL=128 Reply from 192.168.0.1: bytes=32 time=20ms TTL=128 Reply from 192.168.0.1: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 20ms, Average = 5ms PC>ping 192.168.0.2 Pinging 192.168.0.2 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out.
  • 15. Ping statistics for 192.168.0.2: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.3 Pinging 192.168.0.3 with 32 bytes of data: Reply from 192.168.0.3: bytes=32 time=11ms TTL=128 Reply from 192.168.0.3: bytes=32 time=0ms TTL=128 Reply from 192.168.0.3: bytes=32 time=1ms TTL=128 Reply from 192.168.0.3: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.3: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 11ms, Average = 3ms PC>ping 192.168.0.4 Pinging 192.168.0.4 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.4: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.5
  • 16. Pinging 192.168.0.5 with 32 bytes of data: Reply from 192.168.0.5: bytes=32 time=1ms TTL=128 Reply from 192.168.0.5: bytes=32 time=1ms TTL=128 Reply from 192.168.0.5: bytes=32 time=1ms TTL=128 Reply from 192.168.0.5: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.5: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms PC>ping 192.168.0.6 Pinging 192.168.0.6 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.6: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.7 Pinging 192.168.0.7 with 32 bytes of data: Reply from 192.168.0.7: bytes=32 time=11ms TTL=128 Reply from 192.168.0.7: bytes=32 time=1ms TTL=128
  • 17. Reply from 192.168.0.7: bytes=32 time=0ms TTL=128 Reply from 192.168.0.7: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.7: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 11ms, Average = 3ms PC>ping 192.168.0.8 Pinging 192.168.0.8 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.8: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.9 Pinging 192.168.0.9 with 32 bytes of data: Reply from 192.168.0.9: bytes=32 time=1ms TTL=128 Reply from 192.168.0.9: bytes=32 time=0ms TTL=128 Reply from 192.168.0.9: bytes=32 time=0ms TTL=128 Reply from 192.168.0.9: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.9: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  • 18. Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms PC>ping 192.168.0.10 Pinging 192.168.0.10 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.11 Pinging 192.168.0.11 with 32 bytes of data: Reply from 192.168.0.11: bytes=32 time=11ms TTL=128 Reply from 192.168.0.11: bytes=32 time=0ms TTL=128 Reply from 192.168.0.11: bytes=32 time=0ms TTL=128 Reply from 192.168.0.11: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.11: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 11ms, Average = 2ms PC>ping 192.168.0.12
  • 19. Pinging 192.168.0.12 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.12: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.13 Pinging 192.168.0.13 with 32 bytes of data: Reply from 192.168.0.13: bytes=32 time=2ms TTL=128 Reply from 192.168.0.13: bytes=32 time=0ms TTL=128 Reply from 192.168.0.13: bytes=32 time=0ms TTL=128 Reply from 192.168.0.13: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.13: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 2ms, Average = 0ms PC>ping 192.168.0.14 Pinging 192.168.0.14 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.14: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
  • 20. CONCLUSION: Thus, we have designed Virtual LAN and it’s connection.