Border Router
Understanding Border Routers
The Border Router bridges two fundamentally different network domains: the constrained mesh (low data rate, battery-powered, lossy links) and the backbone (high bandwidth, reliable). It adapts packet sizes (6LoWPAN fragments 1280-byte IPv6 packets into 127-byte 802.15.4 frames), manages routing tables, and provides Network Address Translation where needed.
Thread networks support multiple Border Routers for redundancy. If one fails, mesh traffic automatically routes through another. The OpenThread Border Router (OTBR) project provides a full reference implementation running on Raspberry Pi or similar platforms.
6LoWPAN: Header compression (40B → 2-7B)
Fragmentation: 1280B IPv6 → 127B 802.15.4
Service Discovery: mDNS/DNS-SD proxy
Security: Thread commissioning, key management
IoT Gateway Architecture Comparison
| Protocol | Gateway Type | IP Native | Layer |
|---|---|---|---|
| Thread | Border Router | Yes (IPv6) | L3 |
| Zigbee | App Gateway | No | L7 |
| Z-Wave | Hub/Controller | No | L7 |
| Wi-SUN | Border Router | Yes (IPv6) | L3 |
Frequently Asked Questions
Thread BR?
Routes IPv6 between Thread mesh (802.15.4) and Wi-Fi/Ethernet. 6LoWPAN compression, multicast, service discovery. OTBR is open-source ref.
BR vs Gateway?
BR: Layer 3, IP routing (Thread, Wi-SUN). Gateway: Layer 7, protocol translation (Zigbee, Z-Wave). Thread is IP-native.
Matter?
Matter-over-Thread requires BR. HomePod, Nest Hub, Echo include Thread BR. Enables mesh devices to reach IP network and cloud.