# Absolut interim CAPsMAN migration patch
# Purpose:
# - prepare Absolut to take over CAPsMAN
# - preserve Courvoisier Guest DHCP during migration
# - allow temporary Guest traffic traversal through Absolut only during interim state
# - keep main/IoT traffic off Absolut during migration
# - fix Baker 2.4 provisioning symmetry
#
# Replace placeholders before import:
#   <ABSOLUT_IP>
#   <COURVOISIER_CAPSMAN_CERT>
#   <COURVOISIER_CAPSMAN_CA>

# Optional: verify current objects before applying
/caps-man datapath print detail
/caps-man provisioning print detail

# Use imported Courvoisier CAPsMAN identity on Absolut
/caps-man manager set enabled=yes certificate=<COURVOISIER_CAPSMAN_CERT> ca-certificate=<COURVOISIER_CAPSMAN_CA>

# Temporary Guest bridge on Absolut for interim migration only
/interface bridge add name=BWF.KitsNetG comment="TEMP guest bridge for CAPsMAN migration"

# Temporary Guest EoIP transport back to Courvoisier guest bridge
/interface eoip add name=EOIP.KitsNetG.to.Courvoisier local-address=<ABSOLUT_IP> remote-address=192.168.15.6 tunnel-id=120 comment="TEMP guest L2 backhaul to Courvoisier during CAPsMAN migration"
/interface bridge port add bridge=BWF.KitsNetG interface=EOIP.KitsNetG.to.Courvoisier

# Keep main and current IoT behavior local to avoid pushing that traffic through the CHR
/caps-man datapath set [find name="DP.KitsNet"] local-forwarding=yes
/caps-man datapath set [find name="DP.KitsNetI"] local-forwarding=yes

# TEMPORARILY central-forward Guest into the temporary Guest bridge on Absolut
/caps-man datapath set [find name="DP.KitsNetG"] local-forwarding=no bridge=BWF.KitsNetG

# Fix Baker 2.4 symmetry so it matches the intended SSID set of Able 2.4
/caps-man provisioning set [find comment="CAP baker 2.4Ghz"] slave-configurations=slave-KitsNetGN,slave-KitsNetIN

# Verification
/caps-man manager print
/caps-man datapath print detail
/interface eoip print detail
/interface bridge port print
/caps-man provisioning print detail