From a5ad4f828027a4a10d8bd8969c9560ae48ac7083 Mon Sep 17 00:00:00 2001
From: staleycyn <45440075+staleycyn@users.noreply.github.com>
Date: Wed, 7 Feb 2024 09:37:54 -0800
Subject: [PATCH] Update LAB_05-Implement_Intersite_Connectivity.md

---
 .../Lab/LAB_05-Implement_Intersite_Connectivity.md            | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md b/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md
index 155f1915..5f71c46d 100644
--- a/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md	
+++ b/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md	
@@ -259,9 +259,9 @@ In this task, you want to control network traffic between the perimeter subnet a
     | --- | --- |
     | Route name | `PerimetertoCore` |
     | Destination type | **IP Addresses** |
-    | Destination IP addresses | `10.0.0.0/16` (core services virtual network) |
+    | Destination IP addresses | `10.0.1.0/16` (core services virtual network) |
     | Next hop type | **Virtual appliance** (notice your other choices) |
-    | Next hop address | `10.0.0.7` (future NVA) |
+    | Next hop address | `10.0.1.7` (future NVA) |
 
 1. Select **+ Add** when the route is completed. The last thing to do is associate the route with the subnet.