Test the IPv6 mesh boundary below Matter

Use real RPL border-router firmware to test two end devices before and after router loss, then separate mesh evidence from Matter claims.

Radio Remi — I trace the measured path and keep application claims separate., your practice guide

Radio Remi — I trace the measured path and keep application claims separate.
Predict the reading, then compare it with the measurement.

Contiki-NG Cooja

Third party Tool

Use real RPL border-router firmware to test two end devices before and after router loss, then separate mesh evidence from Matter claims.

Tier 2 · Free simulator · install required · No account

Version tested: Contiki-NG release/v4.9 c20b12cd, Cooja 4.8 (2022071901), Temurin 17.0.20.1, image sha256:b14d5afb0a2a852d9e72bbed607ead03f6ccc5f4d4dee44f0799110be2f4b609. Date: 2026-09-10.

Download the complete lab packet and follow README.md to run it in the free simulator.

Download the setup and run guide

Get the lab files

Download the complete packet for the simulation and its firmware, or download individual files for inspection. README.md gives the setup and run commands.

Steps

Screens captured against Contiki-NG Cooja Contiki-NG release/v4.9 c20b12cd, Cooja 4.8 (2022071901), Temurin 17.0.20.1, image sha256:b14d5afb0a2a852d9e72bbed607ead03f6ccc5f4d4dee44f0799110be2f4b609 on 2026-09-10; the tool may have moved on — the text steps are the contract.

  1. Step 1

    Do
    Open the CSC and let it pause at 89 seconds. Identify border router 1, routers 2/3 and non-forwarding end devices 4/5. Inspect the prefix event in expected-output.txt.
    You will see
    The real border-router firmware receives fd00::/64 through SLIP at 2.065 s. Both end devices have two-hop paths: source 4 through relay 3 and source 5 through relay 2.
    Why it matters
    A border-router network interface is below Matter. This uses RPL as an IPv6 mesh analogue; it does not run OpenThread or Matter.

  2. Step 2

    Do
    Filter Received ping reply|^-- Preferred parent|^-- Rank|^-- OF|^-- State|^-- MOP. Match the two pre-fault end-device pings to root 1.
    You will see
    End device 4 receives a reply in 112 ms and end device 5 in 104 ms; both replies have TTL 63.
    Why it matters
    A replying mesh endpoint establishes network reachability. It does not establish commissioning, a secure Matter session or cluster behavior.

  3. Step 3

    Do
    Bring Radio messages to the front, inspect From and To, then minimize that window to return to Network.
    You will see
    The actual run records radio exchanges among end devices, relay 2 and root 1, including control and background UDP traffic.
    Why it matters
    These are simulated 802.15.4/6LoWPAN frames, not Matter interaction or commissioning traces.

  4. Step 4

    Do
    Click Start/Pause to continue. The script removes the selected router at 90.065 s; let the run finish at 210 seconds.
    You will see
    Router 2 disappears. Source 5 changes to relay 3 at 101.046728 s; source 4 already used relay 3 and stays connected.
    Why it matters
    The test removes a router, then independently checks both end devices; one recovered arrow is not enough.

  5. Step 5

    Do
    Use the same ping/status filter. Compare each post-fault ping with its own baseline result.
    You will see
    End device 4 replies in 61 ms and end device 5 in 88 ms after the fault; both have TTL 63. TEST OK requires all four pre/post ping results and a new parent.
    Why it matters
    Source 5’s affected path recovered, while source 4 provides an unaffected comparison. These RTTs are bounded samples, not a Matter service-level guarantee.

  6. Step 6

    Do
    Filter Unknown ICMPv6|Received ping reply. Compare the successful ICMP probes with the unsupported UDP application, then fill the README Matter scope table.
    You will see
    The border-router example has no UDP echo service: root_received=0 and reply_clients=0. Background stock clients provoke ICMPv6 type-1 errors; successful pings do not erase this application boundary.
    Why it matters
    Matter commissioning, data model, fabrics, subscriptions, reset recovery and certification remain paper review items. Approve the mesh reachability test only.

Chapter checks

These questions refer to the chapter’s examples. Use the return links to review their answers.

  1. A Matter plug declares an optional feature in its PICS that the firmware does not correctly implement. What should happen before certification?

    Return to the chapter’s knowledge check

  2. A Matter device passes basic command tests, but after a factory reset it intermittently fails to establish an operational session on the same fabric. Which evidence is most important before certification readiness can be approved?

    Return to the chapter’s knowledge check

Return to Matter Testing and Certification · Browse Labs