STEP_031F_LOAD_IFUP_VPN4_TABLE204 PASS_VPN4_TABLE204_RUNTIME
timestamp: 20260708-104100

Actions:
- /root/hmn/hmn-load-egress-slot.sh vpn4 /root/hmn/configs/awg1/20260708-042000/072-NL-Netherlands-Amsterdam-S8-78.31.250.16-awg1.conf load
- ifup vpn4
- ip route replace table 204 default dev vpn4 scope link

Generated:
- /tmp/step031f-load-ifup-vpn4-table204-20260708-104100.txt

Validation:
- load4_rc: 0
- ifup4_rc: 0
- route204_rc: 0
- ping_i_vpn4_rc: 0
- amneziawg_show_vpn4_rc: 0
- vpn4_runtime_lines: 1
- table203_default_lines: 1
- table204_default_lines: 1
- table200_default_vpn1_lines: 1
- rule203_204_lines: 0
- firewall_has_vpn3_vpn4: 0
- UCI pending change lines after: 0

Safe capture:
- REPORT=/opt/router-ops/captures/20260708-104116_step031f_vpn4_table204_runtime_20260708-104100/REPORT.txt
- SAFE_ARCHIVE=/opt/router-ops/captures/20260708-104116_step031f_vpn4_table204_runtime_20260708-104100.safe.tar.gz

Remote changes:
- VM101 /etc/config/network changed and committed for vpn4
- VM101 runtime interface vpn4 brought up
- VM101 runtime route table 204 only
- no ip rule added
- no firewall changes
- no production traffic switch

Rollback if needed:
- ifdown vpn4
- ip route flush table 204

Next:
- if PASS_VPN4_TABLE204_RUNTIME, STEP_031G can load+ifup vpn5 and table 205 with same isolated pattern