IPv4 Protocol field tells the receiver what kind of protocol message is inside the IP datagram’s payload. So, no—ICMP, IGMP, OSPF, TCP, and UDP are not flags inside the payload. The IPv4 header contains a …
Yes — if the link between two routers is Ethernet, the packet is carried from one router to the next inside an Ethernet frame that uses MAC addresses for that particular hop. But the important …
An electrical signal is a changing electrical quantity, usually voltage or current, in a wire, cable, or electronic circuit. Examples include: A simple way to think about it is: Electrical signal = changing voltage and/or …
A signal is a physical quantity that changes over time or space. Examples include changes in sound pressure, light, temperature, voltage, or current. An electrical signal is a changing electrical quantity, usually voltage or current. …
Electrical Signals: What Is Really Traveling Through a Wire? Electrical Signals: What Is Really Traveling Through a Wire? When people hear the phrase electrical signal, it is easy to imagine electricity as something flowing through …
IPv4 Protocol field tells the receiver what kind of protocol message is inside the IP datagram’s payload.
So, no—ICMP, IGMP, OSPF, TCP, and UDP are not flags inside the payload. The IPv4 header contains a small numeric field called Protocol, and that number identifies how to interpret the payload.
Yes — if the link between two routers is Ethernet, the packet is carried from one router to the next inside an Ethernet frame that uses MAC addresses for that particular hop.
But the important distinction is:
Routers decide where to send the packet using Layer 3 information such as the IP destination (or sometimes an MPLS label), not by using the final destination’s MAC address.
For example:
Host A → Router 1 → Router 2 → Router 3 → Host B
Suppose all links are Ethernet.
Hop 1: Host A → Router 1
IP packet:
Source IP = Host A
Destination IP = Host B
Ethernet frame:
Source MAC = Host A MAC
Destination MAC = Router 1 MAC
Hop 2: Router 1 → Router 2
Router 1 removes the old Ethernet frame, examines the IP packet, chooses Router 2 as the next hop, and creates a new frame:
IP packet:
Source IP = Host A
Destination IP = Host B
New Ethernet frame:
Source MAC = Router 1's outgoing-interface MAC
Destination MAC = Router 2's MAC
Hop 3: Router 2 → Router 3
Again:
Source MAC = Router 2
Destination MAC = Router 3
The MAC addresses change at every Ethernet hop.
So:
IP addresses: mostly end-to-end
MAC addresses: hop-to-hop
A useful diagram is:
Host A R1 R2 R3 Host B
IP A IP B
MAC A → MAC R1
MAC R1 → MAC R2
MAC R2 → MAC R3
MAC R3 → MAC B
IP A --------------------------------------------------> IP B
But not every Internet-core link has to use MAC addresses
This is the important qualification.
A router-to-router link could use:
Ethernet → MAC addresses are used
PPP → no Ethernet MAC addressing
MPLS → labels may be used for forwarding through the provider network
other Layer-2 technologies → their own framing/addressing rules
Today, Ethernet is very common even between routers, so MAC addresses are often involved. But it is more accurate to say:
Each router forwards the IP packet to the next hop using the Layer-2 mechanism of that particular link. If the link is Ethernet, that mechanism includes source and destination MAC addresses.
So I would not say:
“The Internet core routes packets using MAC addresses.”
I would say:
The Internet core routes packets using Layer 3 routing, while each individual Ethernet hop uses MAC addresses to deliver the frame to the next router.
An electrical signal is a changing electrical quantity, usually voltage or current, in a wire, cable, or electronic circuit.
Examples include:
signals traveling through copper Ethernet cables,
audio signals inside electronic circuits,
voltage pulses inside digital electronics.
A simple way to think about it is:
Electrical signal = changing voltage and/or current
For example:
Voltage
↑
| /‾\ /‾\
| / \ / \
|____/ \__/ \____ → Time
The graph shows how the voltage changes over time.
An electromagnetic signal is a changing combination of electric and magnetic fields that propagates through space or through a medium.
Examples include:
Wi-Fi signals,
cellular signals,
radio broadcasts,
satellite communication,
microwave communication.
A simple way to think about it is:
Electromagnetic signal = changing electric and magnetic fields traveling as a wave
For Wi-Fi, the process is approximately:
Digital data
↓
Electrical signal inside the device
↓
Antenna
↓
Electromagnetic radio signal
↓
Air
The antenna converts the high-frequency electrical signal in the circuit into an electromagnetic wave that travels through the air.
Main Difference
Electrical Signal
Electromagnetic Signal
Usually described in terms of voltage and current
Described in terms of electric and magnetic fields
Commonly travels through conductors or circuits
Can travel through air or space
Example: copper Ethernet cable
Example: Wi-Fi
Often measured as voltage versus time
Often discussed as radio waves, frequency, field strength, or wavelength
The two ideas are related.
A changing electrical current can create changing electric and magnetic fields. This is how an antenna produces a radio signal.
Similarly, when an electromagnetic radio wave reaches a receiving antenna, it causes a small electrical signal in the antenna and receiver circuitry.
So the relationship can be shown as:
Electrical signal
↓
Antenna
↓
Electromagnetic signal
↓
Antenna
↓
Electrical signal
For networking, a simple distinction is:
Copper cable → electrical signal
Fibre-optic cable → optical/light signal
Wi-Fi → electromagnetic/radio signal
One subtle point is that electrical signals in real cables also involve electromagnetic fields physically. However, in normal engineering and networking terminology, a signal carried through a copper conductor is usually called an electrical signal, while a wireless signal traveling through the air is usually called an electromagnetic or radio signal.
Electrical Signals: What Is Really Traveling Through a Wire?
Electrical Signals: What Is Really Traveling Through a Wire?
When people hear the phrase electrical signal, it is easy to imagine electricity as something flowing through a wire like water through a pipe. That picture is useful in some situations, but it does not fully describe what is happening in communication systems.
An electrical signal is better understood as a controlled change in electrical quantities, especially voltage and current, over time. In cables and transmission lines, these changes are associated with electromagnetic fields that propagate along the conductors.
What Is an Electrical Signal?
At a simple level:
An electrical signal is a changing voltage and/or current that can represent information.
For example, a communication system might use different electrical conditions to represent digital data:
Data: 1 0 1 1
Voltage: High Low High High
The actual encoding used in modern networks can be much more sophisticated, but the basic idea is the same: information is represented by controlled electrical changes.
Is an Electrical Signal Voltage or Current?
It can involve both.
Voltage and current are closely related in an electrical circuit or transmission line.
Voltage is the electrical potential difference between two points.
Current is the movement of electric charge.
An electrical signal generally involves time-varying voltage and corresponding current.
For introductory explanations, electrical signals are often shown as voltage changing over time, because voltage is easy to visualize on a graph.
For example:
Voltage
5 V ──────── ────────
│ │
0 V └──────────┘
time →
But this graph is only one representation of the physical signal.
What Is Actually Happening in the Wire?
A real electrical communication signal is more than voltage values appearing at different moments.
In a cable:
voltage changes,
current changes,
an electric field exists between conductors,
a magnetic field exists around the conductors,
electromagnetic energy propagates along the cable.
A more complete description is:
A real electrical signal is an electromagnetic disturbance guided by the conductors, represented electrically by changing voltage and current.
This becomes especially important when dealing with high-speed communication systems such as Ethernet.
What Is a Conductor?
A conductor is a material that allows electric charge to move relatively easily.
Common conducting materials include:
copper,
aluminum,
silver.
In networking cables, copper is very common.
For example, a simple pair of conductors might look like:
Copper conductor A ─────────────────────
Copper conductor B ─────────────────────
The electrical signal is related to the voltage difference between these conductors and the current flowing through them.
Twisted-Pair Ethernet
Ethernet cables commonly use twisted pairs of copper wires.
A simplified pair looks like:
Wire 1 ~~~~~~~\
} Twisted pair
Wire 2 ~~~~~~~/
The two wires are twisted around each other.
Ethernet commonly uses differential signaling, which means that the receiver is interested mainly in the voltage difference between the two wires rather than simply the voltage on one wire relative to ground.
Conceptually:
Wire A voltage: rises
Wire B voltage: falls
Receiver examines:
Voltage A - Voltage B
This approach helps the communication system resist electrical noise.
Does Electricity Travel Through the Wire?
This question needs careful wording.
Electric charge does move in conductors, but the electrons themselves do not race from the transmitter to the receiver at the speed of the communication signal.
Individual electrons usually have a relatively slow average drift.
The electromagnetic disturbance, however, propagates along the cable much faster—typically a significant fraction of the speed of light.
So when data is sent through an Ethernet cable:
The same individual electrons are not carrying the data all the way from one computer to another.
Instead, changes in the electromagnetic field propagate through the transmission line.
A useful analogy is a long row of closely spaced objects. Movement at one end can produce an effect that travels along the row even though each individual object moves only a small distance.
The Signal Is Not Just Inside the Copper
Another important idea is that the electromagnetic energy associated with the signal is not confined entirely inside the metal conductor.
Electric and magnetic fields exist around and between the conductors.
The conductors help establish and guide these fields.
Therefore, a more accurate statement than:
“The electricity travels inside the wire”
is:
The conductors guide an electromagnetic signal along the cable.
For everyday explanations, saying that an electrical signal travels through a wire is still perfectly reasonable. The electromagnetic description simply explains the physical process more accurately.
Electrical Signals and Digital Data
Suppose a computer needs to transmit:
10110100
Those 0s and 1s are data.
They are abstract symbols. Literal 0s and 1s do not travel through the copper cable.
The network interface converts the digital information into electrical signal patterns.
Conceptually:
Digital data
↓
Electrical encoding
↓
Changing voltage/current
↓
Cable
↓
Receiver detects signal
↓
Digital data reconstructed
This is the connection between data and signals.
Data is the representation of information. The electrical signal is the physical mechanism used to carry that data.
Does a Digital Signal Have to Be a Square Wave?
No.
Diagrams often show digital signals as simple high and low voltage levels:
┌───────┐ ┌───────┐
──────┘ └───────┘ └────
This is useful for explaining basic digital concepts, but real high-speed signals usually do not look like perfect square waves.
Real systems are affected by:
resistance,
capacitance,
inductance,
bandwidth limitations,
attenuation,
reflections,
interference,
noise.
Modern communication systems also use sophisticated signaling and coding methods.
Therefore:
Digital data does not mean that the real physical signal must look like perfect rectangular pulses.
Signal Versus Power
Electrical signals also relate to electrical power.
So the device is using or transferring power at a rate of:\[ 20\text{ watts} \]
Power Is Not Energy
Power and energy are related, but they are not the same thing.
Power tells us how quickly energy is being transferred or used.
Energy includes time:\[ E = P \times t \]
Since:\[ P = V \times I \]
we can write:\[ E = V \times I \times t \]
If a device uses 20 W for one hour:\[ 20\text{ W} \times 1\text{ h} = 20\text{ Wh} \]
So:
Voltage × Current = Power
while:
Voltage × Current × Time = Energy
This is also why electricity bills commonly use kilowatt-hours:\[ 1\text{ kWh} = 1000\text{ Wh} \]
Signals and Power Are Related but Different Concepts
An electrical communication signal contains energy, but its main purpose is often to represent information, not simply to deliver useful electrical power.
Compare two systems:
Electrical power cable
The main goal is to transfer energy.
Power source
↓
Electrical energy
↓
Appliance
Communication cable
The main goal is to communicate information.
Data
↓
Electrical signal
↓
Cable
↓
Signal detected
↓
Data recovered
Both involve voltage, current, energy, and electromagnetic fields, but their primary purposes are different.
A Useful Mental Model
At different levels of detail, electrical signals can be described in different ways.
At the simplest level:
An electrical signal is voltage changing over time.
A more complete description is:
An electrical signal involves changing voltage and current.
At the physical level:
An electrical communication signal is an electromagnetic wave or disturbance guided by conductors, represented by changing voltage and current.
All three statements can be useful. The difference is simply the level of detail.
Putting Everything Together
A communication system using copper can be summarized as:
Information
↓
Data
↓
Electrical encoding
↓
Changing voltage and current
↓
Electromagnetic signal
↓
Copper conductors guide the signal
↓
Receiver detects the electrical changes
↓
Data reconstructed
↓
Information recovered
The key idea is that an electrical signal is not simply “electrons carrying bits through a wire.”
It is a physical electromagnetic phenomenon involving voltage, current, electric fields, and magnetic fields, used in a controlled way to carry information from one location to another.
Most digital communication can be understood with one simple idea:
Data and Signals: A Simple Way to Understand How Communication Works
Data is the information represented in a form that a system can use. A signal is the physical way that data is carried from one place to another.
This distinction sounds technical at first, but it becomes much easier when connected to everyday examples such as phone calls, Wi-Fi, music streaming, text messages, and fibre-optic Internet.
Information, Data, Signal, and Medium
These four ideas are related, but they are not the same.
Information is the meaning that someone wants to communicate.
For example:
“The meeting starts at 9:00.”
That sentence has meaning. That meaning is the information.
Data is the representation of that information.
A computer may represent text using numbers, and ultimately using bits such as:
01001000 01100101 01101100 01101100 01101111
These bits are data.
However, written 0s and 1s do not physically travel through a cable or through the air. Something physical must represent them.
That is where the signal comes in.
A signal is a physical quantity that changes in a controlled way so that it can represent data. Depending on the communication system, the signal may involve:
electrical changes in copper,
light in optical fibre,
radio waves through the air.
The medium is the path through which that signal travels.
So the overall idea is:
Information → Data → Signal → Medium → Signal → Data → Information
A Simple Phone Example
Imagine saying:
“Hello.”
The meaning of “Hello” is the information.
A modern phone converts the sound of the voice into digital data. That data is then represented by signals and transmitted through the communication network.
The path might look conceptually like this:
Voice
↓
Digital data
↓
Signal
↓
Communication network
↓
Signal
↓
Digital data
↓
Sound
The receiver does not receive the original sound travelling all the way from one mouth to another. The communication system converts, represents, transmits, reconstructs, and plays the information.
What Does a Sound Wave Represent?
Sound is a useful example because it shows the difference between information and a physical signal.
A sound wave in air is created by variations in air pressure.
As sound travels, regions of higher and lower pressure move through the air.
These are commonly described as:
Compression — a region of relatively higher air pressure.
Rarefaction — a region of relatively lower air pressure.
The wavy line does not mean that air molecules literally fly through the air in a curved path like that.
The graph simply shows how pressure changes over time.
The air molecules mainly vibrate back and forth around their normal positions while the pressure disturbance travels.
What Does a Signal Graph Mean?
A signal graph can be understood as a picture of:
How some physical quantity changes over time.
The horizontal direction normally represents time.
The vertical direction represents some measurable property, such as:
voltage,
signal strength,
air pressure,
light intensity.
For example:
Signal strength
↑
| /\ /\
| / \ / \
|_____/ \____/ \_____ → Time
This picture simply says that the signal becomes stronger and weaker as time passes.
Once that basic idea is clear, several common terms become easier to understand.
Amplitude describes how large or strong the signal variation is.
Frequency describes how often the pattern repeats.
Period describes how long one complete repetition takes.
Wavelength describes the physical distance covered by one complete repeating cycle of a wave.
Data Is Abstract; Signals Are Physical
One of the most useful ways to remember the distinction is:
Data is abstract. Signals are physical.
For example:
10110010
is data.
A physical communication system may represent that data using changing voltage levels, light patterns, or radio waves.
A very simplified electrical representation might look like:
Data: 1 0 1 1 0
Signal: HIGH LOW HIGH HIGH LOW
Real communication systems can use much more sophisticated encoding, but the basic principle remains the same:
Physical signals represent data.
Text Messages Do Not Literally Fly Through the Air
Suppose a phone sends:
“Hi”
over Wi-Fi.
The letters H and i do not physically fly through the room.
The phone converts the text into digital data.
That digital data is processed by networking hardware and represented in a radio signal.
The radio signal travels through the air.
A receiving device detects the radio signal and reconstructs the data.
So the process is closer to:
"Hi"
↓
Digital representation
↓
Bits
↓
Radio signal
↓
Air
↓
Radio signal received
↓
Bits reconstructed
↓
"Hi"
This is one of the clearest examples of the difference between data and signal.
What Happens in Copper, Fibre, and Wireless?
The same data can be carried using very different physical signals.
Communication medium
Typical physical signal
Copper cable
Electrical changes
Optical fibre
Light
Wi-Fi
Radio waves
Cellular network
Radio waves
Satellite communication
Radio/microwave signals
The data may remain logically the same even though the physical way of carrying it changes.
For example, an Internet packet may travel:
Laptop
↓
Wi-Fi radio
↓
Access point
↓
Electrical Ethernet signal
↓
Router
↓
Optical fibre signal
↓
Service-provider network
The same communication may pass through several different signal types before reaching its destination.
Analog and Digital
Another common distinction is between analog and digital.
An analog quantity changes continuously.
Natural sound is a good example. Air pressure varies continuously as someone speaks.
A digital representation uses discrete values.
Computers commonly represent data using binary values:
0 and 1
A microphone and digital audio system may therefore perform a process conceptually like:
Continuous sound
↓
Measurements / samples
↓
Numbers
↓
Digital data
The reverse happens during playback:
Digital data
↓
Audio reconstruction
↓
Speaker movement
↓
Sound waves
Digital Data Does Not Mean Square Waves Everywhere
A common misunderstanding is to imagine that digital communication always means perfect square-shaped electrical pulses.
Digital data may be represented by many kinds of physical signals.
For example, radio communication may encode digital information by changing properties such as:
amplitude,
frequency,
phase,
combinations of these.
Therefore:
Digital describes the data representation, not necessarily the shape of the physical signal.
A Music Streaming Example
Consider listening to music over Wi-Fi.
The music is the information.
The audio file contains digital data.
The networking system processes that data.
Wi-Fi converts networking data into radio signals.
The signal travels through the air.
The receiving device reconstructs the data.
The audio system converts the digital audio into electrical signals that drive a speaker.
The speaker produces sound waves.
So one communication chain may look like:
Music
↓
Digital audio data
↓
Network data
↓
Wi-Fi radio signal
↓
Air
↓
Wi-Fi receiver
↓
Network data
↓
Digital audio
↓
Speaker
↓
Sound
This shows that communication frequently involves several kinds of representation and several kinds of signals.
Why This Distinction Matters
Understanding data and signals makes many networking concepts easier.
It helps explain:
why computers use bits,
why networks need physical media,
why Wi-Fi uses radio,
why fibre uses light,
why copper carries electrical signals,
why the same data can travel through different media,
why signal quality affects communication,
why data can remain unchanged even when the physical transmission technology changes.
It also helps separate two questions that are often mixed together:
What information are we sending?
and
How are we physically carrying it?
The first is mainly about information and data.
The second is mainly about signals and transmission media.
The Simplest Mental Model
The entire subject can be summarized with four ideas:
Information is what we mean. Data is how we represent it. Signal is how we physically carry it. Medium is where the signal travels.
Or, in one line:
Information → Data → Signal → Medium → Signal → Data → Information
That simple chain explains a surprisingly large part of modern communication—from voice calls and Wi-Fi to fibre optics, mobile networks, satellite systems, and the Internet.
A sound wave represents changes in pressure in a medium—usually air—as the sound travels.
In air, molecules vibrate back and forth, creating alternating regions of:
Compression — higher pressure
Rarefaction — lower pressure
So when you see a sound-wave graph, the vertical axis usually represents pressure variation or signal amplitude, while the horizontal axis represents time or distance.
Wavelength → distance between repeating points such as two compressions
Period → time for one complete cycle
One important clarification: the wavy line does not mean air molecules themselves travel in a sine-wave path. The molecules mainly move back and forth around their normal positions while the pressure disturbance travels forward.
The Hidden Firewall: How Public Wi-Fi Keeps Your Devices Apart : From AI tools as is
Have you ever sat in a crowded coffee shop, connected to the free Wi-Fi, and wondered: If dozens of us are on the exact same network, why can’t I see anyone else’s computer?
It’s a valid question. When you connect to a local area network (LAN)—like the one in your home—your devices generally talk to each other without issue. Your phone can cast a video to your TV, your laptop can send a file to your printer, and you can share folders across computers.
So why doesn’t that happen when you connect to a public hotspot?
Let’s break down how public Wi-Fi networks manage dozens of simultaneous connections, how they stop strangers from peering into your laptop, and what options you have when you actually do need to share data with someone sitting right next to you.
1. The Basics: Does Everyone Get an IP Address?
Yes. The moment your phone or laptop connects to a public hotspot, the router assigns it a unique private IP address.
This happens through a protocol called DHCP (Dynamic Host Configuration Protocol). The network’s router acts as a traffic controller:
It hands out private IP addresses (typically starting with 192.168.x.x or 10.x.x.x) to every single connected device.
It uses these unique IP addresses to manage incoming and outgoing data, making sure that the web page you requested ends up on your screen and not on the laptop of the person sitting two tables over.
From a networking standpoint, every device connected to that hotspot forms a single Wireless Local Area Network (WLAN).
2. The Security Barrier: Why Devices Can’t See Each Other
If everyone is on the same local network, shouldn’t you be able to “ping” or browse the device next to you?
On an unmanaged or default home network, yes. But public networks implement a fundamental security feature known as AP Isolation (Access Point Isolation), also referred to as Client Isolation.
[ Public Wi-Fi Router ]
/ \
/ \
v v
[ Your Laptop ] x [ Stranger's Laptop ]
(Blocked by AP Isolation)
How AP Isolation Works
When AP Isolation is enabled on a router:
Vertical Traffic is Allowed:Your computer can send data up to the router to access the wider internet, and the router can send data back down to your computer.
Horizontal Traffic is Dropped:The router is configured to block direct frame forwarding between wireless clients connected to the same network. If your laptop sends a packet aimed at another laptop’s local IP address, the router simply drops it.
Without AP Isolation, public Wi-Fi would be a free-for-all. A malicious user on the network could easily scan the local IP range, discover exposed network shares, attempt ARP spoofing attacks, or probe open ports on vulnerable devices.AP Isolation ensures that every connected device sits in its own digital quarantine.
3. Can You Bypass AP Isolation?
A common question among networking students and tech enthusiasts is whether an end-user can override this setting to access other devices on the network.
The short answer is no.
Because AP Isolation is enforced at Layer 2 (the data link layer) directly inside the router’s hardware/firmware, you cannot bypass it via software tweaks or terminal commands on your own device. The router is the central gatekeeper; if its rulebook says “do not forward packets between client A and client B,” your traffic goes nowhere.
Only the network administrator with direct access to the router’s management panel can enable or disable Client Isolation.
4. How to Connect Devices on Public Wi-Fi
If AP Isolation blocks local communication, how can you share a file or play a local multiplayer game with a friend sitting next to you at a coffee shop?
You have to route around the router’s local restrictions using one of these four methods:
Method
How It Works
Best Used For
Cloud / Internet Routing
Data travels vertically up to the internet (e.g., via Google Drive, Dropbox, or email) and back down to the destination device.
Basic file sharing and document collaboration.
Peer-to-Peer Wireless
Protocols like Apple AirDrop, Google Quick Share, or Wi-Fi Direct bypass the router entirely. Devices negotiate a direct radio link between their Wi-Fi cards.
Fast, local transfers without using mobile data.
Virtual Private Networks (Mesh VPNs)
Tools like Tailscale or ZeroTier build an encrypted overlay network over the internet. Both devices see each other as if they were on a private LAN.
Remote access, SSH, and local development testing.
Personal Hotspot
One device shares its cellular connection, creating an entirely new, unisolated Wi-Fi LAN for both users.
Local gaming, wireless debugging, or private file servers.
Summary
Public Wi-Fi networks give everyone an IP address, but AP Isolation keeps those devices completely isolated from one another.It’s one of the simplest and most effective layers of protection in public network design—ensuring you can enjoy your coffee and surf the web without worrying about who else is sharing the airwaves.
One Physical Switch, Multiple VLANs: How VLANs Work, How to Configure Them, and Where IP Subnets Fit In
From AI tools as IS.
A single managed Ethernet switch can behave as though it were several independent switches.
This is the basic idea behind a VLAN — Virtual Local Area Network.
Suppose an organization has one 24-port switch. Without VLANs, all 24 ports could belong to the same Layer 2 network. Broadcast traffic generated by one device could potentially reach devices connected to all of the other ports.
With VLANs, the same physical switch can be divided logically:
The switch maintains separate Layer 2 forwarding environments for the different VLANs.
If Port 1 belongs to VLAN 10 and Port 10 belongs to VLAN 20, traffic does not simply flow between those ports merely because they are on the same physical switch.
A broadcast arriving in VLAN 10 remains in VLAN 10.
PC-A
│
│ VLAN 10 broadcast
▼
Switch
├── VLAN 10 devices receive it
└── VLAN 20 devices do NOT receive it
This is why each VLAN is normally described as a separate Layer 2 broadcast domain.
How Does a Switch Know Which VLAN a Device Belongs To?
For an ordinary user device, the administrator typically assigns the physical switch port to a VLAN.
For example:
Port 1 → VLAN 10
Port 2 → VLAN 10
Port 3 → VLAN 10
Port 4 → VLAN 20
Port 5 → VLAN 20
These ports are commonly called access ports.
A computer connected to an access port normally does not need to know anything about VLAN tagging.
The computer sends a normal Ethernet frame.
The switch already knows:
Frame entered Port 1
Port 1 belongs to VLAN 10
Therefore this frame belongs to VLAN 10
The VLAN membership is being enforced by the switch.
How Are VLANs Created?
On a managed switch, VLANs are normally created through one of several management mechanisms:
command-line interface;
web interface;
centralized network controller;
cloud management platform;
network-management API.
For example, on a Cisco-style command-line interface:
vlan 10
name STAFF
vlan 20
name ACCOUNTING
vlan 30
name GUESTS
Network Devices, VLANs, Subnets, Layer 2 and Layer 3 Switches, and Routers
From AI tools as IS.
Modern computer networks are built from several different kinds of devices and several different kinds of logical boundaries. This can become confusing because terms such as switch, router, VLAN, subnet, LAN, Layer 2, and Layer 3 are closely related but do not mean the same thing.
A particularly common source of confusion is the relationship between a VLAN and an IP subnet. In a typical corporate network, one VLAN is normally paired with one IP subnet, making them look almost interchangeable. Technically, however, they operate at different layers and solve different problems.
Similarly, a modern Layer 3 switch can perform routing, which makes it look very much like a router. Yet Layer 3 switches and routers are normally designed for somewhat different jobs.
The easiest way to understand all of this is to start with how devices communicate on a simple Ethernet network and gradually build up from there.
The Main Types of Network Devices
A modern network can include many kinds of devices.
Some of the most important are:
end devices or hosts;
servers;
Ethernet switches;
wireless access points;
routers;
firewalls;
gateways;
modems and optical network terminals.
End Devices or Hosts
An end device, often called a host, is a device that produces or consumes network communication.
Examples include:
desktop computers;
laptops;
smartphones;
tablets;
printers;
IP phones;
security cameras;
smart TVs;
servers;
IoT devices.
A laptop opening a website is an end device.
A smartphone making a VoIP call is an end device.
A printer receiving a print job is an end device.
Servers
A server is also a host, but it normally provides services to other devices.
Examples include:
web servers;
database servers;
email servers;
file servers;
DNS servers;
DHCP servers;
authentication servers;
application servers.
The distinction between a client and a server is therefore mainly about the role of the device or application, not necessarily different hardware.
What Does a Layer 2 Switch Do?
An Ethernet switch primarily works at Layer 2, the Data Link layer.
Its basic job is to move Ethernet frames between devices.
A Layer 2 switch primarily makes forwarding decisions based on:
MAC addresses
Suppose four computers are connected to one switch:
PC-A ─┐
PC-B ─┤
Switch
PC-C ─┤
PC-D ─┘
Each Ethernet network interface has a MAC address.
For example:
PC-A = AA:AA:AA:AA:AA:AA
PC-B = BB:BB:BB:BB:BB:BB
When frames arrive, the switch learns which MAC addresses are reachable through which ports.
Its MAC address table might eventually look like:
MAC address
Switch port
AA:AA:AA:AA:AA:AA
Port 1
BB:BB:BB:BB:BB:BB
Port 2
CC:CC:CC:CC:CC:CC
Port 3
If a frame destined for PC-B arrives on Port 1, the switch sees:
Destination MAC = BB:BB:BB:BB:BB:BB
checks its MAC address table and forwards the frame through Port 2.
This process does not require the switch to examine the destination IP address.
Ubiquiti’s current networking documentation describes the same basic process: Layer 2 switches learn source MAC addresses, build forwarding tables, and use those tables to decide where Ethernet frames should be sent.
Does a Layer 2 Switch Need an IP Address?
Interestingly:
A basic Layer 2 switch does not need an IP address to switch Ethernet frames.
It can learn MAC addresses and forward frames without having an IP address of its own.
For example:
PC-A ─ Switch ─ PC-B
PC-A and PC-B can exchange Ethernet traffic through the switch even if the switch itself has no management IP address.
Managed switches are usually assigned an IP address so administrators can:
connect using SSH;
access a web interface;
use SNMP;
collect telemetry;
perform configuration and monitoring.
That IP address is for management.
It is not what allows ordinary Layer 2 frame forwarding to happen.
Is a MAC Address Required?
For normal Ethernet communication, MAC addresses are fundamental.
An Ethernet frame contains source and destination MAC addresses.
For example:
Destination MAC
Source MAC
EtherType
Payload
Frame Check Sequence
So Ethernet devices generally require MAC addressing to deliver frames.
However:
IP networking itself does not universally require MAC addresses.
MAC addresses belong to technologies such as Ethernet.
IP can also operate over other Layer 2 technologies that do not use Ethernet MAC addressing in the same way.
Examples include certain:
point-to-point links;
tunnels;
PPP links;
virtual interfaces.
Therefore:
Ethernet → normally requires MAC addressing
but:
IP → does not inherently require Ethernet MAC addresses
Can MAC Communication Exist Without IP?
Yes.
Ethernet is not dependent on IP.
Two devices can exchange Layer 2 Ethernet frames using MAC addresses without running IPv4 or IPv6.
Various Layer 2 control protocols also operate without depending on ordinary IP forwarding.
Examples include protocols associated with:
spanning tree;
link discovery;
link aggregation.
So:
MAC addressing can exist without IP addressing.
Can IP Exist Without Ethernet?
Yes.
IP is a Layer 3 protocol and is not limited to Ethernet.
An IP packet can be transported over:
Ethernet;
Wi-Fi;
cellular systems;
point-to-point links;
tunnels;
many other underlying technologies.
This is one of the great strengths of IP.
The Layer 3 packet does not need to know whether one particular segment of its journey uses copper Ethernet, fiber, Wi-Fi, or another technology.
What Is a VLAN?
VLAN means:
Virtual Local Area Network
A VLAN logically separates one physical switched Ethernet infrastructure into multiple Layer 2 networks.
Suppose a company owns one switch:
Port 1 → Employee PC
Port 2 → Employee PC
Port 3 → Accounting PC
Port 4 → Accounting PC
Port 5 → Guest device
Port 6 → Guest device
Instead of putting everyone into the same Layer 2 network, the administrator could configure:
Cisco documentation describes this common design explicitly: individual IP subnetworks are commonly mapped to individual VLANs, while routing is required to communicate between VLANs.
So in practice:
One VLAN = one subnet
is a very useful design rule.
But it is not a definition saying VLAN and subnet are technically identical.
Does Subnetting Create VLANs?
No.
Subnetting creates IP networks.
It does not automatically create Layer 2 VLANs.
Consider a router:
Router
/ \
192.168.10.0/24 192.168.20.0/24
Each router interface could connect to a separate physical Ethernet network.
There might be no VLAN configuration anywhere.
Yet there are clearly two IP subnets.
Therefore:
A subnet can exist without a VLAN.
Can a VLAN Exist Without a Subnet?
Yes.
A VLAN can exist entirely at Layer 2 without any IP subnet being assigned to it.
For example:
VLAN 100
may be configured on a switch and contain Ethernet devices that use some non-IP protocol.
Or an administrator may create a VLAN before any devices or IP addresses have been assigned.
Therefore:
A VLAN does not technically require an IP subnet.
However, if hosts in that VLAN are going to use normal IPv4 or IPv6 communication, the VLAN will ordinarily be associated with an IP subnet.
Can a Network Exist Without IP?
Yes.
A computer network does not have to use Internet Protocol.
Ethernet itself is a networking technology and can carry protocols other than IPv4 or IPv6.
Historically, many networks used protocols such as:
IPX;
AppleTalk;
various proprietary networking protocols.
Specialized industrial environments can also use communication mechanisms that are not ordinary IP networks.
Today, however, IP dominates general-purpose computer networking.
Can Multiple VLANs Use One IP Subnet?
Under normal network design:
They should not.
Suppose:
VLAN 10
PC-A = 192.168.1.10/24
and:
VLAN 20
PC-B = 192.168.1.20/24
Both hosts believe they are on:
192.168.1.0/24
PC-A examines:
192.168.1.20
and concludes:
“That address belongs to my local subnet.”
So PC-A tries to discover PC-B’s MAC address using ARP.
It broadcasts:
Who has 192.168.1.20?
But the broadcast remains within VLAN 10.
PC-B is in VLAN 20 and never receives it.
Communication therefore fails under normal circumstances.
This is why the normal design is:
VLAN 10 → Subnet A
VLAN 20 → Subnet B
rather than putting the same subnet into two isolated VLANs.
Specialized techniques can change this behavior, but they are exceptions rather than the normal design.
Can One VLAN Contain Multiple IP Subnets?
Technically, yes.
For example, devices in one VLAN could be configured using:
192.168.10.0/24
and:
192.168.20.0/24
on the same Layer 2 broadcast domain.
But this is generally not the preferred design.
It complicates:
addressing;
gateway configuration;
troubleshooting;
security;
broadcast-domain design.
The normal design remains:
One VLAN mapped to one IP subnet.
What Happens When Two Computers Are in the Same VLAN and Subnet?
Suppose:
PC-A
IP: 192.168.10.10
MAC: AA-AA-AA-AA-AA-AA
and:
PC-B
IP: 192.168.10.20
MAC: BB-BB-BB-BB-BB-BB
Both belong to:
VLAN 10
Subnet: 192.168.10.0/24
and are connected through a Layer 2 switch.
The communication process is roughly as follows.
Step 1: PC-A examines the destination IP
PC-A sees:
192.168.10.20
Its subnet mask tells it that the destination is on the same subnet.
Therefore, PC-A does not send the packet to its router.
Step 2: PC-A Needs the Destination MAC Address
Ethernet delivers frames using MAC addresses.
PC-A therefore needs to determine which MAC address corresponds to:
192.168.10.20
It uses ARP for IPv4.
Conceptually:
Who has 192.168.10.20?
This is transmitted as an Ethernet broadcast.
Step 3: The Switch Floods the Broadcast
Because it is a broadcast, the switch sends it to the other ports belonging to VLAN 10.
How Does a Layer 3 Switch Move Data Between VLANs?
Suppose:
PC-A
192.168.10.10/24
VLAN 10
needs to contact:
PC-B
192.168.20.20/24
VLAN 20
PC-A examines the destination.
It sees that:
192.168.20.20
is outside its local subnet.
Therefore, rather than trying to find PC-B’s MAC address, PC-A sends the packet to its default gateway:
192.168.10.1
which belongs to the Layer 3 switch.
The First Ethernet Frame
PC-A transmits approximately:
Ethernet:
Destination MAC = MAC of VLAN 10 gateway
Source MAC = MAC of PC-A
IP:
Source IP = 192.168.10.10
Destination IP = 192.168.20.20
Notice something very important:
The destination MAC address is the gateway’s MAC address, but the destination IP address remains PC-B’s IP address.
The Layer 3 Switch Routes the Packet
The Layer 3 switch:
receives the Ethernet frame;
removes the Layer 2 Ethernet header;
examines the destination IP address;
checks its routing table;
determines that 192.168.20.0/24 is reachable through VLAN 20;
discovers PC-B’s MAC address if necessary;
constructs a new Ethernet frame;
sends the packet into VLAN 20.
The new frame might contain:
Destination MAC = PC-B's MAC
Source MAC = Layer 3 switch VLAN 20 MAC
Source IP = 192.168.10.10
Destination IP = 192.168.20.20
The Ethernet addresses changed.
The source and destination IP addresses normally did not.
This illustrates a fundamental principle:
MAC addresses normally change as packets cross routed Layer 3 boundaries, while end-to-end IP addresses normally remain the same unless something such as NAT changes them.
Layer 2 Switch vs. Layer 3 Switch
Capability
Layer 2 Switch
Layer 3 Switch
Ethernet switching
Yes
Yes
MAC address table
Yes
Yes
VLANs
Yes
Yes
Layer 2 broadcast separation
Yes
Yes
IP routing
Normally no
Yes
Routing table
Normally no forwarding role
Yes
Inter-VLAN routing
No
Yes
SVI/default gateway
Management only or limited
Yes
Static/dynamic routes
No or very limited
Usually supported to varying degrees
Typical use
Access switching
Distribution/core + access in some designs
Cisco’s training material similarly contrasts a Layer 2 Catalyst 2960 with a Layer 3-capable switch and notes that enabling IP routing allows the Layer 3 switch to perform routing functions.
What Is a Router?
A router is fundamentally a Layer 3 device.
Its main job is:
to connect different IP networks and forward packets between them based on destination IP addresses and routing information.
For example:
LAN A
192.168.10.0/24
│
Router
│
LAN B
192.168.20.0/24
or:
Corporate LAN
│
Router
│
ISP
│
Internet
Routers maintain routing tables showing how different networks can be reached.
A Router Is Not Defined as “LAN to WAN”
It is common to think:
Switch = LAN
Router = LAN to Internet
That is an oversimplification.
A router can connect:
LAN to LAN;
subnet to subnet;
VLAN to VLAN;
LAN to WAN;
WAN to WAN;
branch office to headquarters;
enterprise network to ISP;
one ISP to another ISP.
For example, two subnets inside the same building may communicate through a router.
No WAN is necessary.
If a Layer 3 Switch Routes, Why Do We Need Routers?
This is an important question.
A modern Layer 3 switch and a router overlap substantially.
Both can:
maintain routing tables;
forward IP packets;
support static routes;
support routing protocols;
route between networks.
The difference is increasingly about design, interfaces, features, scale, and intended role rather than a rigid Layer 2-versus-Layer 3 distinction.
Layer 3 Switch: Optimized for High-Speed LAN Routing
a dedicated edge router, firewall, or integrated security gateway is often used.
Can a Router Perform Layer 2 Switching?
Some routers can.
Modern network appliances frequently combine many functions.
One physical box might contain:
router;
Ethernet switch;
firewall;
VPN gateway;
Wi-Fi access point;
DHCP server.
A typical home “wireless router” is a good example.
Internally, it often contains:
Router
+
Ethernet switch
+
Wi-Fi access point
+
Firewall/NAT
+
DHCP server
So the product name does not necessarily reveal every internal function.
What Is an Access Switch?
An access switch connects end devices to the network.
Examples include:
desktop computers;
printers;
IP phones;
Wi-Fi access points;
security cameras.
A typical corporate access layer looks like:
PC ─┐
IP Phone ─┤
Printer ──┤ Access Switch
Wi-Fi AP ─┤
Camera ───┘
Access switches often provide Power over Ethernet (PoE) so the Ethernet cable can provide both data and electrical power to:
IP phones;
access points;
cameras.
Distribution and Core Switches
Larger networks often use hierarchical designs.
A simplified traditional campus architecture is:
End Devices
│
Access Switches
│
Distribution Switches
│
Core
│
WAN/Internet
Distribution and core switches are often Layer 3 switches.
They can route between many VLANs and aggregate traffic from many access switches.
Current Cisco campus families illustrate this separation. Cisco positions Catalyst 9200 and 9300 systems for access and branch/campus use, while Catalyst 9400, 9500, and 9600 families serve increasingly large distribution and core roles.
A Small-Business Network
A small office might have only:
Internet
│
Router/Firewall
│
Managed Switch
┌─┼────┬─────┐
PC AP Printer Phone
The router/firewall might perform:
Internet routing;
NAT;
DHCP;
VPN;
firewalling.
The switch provides:
Ethernet connectivity;
VLANs;
PoE;
perhaps some Layer 3 functionality.
Current examples aimed at smaller environments include Cisco Catalyst 1300 switches, which Cisco describes as designed for small and medium-sized businesses.
Cloud-managed platforms are also common in this market. Cisco Meraki, for example, offers smaller security/SD-WAN appliances for branches ranging from tens to hundreds of users.
Ubiquiti UniFi is another commonly encountered architecture in small and medium environments, offering Layer 2 and Layer 3 switching along with gateway and Wi-Fi systems.
A firewall may control which VLANs are permitted to communicate.
The edge router or firewall handles connectivity toward:
Internet providers;
branch offices;
cloud services;
VPNs.
Representative current enterprise switching platforms include Cisco Catalyst 9200 and 9300 systems. Cisco describes the 9200 family as enterprise access switching for branches and midsize campuses and the 9300 family as campus access systems with greater scale and capabilities.
For branch/WAN routing, Cisco’s current Catalyst 8300 platform is designed for SD-WAN, SASE, 5G and cloud-edge applications.
A Large Corporate Campus
A large corporation may have thousands or tens of thousands of devices.
A simplified architecture could be:
Internet / WAN
│
Edge Routers
│
Firewalls
│
Core L3 Switches
/ \
Distribution Distribution
/ \ / \
Access Access Access Access
│ │ │ │
Users/APs Phones Servers Cameras
At this scale, redundancy becomes essential.
Organizations may use:
redundant core switches;
redundant routers;
multiple ISPs;
dynamic routing protocols;
high-speed fiber links;
link aggregation;
hundreds or thousands of VLANs;
large routing tables.
Cisco currently positions Catalyst 9500 and 9600 systems for midsize-to-large campus core roles.
What Happens in a Data Centre?
Data-centre networks can be much larger and faster.
Instead of the traditional access/distribution/core hierarchy, many data centres use leaf-spine architectures.
These devices often perform both sophisticated Layer 2 and Layer 3 functions.
Cisco’s Nexus 9000 family, for example, is designed for data-centre switching and currently supports interfaces reaching 800 Gb/s on some platforms.
At this scale, the old idea that:
“switch = simple Layer 2 device”
becomes increasingly inadequate.
Modern data-centre switches often perform extensive Layer 3 routing as well.
What Devices Make Up the Internet?
The Internet is fundamentally a network of networks.
A simplified path might be:
Home/Office
│
Access Router
│
ISP Edge Router
│
ISP Core
│
Internet Peering Router
│
Another ISP
│
Data Centre
│
Server
Internet-scale routers must manage enormous quantities of traffic and very large routing tables.
They commonly use:
BGP;
MPLS;
segment routing;
high-speed optical Ethernet;
100G;
400G;
increasingly 800G links.
Representative service-provider platforms include Cisco’s 8000 Series and Juniper’s MX and PTX families.
Cisco positions its 8000 systems for carrier core, aggregation and Internet peering applications.
Juniper’s MX family is used for service-provider edge, broadband, peering and related applications, while the PTX family is designed for high-capacity core and WAN environments. Current PTX platforms support 400G and 800G architectures.
Are There Switches Inside the Internet?
Certainly.
The Internet is not built only from routers.
Switches are heavily used inside:
data centres;
ISP facilities;
Internet exchanges;
carrier Ethernet networks;
aggregation networks.
The distinction depends on what function is being performed at that point.
For communication between IP networks or autonomous systems, routing is central.
Within a data-centre fabric or local Layer 2 domain, switching may be central.
Modern hardware can perform both.
Common Equipment in Networking Labs
Networking laboratories often use either real hardware or network simulators/emulators.
Historically and still in many training environments, Cisco devices such as:
Catalyst 2960 Layer 2 switches;
Catalyst 3560/3650 Layer 3 switches;
Cisco 1941/2900-series routers
are frequently encountered.
These should be understood as training and legacy platforms, not necessarily recommendations for new corporate deployments in 2026.
Cisco’s own networking lab material has used Catalyst 2960 switches and Cisco ISR routers in hands-on exercises, while Layer 2-versus-Layer 3 comparison material uses the 2960 alongside Layer 3-capable Catalyst platforms.
Today, many labs are also virtual.
Common approaches include:
Cisco Packet Tracer;
GNS3;
EVE-NG;
vendor virtual router images;
cloud networking labs.
Virtual labs make it possible to construct networks containing many routers and switches without owning large amounts of physical hardware.
Representative Devices by Environment
The following is not a strict purchasing guide; it illustrates the kinds of equipment encountered at different scales.
Branch/WAN: Cisco Catalyst 8300 and comparable platforms;
Data centre: Cisco Nexus 9000, Juniper QFX and comparable systems;
Service-provider edge/core: Cisco 8000, Juniper MX and PTX.
Cisco’s current Catalyst portfolio explicitly divides its families among access, distribution, and core roles, while Juniper positions its MX/PTX families for edge, peering, WAN and core routing.
Putting VLAN, Subnet, Switch and Router Together
Consider a corporate network with three departments.
This architecture demonstrates all of the concepts.
Inside VLAN 10
Frames are switched using MAC addresses.
Between VLAN 10 and VLAN 20
Packets are routed using IP addresses.
Between the company and the Internet
A router/firewall forwards traffic toward the ISP.
VLAN
Defines the Layer 2 logical network.
Subnet
Defines the Layer 3 IP network.
Layer 2 switch
Moves frames within VLANs.
Layer 3 switch
Moves frames within VLANs and routes packets between IP subnets.
Router
Connects IP networks and is commonly used at WAN and Internet boundaries.
What Addresses Are Actually Used During Communication?
A useful summary is:
Inside one Ethernet LAN
Both are used:
IP address → identifies the Layer 3 endpoint
MAC address → identifies the local Ethernet destination
Suppose:
192.168.10.10
sends something to:
192.168.10.20
The IP addresses identify the endpoints.
The MAC addresses allow the Ethernet frame to cross the local LAN.
Across a Router
Suppose:
192.168.10.10
communicates with:
8.8.8.8
The destination is not local.
The computer creates a frame whose:
Destination IP = 8.8.8.8
Destination MAC = MAC address of local gateway
The router receives it.
At the next Ethernet link, a different pair of MAC addresses is normally used.
Therefore:
IP addresses identify Layer 3 source/destination communication, while MAC addresses generally identify the next Ethernet hop.
That is why MAC addresses normally change at routed boundaries while IP addresses can remain end-to-end.
Does Every Router Need a MAC Address?
Not inherently.
A router performing IP routing over Ethernet has MAC addresses on its Ethernet interfaces because Ethernet requires them.
But a router could also have a non-Ethernet point-to-point interface where Ethernet MAC addressing is irrelevant.
So:
Routing requires Layer 3 addressing, but Ethernet MAC addressing is only required when the relevant link technology is Ethernet or uses comparable MAC mechanisms.
Does Every Switch Need an IP Address?
No.
A Layer 2 switch can forward frames with no IP address configured.
A managed switch normally receives an IP address so administrators can manage it.
A Layer 3 switch, however, needs Layer 3 addresses on interfaces or SVIs when it is actually performing IP routing.
This one-to-one VLAN-to-subnet relationship is a design convention, not a statement that VLAN and subnet are identical.
Common Misconceptions
Several statements sound reasonable but are technically incorrect.
“A VLAN is a subnet.”
Not exactly.
A VLAN is Layer 2.
A subnet is Layer 3.
They are normally paired.
“Subnetting creates VLANs.”
No.
Subnetting creates IP subnets.
VLANs are configured separately at Layer 2.
“A VLAN requires IP.”
No.
A VLAN can exist without IP.
“IP requires Ethernet MAC addresses.”
No.
IP can operate over technologies other than Ethernet.
“A Layer 2 switch requires an IP address.”
No.
It requires no IP address for ordinary frame forwarding.
“A switch connects devices while a router connects LANs.”
Too simplistic.
A Layer 3 switch can route between networks, and a router can connect networks within the same building.
“Routers are only for LAN-to-WAN communication.”
No.
A router can connect any appropriate different Layer 3 networks.
“Different VLANs can normally use the same subnet.”
No.
Separate VLANs isolate Layer 2 broadcasts such as ARP, so one IP subnet spread across independently isolated VLANs normally will not function correctly without special mechanisms.
A Useful Mental Model
The simplest way to keep everything straight is to ask three different questions.
Question 1: What Layer 2 network am I in?
Think:
VLAN
and:
MAC address
and:
switch
Question 2: What Layer 3 network am I in?
Think:
subnet
and:
IP address
Question 3: How do I reach another Layer 3 network?
Think:
router
or:
Layer 3 switch
and:
default gateway
and:
routing table
Final Thought
The boundaries between switches and routers have become less rigid as networking hardware has evolved.
A traditional Layer 2 switch primarily forwards:
Ethernet frames based on MAC addresses.
A router primarily forwards:
IP packets between networks based on IP addresses and routing tables.
A Layer 3 switch combines both capabilities:
Layer 2 switching + Layer 3 routing.
Likewise, a VLAN and a subnet often appear together but represent different things:
VLAN = Layer 2 logical separation
Subnet = Layer 3 logical addressing
The normal modern design is:
One VLAN
↓
One IP subnet
↓
Layer 3 gateway
↓
Other VLANs/subnets
Within the VLAN, switches use MAC addresses.
Between subnets, routers or Layer 3 switches use IP addresses.
At the edge of the organization, routers, firewalls, or integrated gateways connect the internal network to WANs, service providers, cloud networks, and ultimately the Internet.
Once these layers are separated conceptually, much of networking becomes easier to understand:
MAC addresses and VLANs organize local Layer 2 communication. IP addresses and subnets organize Layer 3 communication. Switches move frames locally. Routers and Layer 3 switches move packets between networks.
Modern networking equipment may combine these functions in one physical device, but the underlying concepts remain distinct.
References and Further Reading
Cisco — Catalyst 9000 Switching Family. Current enterprise access, distribution, and core switching families, including Catalyst 9200, 9300, 9400, 9500, and 9600.
Cisco — Campus LAN Core and Distribution Switches. Current positioning of enterprise Layer 3 switching platforms for small, midsize, and large campus networks.
Cisco — Catalyst 8300 Series Edge Platforms. Current enterprise branch, SD-WAN, WAN edge, security, and 5G-capable routing platform.
Cisco — Nexus 9000 Series. Modern high-performance data-centre switching platforms supporting high-speed Ethernet up to 800G on current systems.
Cisco — Cisco 8000 Series. Carrier-class routing platforms designed for core, aggregation, peering, ISP and cloud-scale applications.
Cisco Networking Academy — Comparing Layer 2 and Layer 3 Devices. Discussion of Layer 2 switches, Layer 3 switches and routers, including inter-VLAN routing concepts.
Cisco — VLAN and IP Routing Configuration. Documentation explaining that hosts within the same VLAN can communicate through switching while communication between different VLANs requires Layer 3 routing.
Juniper Networks — MX Series Universal Routing Platforms. Service-provider and enterprise routing systems for broadband edge, peering, mobile backhaul and data-centre edge roles.
Juniper Networks — PTX Series Routers. High-capacity WAN/core and peering platforms supporting current 100G, 400G and 800G architectures.
Ubiquiti — Switching, Routing and STP. Modern explanation of Layer 2 MAC learning and Layer 3 routing concepts.
