[INFO] Creating configuration snippets
[CREATED] h1: initial,routing
[CREATED] h2: initial,routing
[CREATED] h3: initial,routing
[CREATED] h4: initial,routing
[CREATED] s1: initial,vlan
 [INFO] Executing initial configuration for node h1 (namespace clab-
          ml-17-h1)
 [INFO] Executing initial configuration for node h2 (namespace clab-
          ml-17-h2)
 [INFO] Executing initial configuration for node h3 (namespace clab-
          ml-17-h3)
 [INFO] Executing initial configuration for node h4 (namespace clab-
          ml-17-h4)
 [INFO] Executing initial configuration for node s1 (namespace clab-
          ml-17-s1)
 [INFO] Executing routing configuration for node h3 (namespace clab-
          ml-17-h3)
 [INFO] Executing routing configuration for node h1 (namespace clab-
          ml-17-h1)
 [INFO] Executing routing configuration for node h4 (namespace clab-
          ml-17-h4)
 [INFO] Executing routing configuration for node h2 (namespace clab-
          ml-17-h2)
 [INFO] Executing vlan configuration for node s1 (namespace clab-
          ml-17-s1)

Results of configuration script deployments
================================================================================
h1                           OK: 2   
h2                           OK: 2   
h3                           OK: 2   
h4                           OK: 2   
s1                           OK: 2   


The device under test is a simple bridge without an IP address in the red
or blue VLAN. Both VLANs are using the same IP prefix to identify potential
inter-VLAN leaking.

* h1 and h2 should be able to ping each other
* h3 and h4 should be able to ping each other
* h1 should not be able to reach h3