Christoph Emsenhuber
e8f58b0e5e
Sideboard-Test fuer ap1 (TP28) plus Umsetzung des TP25-Kanalplans in einem Zug am Manager (crs326-core): L2 (TEST-ether3-trunk-ap1-sideboard-2, bridge-vlan, committed): - ether3 zum AP-Trunk fuer ap1 hinzugefuegt (analog ether15/ether21) - Template mikrotik_routeros.j2 nachgezogen: ether3 in allen VLAN-Zeilen WLAN (TP25-kanalplan-ap1-live, wifi-channel, OFFEN bis 2026-09-10): - ch-5g-ap1: 5180 -> Frequenz-Liste 5260,5280 (DFS Band B, ch52/56) - ch-5g-ap2: 5220 -> Frequenz-Liste 5300,5320 (DFS Band B, ch60/64) - Neue Provisioning-Regeln fuer ap1 (radio-mac E5=5G, E6=2G), analog ap2/ap3 - remote-cap provision fuer ap1 und ap2 Live-Ergebnis (35 Clients an der Registration-Table, vorher 30): - ap1: 5260/5280 + 2412 (ch1), 9/9 Interfaces up - ap2: 5300/5320 + 2462 (ch11), 9/9 up - ap3: 5180 + 2437 (ch6), unveraendert - Keine 5-GHz-Kollisionen mehr, 2,4-GHz sauber auf ch1/6/11 Follow-up in naechster Session: In-situ-Messungen an den Aufstellorten; bei ok Template auf Frequenz-Listen + ap1-Provisioning-Regeln erweitern und die offene Akte committen. Snapshot fuer Rollback liegt bereit. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
8 lines
754 B
Plaintext
8 lines
754 B
Plaintext
/interface bridge vlan set [find where vlan-ids=10 and !dynamic] tagged=ether1,ether3,ether8,ether13,ether15
|
|
/interface bridge vlan set [find where vlan-ids=20 and !dynamic] tagged=ether3,ether8,ether13,ether15
|
|
/interface bridge vlan set [find where vlan-ids=30 and !dynamic] tagged=ether1,ether3,ether8,ether15
|
|
/interface bridge vlan set [find where vlan-ids=40 and !dynamic] tagged=ether1,ether3,ether8,ether13,ether15 untagged=ether2,ether4,ether5
|
|
/interface bridge vlan set [find where vlan-ids=50 and !dynamic] tagged=ether1,ether3,ether8,ether15
|
|
/interface bridge vlan set [find where vlan-ids=90 and !dynamic] tagged=ether1,ether3,ether8,ether15
|
|
/interface bridge vlan set [find where vlan-ids=99 and !dynamic] tagged=ether3,ether8,ether15,bridge
|