From 63a33e47234437951ffbeede830530dab090d985 Mon Sep 17 00:00:00 2001 From: Vasyl Saienko Date: Fri, 20 Feb 2026 10:13:49 +0200 Subject: [PATCH] fix: Update flag name that controls internet connectivity Allign documentation with hhfab tool cli, use --controls-restricted=false to control internet connectivity. --- docs/vlab/running.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/vlab/running.md b/docs/vlab/running.md index 08528127..ccb91c11 100644 --- a/docs/vlab/running.md +++ b/docs/vlab/running.md @@ -434,7 +434,7 @@ node and other VMs to watch the Fabric coming up and switches getting provisione ## Enable Outside connectivity from VLAB VMs By default, all test server VMs are isolated and have no connectivity to the host or the Internet. You can configure -enable connectivity using `hhfab vlab up --restrict-servers=false` to allow the test servers to access the Internet and +enable connectivity using `hhfab vlab up --controls-restricted=false` to allow the test servers to access the Internet and the host. When you enable connectivity, VMs get a default route pointing to the host, which means that in case of the VPC peering you need to configure test server VMs to use the VPC attachment as a default route (or just some specific subnets).