During first-run setup testing on the Caddy/SSL branch, the interface picker defaulted to selecting the same interface for both sides of the shaper.\n\nExpected behavior:\n- In a normal two-interface setup, the Internet-facing and Network/ISP-facing selections should not default to the same interface.\n- If exactly two eligible interfaces are present, setup should either choose distinct defaults or require explicit confirmation.\n- If only one eligible interface is present, setup should clearly enter single-interface / VLAN-on-a-stick mode rather than silently using the same interface for both roles.\n\nObserved behavior:\n- The setup UI defaulted both interface selections to the same interface.\n\nImpact:\n- A new install can proceed with an invalid or surprising topology if the operator does not notice the duplicated selection.\n- This is especially easy to miss during first-run setup and VM validation.\n\nNotes:\n- Found while verifying the package built from feat/1056_caddy after merging current develop.\n- This is not part of the Caddy/SSL scope, but should be tracked separately.
During first-run setup testing on the Caddy/SSL branch, the interface picker defaulted to selecting the same interface for both sides of the shaper.\n\nExpected behavior:\n- In a normal two-interface setup, the Internet-facing and Network/ISP-facing selections should not default to the same interface.\n- If exactly two eligible interfaces are present, setup should either choose distinct defaults or require explicit confirmation.\n- If only one eligible interface is present, setup should clearly enter single-interface / VLAN-on-a-stick mode rather than silently using the same interface for both roles.\n\nObserved behavior:\n- The setup UI defaulted both interface selections to the same interface.\n\nImpact:\n- A new install can proceed with an invalid or surprising topology if the operator does not notice the duplicated selection.\n- This is especially easy to miss during first-run setup and VM validation.\n\nNotes:\n- Found while verifying the package built from feat/1056_caddy after merging current develop.\n- This is not part of the Caddy/SSL scope, but should be tracked separately.