6LoWPAN Mesh-Under vs Route-Over Animation

Compare Layer 2 mesh forwarding with Layer 3 IP routing in constrained IoT networks

animation
6lowpan
routing
mesh-under
route-over
rpl
ipv6
802.15.4
Interactive 6LoWPAN routing workbench showing mesh-under and route-over packet flow, header overhead, per-hop processing, RPL/IP management trade-offs, frame budget checks, and mobile-safe reference material.

6LoWPAN Mesh-Under vs Route-Over Animation

Animation 6LoWPAN Routing trade-off

6LoWPAN Mesh-Under vs Route-Over

Compare where forwarding decisions happen in a constrained IPv6 mesh. Toggle the routing model, change hop count and header assumptions, then watch packet flow, frame budget, processing cost, and design guidance update together.

Route-overCurrent model
82 BEstimated frame
1.1 msPath processing
IP toolsBest reason
1Begin with the layer

Mesh-under forwards below IP with 802.15.4 addresses. Route-over forwards at IPv6 using routing state such as RPL.

2Track the header

Mesh-under adds a mesh addressing header. Route-over usually avoids that header but performs IP processing at each hop.

3Check the frame budget

IEEE 802.15.4 frames are small, so every address size, security option, and payload byte matters.

4Choose by operation

Latency, standards, diagnostics, topology change, and vendor interoperability usually matter more than one metric alone.

1. Source

Sensor creates an IPv6 packet.

2. Adapt

6LoWPAN compresses and frames it.

3. Forward

Each hop chooses the next node.

4. Header

Addressing and IPHC behavior differ.

5. Border

The border router connects to IPv6.

6. Decide

Pick the model that fits the network.

Animated Packet Path

A constrained sensor packet starts at the left and crosses a multi-hop 802.15.4 mesh toward the border router.

Stage Source
6LoWPAN routing model animation A six-node low-power mesh shows packet movement, active forwarding hops, header stack, frame budget, and decision metrics for mesh-under and route-over routing. Low-power 802.15.4 mesh Route-over: each router forwards using IPv6/RPL state S sensor A router B router C router D router BR border router packet Header stack at this hop MAC IPHC UDP data Route-over updates the MAC header and routes at IPv6 at each hop. Frame and processing check 82 of 127 bytes 1.1 ms route processing Frame fits; no fragmentation expected for this packet.

Experiment Controls

Switch the forwarding model, then change packet and path assumptions. The animation and formulas use classroom estimates so learners can compare the trade-off.

4
48 B
21 B
1.4 ETX
Route-overBest fit: standards and diagnostics

IPv6 routing gives operational visibility and works with standardized LLN routing such as RPL.

Frame OKFrame budget is comfortable

The packet stays under the 127-byte IEEE 802.15.4 maximum before lower-layer details are added.

Trade-offProcessing is higher, operation is easier

Route-over spends more CPU per hop, but radio airtime and sleep strategy often dominate energy.

Formula Trace

Calculating...

Reference Material

Forwarding Model Quick Reference
Mesh-under layer

Forwarding occurs below IPv6, typically using IEEE 802.15.4 source and destination addresses plus a 6LoWPAN mesh header.

Route-over layer

Every forwarding node acts as an IPv6 router and chooses the next hop from IP routing state.

RPL relationship

RPL is the IETF IPv6 routing protocol for low-power and lossy networks and is used with route-over designs.

Single subnet view

Mesh-under can make the low-power mesh appear like one IPv6 subnet to upper layers.

IP visibility

Route-over better supports IPv6 management and diagnosis because hops are IP routers.

Vendor risk

Mesh-under routing behavior is often implementation-specific, so interoperability must be checked carefully.

Header and Frame Budget Notes
802.15.4 limit

The physical frame maximum is 127 bytes, so MAC fields, security, mesh headers, compressed IP, UDP, and payload all compete for space.

Mesh header size

The RFC 4944 mesh header includes dispatch, hops-left, originator address, and final destination address. Short addresses produce a smaller header.

Route-over header

Route-over normally does not need the 6LoWPAN mesh addressing header, but it must process IP routing per hop.

IPHC behavior

Compressed IPv6 can stay compressed through mesh-under forwarding; route-over routers may decompress enough to make IP routing decisions.

Fragmentation risk

If the frame estimate exceeds 127 bytes, 6LoWPAN fragmentation may be needed, which adds reliability and reassembly concerns.

Estimates

The byte counts here are a teaching model. Real frame size depends on addressing, security, elided fields, UDP compression, and link-layer options.

Decision Checklist
Choose mesh-under when

The network is small, latency-sensitive, tightly controlled, and does not need standard IP routing visibility inside the mesh.

Choose route-over when

The network needs standard IPv6 routing, RPL-style topology management, diagnostics, scalability, or multi-vendor operation.

Ask about topology

Frequent join, leave, parent changes, and link-quality variation usually push the design toward standardized route-over routing.

Ask about operations

If field engineers need IP-level tools and predictable integration with routers, route-over is easier to operate.

Ask about latency

When the requirement is strict per-hop forwarding time in a controlled mesh, mesh-under may be attractive.

Avoid absolutes

The best answer depends on device class, stack support, certification needs, topology, and the product ecosystem.

Related Practice

6LoWPAN IPHC

Inspect how IPv6 and UDP headers are compressed before routing or forwarding.

 6LoWPAN Fragmentation

See what happens when a packet cannot fit in a single 802.15.4 frame.

 RPL DODAG

Explore how route-over networks build parent relationships and ranks.

 Book chapter

Read the full routing chapter with RPL concepts and worked examples.