Run any Skill in Manus with one click

openwrt-dns-mesh-setup

Stars0

Forks0

UpdatedApril 10, 2026 at 00:14

OpenWrt encrypted DNS and mesh configuration patterns. Use when setting up https-dns-proxy, configuring WDS WiFi backhaul, or implementing DNS encryption on OpenWrt.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

krmorehead

krmorehead/vm_builds

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

name	openwrt-dns-mesh-setup
description	OpenWrt encrypted DNS and mesh configuration patterns. Use when setting up https-dns-proxy, configuring WDS WiFi backhaul, or implementing DNS encryption on OpenWrt.

OpenWrt DNS and Mesh Setup Rules

Encrypted DNS Integration

https-dns-proxy on OpenWrt auto-configures dnsmasq on install: it adds itself as upstream DNS server and restarts dnsmasq. No manual dnsmasq configuration needed for basic DoH setup.
The configure task only needs to:
- Install https-dns-proxy (with retries per network restart rules)
- Optionally configure specific DoH providers via UCI
- Verify DNS resolution works through the proxy

Mesh Networking Setup

Mesh satellite nodes use WDS AP/STA for wireless backhaul without requiring PCIe passthrough.
The iw package must be pre-installed in custom image for namespace-aware WiFi detection via netlink.

Container Networking Pattern

Container networking follows host topology:
- LAN hosts (router_nodes, lan_hosts) → OpenWrt LAN subnet (10.10.10.x), LAN bridge
- WAN hosts → private NAT bridge (vmbr_ct), 10.99.{host_id}.{offset}/24, DNS 8.8.8.8
- WAN containers are isolated on per-host /24 subnets — no IP collision risk

More from this repository

same repository

project-structure-rules

krmorehead/vm_builds

Project architecture and design principles for vm_builds Ansible project. Includes bake vs configure patterns, two-role service model, and deployment lifecycle.

2026-04-290

python-code-style

krmorehead/vm_builds

Python code conventions. Functions return errors, .env parsing strips quotes, type hints required.

2026-04-290

early-validation-patterns

krmorehead/vm_builds

Proactive validation patterns to catch issues early, prevent debugging blind, and establish testing habits before problems escalate.

2026-04-280

learn-from-mistakes

krmorehead/vm_builds

Update skills and rules when encountering new issues to prevent recurrence. Includes hard-fail patterns, code custodianship, and mandatory testing requirements.

2026-04-280

lxc-container-patterns

krmorehead/vm_builds

LXC container provisioning and configuration patterns. Use when creating LXC services, managing container networking, or handling LXC template operations.

2026-04-280

molecule-performance

krmorehead/vm_builds

Molecule test performance optimization patterns. Template caching, NTP sync, pct_remote overhead, apt cache, selective rebuilds.

2026-04-280

name	openwrt-dns-mesh-setup
description	OpenWrt encrypted DNS and mesh configuration patterns. Use when setting up https-dns-proxy, configuring WDS WiFi backhaul, or implementing DNS encryption on OpenWrt.

OpenWrt DNS and Mesh Setup Rules

Encrypted DNS Integration

https-dns-proxy on OpenWrt auto-configures dnsmasq on install: it adds itself as upstream DNS server and restarts dnsmasq. No manual dnsmasq configuration needed for basic DoH setup.
The configure task only needs to:
- Install https-dns-proxy (with retries per network restart rules)
- Optionally configure specific DoH providers via UCI
- Verify DNS resolution works through the proxy

Mesh Networking Setup

Mesh satellite nodes use WDS AP/STA for wireless backhaul without requiring PCIe passthrough.
The iw package must be pre-installed in custom image for namespace-aware WiFi detection via netlink.

Container Networking Pattern

Container networking follows host topology:
- LAN hosts (router_nodes, lan_hosts) → OpenWrt LAN subnet (10.10.10.x), LAN bridge
- WAN hosts → private NAT bridge (vmbr_ct), 10.99.{host_id}.{offset}/24, DNS 8.8.8.8
- WAN containers are isolated on per-host /24 subnets — no IP collision risk