TP15: CRS326-Core als L3-Router aktiviert
- crs326-core nimmt Routing/DHCP/DNS/NAT/WAN/WireGuard von ap1 ueber. - L2-Portplan korrigiert (ap1 #15, Arris WAN #16, branch #8, Sonos #2/3/5/6, IoT #14, VLAN10-Access #11, VLAN1-Hybrid #3/7/9/10/12/17-24). - Backup-RSC gefixt (ether3-24 disabled) und via fixed-RSC eingespielt. - Gestagede L3-Config enabled in einem Rutsch. - Falsche statische Default-Route 0.0.0.0/0 -> 10.40.41.1 entfernt, WAN-DHCP via 90.146.33.177/24 aktiv. - SFP-Ports bleiben disabled (Stromersparnis). - ap1 ist L3-stillgelegt und wird in naechster Session reiner AP. Backup-Dateien (*.backup) und leases-export.json bleiben lokal. Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -31,17 +31,17 @@ routers:
|
||||
|
||||
# --- TP15 CRS326-Bring-up (2026-07-23) ---
|
||||
# Mgmt auf VLAN99. www=plain HTTP:80 (wie ap1/ap2) -> tls.enabled:false.
|
||||
# ENV in ~/.claude.json (mikromcp-Block): ROUTER_CRS326_CORE_USER/PASS, ROUTER_CRS326_BRANCH_USER/PASS.
|
||||
# Wird erst nach MCP-Neustart (neue Session) live; diese Session Verify via direktem REST-curl + ap1-ping.
|
||||
# ENV via ~/.secrets/exports.zsh: CRS326_CORE_USER/PASS, CRS326_BRANCH_USER/PASS.
|
||||
# Wird erst nach MCP-Neustart (neue Session) live; diese Session Verify via direktem REST-curl.
|
||||
crs326-core:
|
||||
host: "10.40.99.11"
|
||||
host: "10.40.41.211" # TEMP cutover mgmt IP until VLAN99 trunk through sw1 is live
|
||||
port: 80
|
||||
tls:
|
||||
enabled: false
|
||||
rejectUnauthorized: true
|
||||
credentials:
|
||||
source: "env"
|
||||
envPrefix: "ROUTER_CRS326_CORE"
|
||||
envPrefix: "CRS326_CORE"
|
||||
tags: ["bf", "switch", "core", "future-l3-router"]
|
||||
rosVersion: "7.19.5"
|
||||
|
||||
@@ -53,6 +53,6 @@ routers:
|
||||
rejectUnauthorized: true
|
||||
credentials:
|
||||
source: "env"
|
||||
envPrefix: "ROUTER_CRS326_BRANCH"
|
||||
envPrefix: "CRS326_BRANCH"
|
||||
tags: ["bf", "switch", "branch"]
|
||||
rosVersion: "7.19.5"
|
||||
|
||||
Reference in New Issue
Block a user