القائمة
OpenWrt bridge ordering and WAN detection patterns. Use when managing Proxmox bridges, configuring WAN/LAN interfaces, or debugging OpenWrt network topology issues.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Project architecture and design principles for vm_builds Ansible project. Includes bake vs configure patterns, two-role service model, and deployment lifecycle.
Python code conventions. Functions return errors, .env parsing strips quotes, type hints required.
Proactive validation patterns to catch issues early, prevent debugging blind, and establish testing habits before problems escalate.
Update skills and rules when encountering new issues to prevent recurrence. Includes hard-fail patterns, code custodianship, and mandatory testing requirements.
LXC container provisioning and configuration patterns. Use when creating LXC services, managing container networking, or handling LXC template operations.
Molecule test performance optimization patterns. Template caching, NTP sync, pct_remote overhead, apt cache, selective rebuilds.
| name | openwrt-network-topology |
| description | OpenWrt bridge ordering and WAN detection patterns. Use when managing Proxmox bridges, configuring WAN/LAN interfaces, or debugging OpenWrt network topology issues. |
net0/eth0, remaining bridges as LAN ports. Most other VMs need only ONE LAN bridge.proxmox_bridges via the host's default route. NEVER hardcode a bridge as WAN. Override with openwrt_wan_bridge in host_vars only if auto-detection fails.net0/eth0:
_ordered_bridges: [_wan_bridge] + (proxmox_all_bridges | difference([_wan_bridge]) | sort)
vmbr0 always WAN. When the modem was on vmbr0, the Proxmox GUI became unreachable from LAN nodes.add_host as upstream_wan_prefixopenwrt_lan_subnet_candidates and pick first whose prefix differs from WANWhen OpenWrt is primary router, Proxmox host needs predictable IP on LAN bridge:
.2)ip addr add on LAN bridge (immediate, current session)ansible-bridges.conf from inet manual to inet dhcpNEVER use separate config file with iface <bridge> inet dhcp. It conflicts with inet manual stanza in bridges config.
NEVER leave stale IPs on non-LAN bridges in same subnet as LAN bridge. Two routes for same /24 on different bridges causes kernel to use wrong interface, breaking LAN VM connectivity.
To reach OpenWrt at default 192.168.1.1 during initial setup:
192.168.1.2) to WAN bridge on ProxmoxPrevious bug: excluded vmbr0 and tried connecting through vmbr1 (which had no IP in OpenWrt's default config).
On re-runs (VM already configured), the bootstrap IP 192.168.1.1 no longer exists — the VM's LAN is on 10.10.10.1. The openwrt_vm role MUST probe the configured LAN IP first and skip bootstrap if reachable.
OpenWrt LXC containers (bridge, mesh) boot with the default LAN IP 192.168.1.1 on br-lan. On WAN-bridged hosts, this IP is on the same L2 segment as the router VM's bootstrap target. The bridge LXC role MUST override the default LAN IP to the Proxmox-assigned container IP during provisioning.
Previous bug: Bridge LXC containers on bridge-1 and bridge-2 had 192.168.1.1 on the WAN bridge. When the openwrt_vm role added 192.168.1.2/24 to vmbr0 and SSHed to 192.168.1.1, it connected to the bridge container (1 eth interface) instead of the VM (3 interfaces). The configure role then failed with "No LAN devices found."