MAC address vs IP address: What’s the difference?
MAC address vs IP address: One is a unique hardware identifier, while the other identifies a device's network connection. Learn more with BlueCat.
Read moreA local area network (LAN) is a network that connects computers, servers, printers and other devices within a limited physical area such as an office, building or campus, typically using Ethernet or Wi-Fi infrastructure with switches and access points that forward traffic locally based on MAC addresses. LAN design and operation depend critically on DHCP for address assignment and DNS for name resolution, with proper subnet planning, documentation and VLAN segmentation essential to avoid connectivity failures, address conflicts and broadcast storms that degrade performance across the organization. Security and reliability require accurate records of devices and addresses on each segment, device authentication before connection, monitoring for rogue endpoints, and logical segmentation through VLANs and access controls to contain lateral movement and limit exposure from compromised devices.
A LAN works by giving every device a network interface and connecting those interfaces through shared infrastructure that forwards frames locally. Devices on the same LAN reach each other directly, and traffic for other networks goes through a gateway.
Each device connects to a switch by Ethernet cable or to an access point over Wi-Fi. Devices are identified on the LAN by MAC addresses, and switches learn which MAC address is reachable through which port so they can forward frames only where needed. Devices also carry IP addresses, which are commonly assigned by DHCP and drawn from one or more subnets. When a device sends traffic to an address inside its own subnet, it delivers the frame directly. When the destination is outside the subnet, the device sends the traffic to its default gateway, usually a router, which forwards it toward other networks such as the internet or a remote site. A LAN can be divided into several virtual LANs (VLANs) on the same switches, using IEEE 802.1Q tagging, so that groups of devices are separated into distinct broadcast domains. Private address ranges from RFC 1918 are commonly used inside LANs, and network address translation lets those devices reach public networks.
A cabling mistake or a disabled spanning tree can create a Layer 2 loop. Broadcast frames then circulate endlessly, switch CPU and link utilization spike, and every device on the segment loses connectivity.
Short leases on busy guest or wireless segments can use up the scope. New devices fail to get an address and fall back to a self-assigned 169.254 address, while existing devices keep working.
A static address set inside a DHCP range, or a rogue device, produces an address conflict. Users see intermittent connection drops and ARP tables that flip between two MAC addresses.
A consumer router plugged into a wall port can answer DHCP requests with the wrong gateway or DNS server. Clients on that segment lose access or are sent to unintended resolvers, and DHCP snooping on switches is the usual control.
A wrong native VLAN or a missing VLAN on a trunk port leaves devices unable to reach their gateway. Ports show link up, but clients get no address or cannot leave the subnet.