Lines Matching full:hs
16 # In other words, hosts hs-t100-1 and hs-t100-2 are connected through the IPv4
17 # L3 VPN of tenant 100 while hs-t200-3 and hs-t200-4 are connected using the
19 # is forbidden and thus, for example, hs-t100-1 cannot reach hs-t200-3 and vice
27 # example where, within the same domain of tenant 100, the host hs-t100-1 pings
28 # the host hs-t100-2.
30 # First of all, L2 reachability of the host hs-t100-2 is taken into account by
33 # When the host hs-t100-1 sends an IPv4 packet destined to hs-t100-2, the
45 # hs-t100-2 through the veth-t100 interface.
51 # for tenant 100. In this case, only hosts hs-t200-3 and hs-t200-4 are able to
57 # | hs-t100-1 netns | | hs-t100-2 netns |
101 # | hs-t200-3 netns | | hs-t200-4 netns |
325 # - host hs-1 is directly connected to the router rt-1;
326 # - host hs-2 is directly connected to the router rt-2.
332 # - host hs-3 is directly connected to the router rt-1;
333 # - host hs-4 is directly connected to the router rt-2.
338 # setup the IPv4 L3 VPN which connects the host hs-t100-1 and host
339 # hs-t100-2 within the same tenant 100.
343 # setup the IPv4 L3 VPN which connects the host hs-t200-3 and host
344 # hs-t200-4 within the same tenant 200.
386 log_test $? 0 "Hosts connectivity: hs-t${tid}-${hssrc} -> hs-t${tid}-${hsdst} (tenant ${tid})"
398 log_test $? 1 "Hosts isolation: hs-t${tidsrc}-${hssrc} -X-> hs-t${tiddst}-${hsdst}"
408 log_test $? 0 "Hosts connectivity: hs-t${tid}-${hssrc} -> gw (tenant ${tid})"