update interface-lagg test

tests/README.md

@@ -28,6 +28,8 @@ Some tests benefit from having a second network-interface available.
 
 You need to add a `opt1` dummy-interface named `TEST`. The assigned IPs do not matter.
 
+Add another interface and leave it unassigned (`vtnet2`).
+
 ### Internet access
 
 To perform some tests (system, ids) the test firewall needs to reach some public service:
@@ -55,6 +57,14 @@ The gateway tests will not work correctly if the LAN interface mismatches.
 
 You can provide your GW lan-if via env-vars: `TEST_FIREWALL_RULE_GRP_IF`
 
+### LAGG Interfaces
+
+The LAGG tests will not work correctly if the unassigned interface mismatches.
+
+You can provide your if via env-vars: `TEST_FIREWALL_LAGG_IF`
+
+And the count of existing LAGGs via `TEST_FIREWALL_LAGG_CNT`
+
 ----
 
 ## Run

tests/interface_lagg.yml

@@ -13,7 +13,8 @@
       target: 'interface_lagg'
 
   vars:
-    if_lag: "{{ lookup('ansible.builtin.env', 'TEST_FINTERFACE_LAGG_IF') | default('lan', true) }}"
+    if_lag: "{{ lookup('ansible.builtin.env', 'TEST_FIREWALL_LAGG_IF') | default('vtnet2', true) }}"
+    if_lag_ctn: "{{ lookup('ansible.builtin.env', 'TEST_FIREWALL_LAGG_CNT') | default('1', true) }}"
 
   tasks:
     - name: Listing