debug-thread-network

Files (10)

• SKILL.md
• otbr-api.md · references/
• router-advertisements.md · references/
• thread-addressing.md · references/
• analyze_ra_packet.sh · scripts/
• decode_thread_netdata.py · scripts/
• ipv6_diagnostics.sh · scripts/
• query_otbr_api.sh · scripts/
• scan_for_otbr.sh · scripts/
• test_thread_connectivity.sh · scripts/

SKILL.md (first lines)

# Debug Thread Network

Comprehensive toolkit for debugging Thread mesh networks and OpenThread Border Routers.

## Quick Start

Run the main diagnostic script to test connectivity and gather network information:

```bash
scripts/test_thread_connectivity.sh <border-router-ip>
```

Example:
```bash
scripts/test_thread_connectivity.sh 192.168.50.104
```

## Core Scripts

### 1. Thread Connectivity Test (`scripts/test_thread_connectivity.sh`)

**Purpose**: Comprehensive connectivity test for Thread Border Router

**Usage**:
```bash
scripts/test_thread_connectivity.sh <border-router-ip>
```

**What it tests**:
- ICMP reachability (ping)
- HTTP REST API accessibility
- IPv6 Router Advertisement reception
- Thread network status
- Border Router configuration

**Output**: Summary report with pass/fail status for each test

### 2. IPv6 Diagnostics (`scripts/ipv6_diagnostics.sh`)

**Purpose**: Gather complete IPv6 configuration and routing information

**Usage**:
```bash
scripts/ipv6_diagnostics.sh [interface]
```

**Collects**:
- IPv6 addresses on all interfaces
- IPv6 routing table
- Neighbor Discovery cache
- Router Advertisement prefixes
- Default routers

**Output**: Formatted diagnostic report

### 3. Border Router API Query (`scripts/query_otbr_api.sh`)

**Purpose**: Query OpenThread Border Router REST API endpoints

**Usage**:
```bash
scripts/query_otbr_api.sh <border-router-ip> [port]
```

**Endpoints queried**:
- `/get_properties` - Network properties
- `/node_information` - Node details
- `/topology` - Network topology
- `/diagnostics` - Full diagnostic info
- `/node/dataset/active` - Thread credentials

**Output**: JSON responses from each endpoint

### 4. Thread Network Data Decoder (`scripts/decode_thread_netdata.py`)

**Purpose**: Decode Thread Network Data hex string into human-readable format

**Usage**:
```bash
scripts/decode_thread_netdata.py <netdata-hex>
```

Or pipe from API:
```bash
curl -s http://192.168.50.104/diagnostics | \
  jq -r '.[0].NetworkData' | \
  scripts/decode_thread_netdata.py
```

**Decodes**:
- Prefix TLVs with IPv6 prefixes
- Border Router sub-TLVs with flags
- Has Route sub-TLVs
- Service TLVs

**Output**: Structured TLV analysis with prefix flags

### 5. RA Packet Analyzer (`scripts/analyze_ra_packet.sh`)

**Purpose**: Capture and analyze Router Advertisement packets

**Usage**:
```bash
sudo scripts/analyze_ra_packet.sh <interface>
```

**Captures**:
- Router Advertisement packets
- Prefix Information Options (PIO)
- Route Information Options (RIO)
- Router lifetime and flags

**Output**: Parsed RA packet details

## Common Workflows

### Workflow 1: Initial Border Router Discovery

When you know the network but not the border router IP:

From emliunix/home.conf, GPL-3.0.

More from emliunix/home.conf