Network fundamentals 8 min read
How Networks Move Information
Start with the purpose of a network, the jobs performed by endpoints and switches, and the vocabulary that makes everything else easier.
- Describe a network as a system for moving information between endpoints.
- Distinguish a switch, router, endpoint, link, protocol, and service.
- Separate physical connectivity from logical communication.
- Follow a packet through a simple commercial AV system.
A network is an agreement
A network is not just a pile of switches and cables. It is a collection of devices agreeing on how to identify one another, package information, move it, verify it, and respond when something goes wrong.
A Q-SYS Core, Dante amplifier, control processor, laptop, and camera are all endpoints. Each generates or consumes information. The network provides a path between them, while protocols provide the shared rules that make the information understandable.
That distinction matters because a cable can be connected and link lights can be blinking while communication still fails. Physical connectivity answers whether a path exists. Logical connectivity answers whether the devices can actually use it.
The basic jobs
A switch connects devices inside a local network and forwards Ethernet frames toward the correct destination. A router connects different IP networks. An endpoint originates or receives traffic. A service performs a useful job such as DHCP address assignment, DNS name resolution, or NTP time synchronization.
Protocols are the rules. Ethernet, IP, TCP, UDP, DHCP, DNS, PTP, and HTTP each solve a different part of the communication problem. No single protocol is the network; they work as a stack.
- Link: the physical or wireless connection between devices.
- Frame: the Layer 2 container moved by Ethernet switches.
- Packet: the Layer 3 container routed between IP networks.
- Application data: the actual control command, audio sample, video data, or webpage content being transported.
Follow the message, not the box
When troubleshooting, begin with the desired conversation: which device is sending, which device should receive, what protocol is used, and what path lies between them? Then test each dependency in order.
This is more reliable than staring at the most expensive device in the rack and hoping it confesses. A communication failure can come from power, cabling, port configuration, addressing, routing, name resolution, authentication, or the application itself.
Put it in an AV system.
Control command
A touchscreen sends a command through an access switch to a control processor. Ethernet moves it locally; IP identifies the devices; the control protocol defines what the command means.
AV-over-IP route
An encoder creates media traffic, switches forward it across the required links, and a decoder reconstructs it. Discovery, clocking, multicast, and control may each use different supporting protocols.
- Endpoint
- A device that originates or consumes network communication.
- Protocol
- A defined set of communication rules.
- Switch
- A device that forwards Ethernet frames inside a Layer 2 network.
- Router
- A device that forwards packets between different IP networks.
- Service
- A network-accessible function such as DHCP, DNS, NTP, or a web interface.
Trace one conversation
Choose one real AV action—pressing volume up, selecting a source, or subscribing a Dante receiver. Name the sender, receiver, physical path, and every network service you think the action depends on.
Three quick questions.
01Can link lights prove that two applications can communicate?
No. They confirm part of the physical connection, not addressing, routing, security, or application behavior.
02What is the basic difference between a switch and a router?
A switch forwards frames within a Layer 2 network; a router forwards packets between IP networks.
03Why do networks use multiple protocols?
Each protocol solves a different job, and the protocols work together as a stack.