This guide shows how (and when) to daisy‑chain network equipment such as modems, switches, and WiFi extenders (access points). It also compares daisy‑chain vs star topology, and gives wiring recipes and checklists you can apply immediately.
Key idea: Daisy‑chaining can be fine for small or linear layouts, but a star (or tree) topology is usually faster to troubleshoot, easier to scale, and more resilient. Use a daisy‑chain only when a star isn’t practical, and keep the chain short.
Note: If you have a professional IT team, follow their recommendation instead as every network can be different.
1) Network Chains
A) Modem → Switch → Access Point
Use this only if your modem is actually a gateway (modem+router). If it’s a pure modem, you must place a router between the modem and the switch.
Note Plugzio Cellular modems act as both a modem and a router.
Recommended recipe (typical home):
Modem/Router (gateway) → Switch → AP(s) via Ethernet (PoE if available).
Put each AP in AP/Bridge mode (no NAT/DHCP). Give all APs the same SSID/passphrase, different channels.
Note: If you are using a Plugzio extender, these extenders are preconfigured, just connect and power them via ethernet to expand your network.
Keep uplinks fast (e.g., 1G or faster) and runs ≤100 m (or 300ft) per Ethernet segment.
If you segment traffic (e.g., Guest, IoT), trunk VLANs from the router/core switch to the AP ports.
When it makes sense: Small offices or homes where the gateway sits near a closet switch and you’re wiring one or more APs.
Watch‑outs: If the “modem” is not a gateway, your LAN devices may fail to obtain IP addresses or end up exposed to the Internet. Always verify the first device after the modem is a router/gateway.
B) Modem → Switch → Switch + Access Point → Access Point
Think of this as a small tree: a “core” switch feeds an “access” switch, which feeds APs. This is common when rooms are chained by existing cabling.
Recommended recipe:
Modem/Router (gateway) → Core switch → Access switch → AP(s).
Enable RSTP (Rapid Spanning Tree) on managed switches to prevent loops and speed recovery.
Keep the chain shallow (ideally ≤2 switches deep). If you need many closets, prefer a star from the core switch to each access switch.
Use fiber or multi‑gig uplinks for the switch‑to‑switch links if AP density is high.
Consider switch stacking at the core for single‑point management and redundancy (vs many individual daisies).
Plan PoE budget: total switch PoE watts ≥ sum of max draw for all powered APs/cameras/phones.
When it makes sense: Hallway/warehouse/long building where pulling new home‑runs is expensive. Also fine as a temporary build‑out.
Watch‑outs: Long chains concentrate traffic on a few uplinks (bottlenecks), increase latency, and make troubleshooting harder. If you ever close a loop accidentally, you can melt the LAN without STP.
C) Modem → Access Point
Only valid if the “AP” is actually a Wi‑Fi router/gateway. A true AP expects an existing LAN and DHCP server. If you plug a pure AP into a pure modem, clients may connect to Wi‑Fi but won’t get proper IPs or firewalling.
Corrected recipe: Modem → Router/Gateway → (optional) Switch → AP(s).
2) Topologies at a glance
Star (hub‑and‑spoke)
What: Every switch/AP home‑runs to a central switch/router.
Pros: Easy to scale and troubleshoot; single link failures affect only that spoke; high aggregate throughput.
Cons: More cabling to a central point; requires a larger core switch.
Daisy‑chain (linear/bus)
What: Devices connect in a line: A→B→C→D.
Pros: Less cabling, fast to deploy, useful in linear spaces.
Cons: A single upstream failure down the line brings multiple nodes down; upstream links become bottlenecks; harder to diagnose; greater risk if loops appear.
Tree (recommended for multi‑switch LANs)
What: A controlled hierarchy: core → distribution (optional) → access. Functionally a “multi‑star.”
Pros: Modular, resilient, and scalable; naturally limits failure domains; aligns with enterprise design practices.
Cons: Slightly more planning and cabling than a quick daisy chain.
3) Best‑practice checklist (wired)
Put a router after the modem. The router/gateway should perform NAT, firewall, and DHCP.
Prefer star (or tree) to long daisies. If you must daisy‑chain, keep it short (1–2 downstream switches) and use fast uplinks.
Enable RSTP (Rapid Spanning Tree) on managed switches; avoid unmanaged switches in complex topologies.
Avoid loops. Never connect two access switches together unless you know how to do redundant uplinks with STP/stacking.
Use link aggregation (LACP) for higher uplink capacity where supported.
Mind cable limits: Copper Ethernet runs ≤100 m (328 ft). Use fiber for longer or for EMI‑noisy runs.
Plan PoE power budget before hanging APs/cameras/phones; leave ~20% headroom.
VLANs for segmentation (e.g., Guest, IoT, Cameras). Trunk only where needed; keep access ports simple.
Document ports & labels. Save a diagram and port map; it pays back on Day 2.
4) Best‑practice checklist (Wi‑Fi)
Wire APs whenever possible. Wired backhaul beats wireless mesh for throughput and stability.
One SSID per use‑case (e.g., Corp, Guest). Use WPA2/WPA3 as supported. Disable WPS.
Channel planning: 2.4 GHz: use 1/6/11 non‑overlapping; 5 GHz: use non‑overlapping 20/40/80 MHz channels appropriate to density.
Power tuning: Don’t blast max TX power; aim for even cell sizes and roaming.
Roaming features: Enable 802.11k/v/r if your clients support them.
Mesh only if you must. If you do, minimize hops (1–2 max) and ensure strong SNR between nodes.
5) Wiring recipes you can copy
Recipe 1 — Gateway with single switch and APs
ISP → Modem/Router (gateway) → Switch → AP1, AP2, …
Config:
Gateway: DHCP/NAT on; VLANs as required.
Switch: Managed preferred; RSTP on; trunks to AP ports if using VLAN SSIDs.
APs: AP/Bridge mode (no NAT/DHCP); same SSID & security; stagger channels.
Recipe 2 — Small two‑switch tree with APs
ISP → Modem/Router → Core Switch ===(uplink)===> Access Switch → APs
Config:
Use fiber or multi‑gig for the uplink if many APs/cameras hang off the access switch.
RSTP on everywhere; consider LACP for dual‑link uplinks.
Keep depth to two switches where possible.
Recipe 3 — Correcting “Modem → AP”
ISP → Modem → Router/Gateway → (Switch) → AP
Config:
If your ISP gave you a gateway you can’t replace, consider Bridge Mode on the gateway or AP/Bridge Mode on your own router to avoid double NAT.
6) Pros & cons — Daisy‑chain vs Star
Daisy‑chain
✅ Simple cabling in linear spaces
✅ Fewer long home‑run cables; can be cheaper to install
❌ Upstream links are bottlenecks for everything downstream
❌ One cut upstream affects many devices
❌ Harder troubleshooting; more dependent on STP to stay loop‑free
❌ Usually poorer scalability (adds latency/hops per added switch)
Star (or Tree)
✅ Better performance headroom; issues isolated to a spoke
✅ Easier to add/retire devices and closets
✅ Aligns with enterprise designs (core/distribution/access)
❌ Requires central cabling and a beefier core switch
7) Security & reliability notes
Keep the firewall/router at the network edge; don’t expose APs or switches directly to the WAN.
Update firmware on routers/APs/switches; change default passwords; use WPA2/WPA3.
Consider redundant Internet (dual‑WAN) if uptime matters.
Back up switch/router configs.
8) Practical limits & rules of thumb
Switch depth: In small networks aim for ≤2 switches deep from the core; deep chains are fragile. Enterprise STP defaults assume a limited “diameter” (number of bridges between any two hosts).
AP density: One AP per ~75–125 m² (800–1,350 ft²) as a starting point, adjusted for walls/clients.
PoE: Budget max draw, not averages; leave headroom for cold‑start inrush.
9) Troubleshooting quick‑checks
If Wi‑Fi shows “connected, no Internet,” verify the router is actually between modem and LAN; check DHCP leases.
If parts of the network drop when one switch reboots, you likely daisy‑chained too deeply or lack RSTP.
Broadcast storms or sudden slowness after “adding one more cable” → you probably created a loop. Unplug the last change and enable RSTP.