Access Points, Modems, ONTs and Firewalls

The edge of a network often looks like one plastic box, but that box may perform several independent jobs. A useful troubleshooting habit is to name the role that should act before blaming the physical device.

One box, many jobs

A home gateway may contain a wireless access point, Ethernet switch, router, firewall, DHCP service, and sometimes a modem or optical-network terminal. These roles can share one enclosure, but they answer different questions.

Think of a railway station containing platforms, ticket checks, route signs, and a connection to another railway company. Sharing one building does not make every job the same. The analogy stops at the fact that packets are processed electronically rather than carried by people.

Access points bridge wireless

An access point gives Wi-Fi clients access to a local network. In its basic role it bridges wireless traffic to a wired LAN. It handles wireless association and link-layer delivery; it does not automatically become the Internet router or security policy boundary.

The client interface might be labelled Wi-Fi, while the access point's wired side might be LAN, Ethernet, or an uplink port. Both sides can belong to the same IP network.

Modems and ONTs convert signals

A cable or DSL modem adapts customer network data to the provider's access technology. An ONT terminates the optical access link and presents a customer-facing handoff, commonly Ethernet. Their essential lesson role is conversion and provider termination—not choosing a destination route or applying user security policy.

Bridge mode exposes that separation clearly: the modem or ONT supplies the handoff while another device performs routing and firewall functions.

Routers and firewalls set boundaries

A router selects paths between IP networks. A firewall evaluates traffic crossing a security boundary and may permit or deny it using configured policy and session information. One home gateway often performs both roles, but routing and security remain different decisions.

This lesson does not teach firewall rule design, state tables, NAT, or VPN configuration. Those belong to later service and Network Security pathways.

Compare edge devices

Interactive edge-device journey

Choose a common layout and follow the packet through every interface. At each stage, the highlighted device explains what it does and the packet opens to show what remains inside.

Follow traffic across the network edge

Select a layout, then watch each device perform only its own role.

Choose an edge layout

Home fibreHome cableOffice wirelessBridge/modem-only mode

1. LaptopClient Wi-Fipacket→
2. Wi-Fi access pointWireless ↔ LAN bridge→
3. Router + firewallLAN ↔ WAN boundary→
4. ONTCustomer ↔ provider handoff→
5. ISP networkProvider edge

Local-link frame

IP packet

Application data

PreviousPlayNextRestartPlayback speed0.5×1×1.5×2×

Stage 1 of 6

The host creates application data

The laptop creates data for a remote service and passes it down to the network stack.

Inside the packet: Application data → IP packet → local-link frame

Laptop

Interface: Client Wi-Fi

This step does not change the packet's end-to-end IP addresses.