From 1ee4d309b8a3d871301b213c4591754bc254c35c Mon Sep 17 00:00:00 2001 From: Vahan Koloyan Date: Fri, 19 Apr 2024 12:25:35 +0000 Subject: [PATCH] SB01 Public IP Modify --- sandbox/Sandbox1/configurations.rst | 2 +- sandbox/Sandbox1/creating-services.rst | 6 +++--- sandbox/Sandbox1/index.rst | 2 +- sandbox/Sandbox1/sandbox-info.rst | 10 +++++----- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/sandbox/Sandbox1/configurations.rst b/sandbox/Sandbox1/configurations.rst index 8b9b148fb..1db04fec7 100644 --- a/sandbox/Sandbox1/configurations.rst +++ b/sandbox/Sandbox1/configurations.rst @@ -70,7 +70,7 @@ You may also observe the functioning NAT rule in action by pinging any public IP * In a terminal window: - 1. SSH to server **srv04-nyc**: ``ssh demo@166.88.17.24 -p 30064``. + 1. SSH to server **srv04-nyc**: ``ssh demo@216.172.128.201 -p 30064``. 2. Enter the password provided in the introductory e-mail. 3. Start a ping session: ``ping4 1.1.1.1`` diff --git a/sandbox/Sandbox1/creating-services.rst b/sandbox/Sandbox1/creating-services.rst index 46f608371..6edc9c0f9 100644 --- a/sandbox/Sandbox1/creating-services.rst +++ b/sandbox/Sandbox1/creating-services.rst @@ -17,7 +17,7 @@ Let's create a V-Net service to give server **srv05-nyc** the ability to reach i * In a terminal window: - 1. SSH to server **srv05-nyc**: ``ssh demo@166.88.17.24 -p 30065``. + 1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.201 -p 30065``. 2. Enter the password provided in the introductory e-mail. 3. Type ``ip route ls`` and we can see **192.168.46.1** is configured as the default gateway, indicated by the "**default via 192.168.46.1 dev eth1 proto kernel onlink**" line in the output. 4. Start a ping session towards the default gateway: ``ping 192.168.46.1`` @@ -90,7 +90,7 @@ Now that we have both internal and external facing services, we can aim for our * In a terminal window: - 1. SSH to server **srv05-nyc**: ``ssh demo@166.88.17.24 -p 30065``. + 1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.201 -p 30065``. 2. Enter the password provided in the introductory e-mail. 3. Start a ping session towards any public IP address (e.g. ``ping 1.1.1.1``). 4. Keep the ping running as an indicator for when the service starts to work. @@ -176,7 +176,7 @@ Now that **srv05-nyc** can communicate with both internal and external hosts, le * In a terminal window: - 1. SSH to server **srv05-nyc**: ``ssh demo@166.88.17.24 -p 30065``. + 1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.201 -p 30065``. 2. Enter the password provided in the introductory e-mail. 3. Start a ping session: ``ping 1.1.1.1``. 4. If the previous steps were followed, you should see successful ping replies in the form of "**64 bytes from 1.1.1.1: icmp_seq=55 ttl=62 time=1.23 ms**". diff --git a/sandbox/Sandbox1/index.rst b/sandbox/Sandbox1/index.rst index 7d1105025..83af2bdac 100644 --- a/sandbox/Sandbox1/index.rst +++ b/sandbox/Sandbox1/index.rst @@ -7,7 +7,7 @@ ------------------------------------------------------------------------------------------------ Sandbox1 # Sandbox name Uppercase(case sensitive) sandbox1 # Sandbox name Lowercase - 166.88.17.24 # Hypervisor PUBLIC IP + 216.172.128.201 # Hypervisor PUBLIC IP 10.254.45.0/24 # *STATIC NO NEED TO REPLACE* MANAGEMENT Allocation/Subnet 10.254.46.0/24 # *STATIC NO NEED TO REPLACE* LOOPBACK Allocation/Subnet 192.168.44.0/24 # *STATIC NO NEED TO REPLACE* ROH Allocation/Subnet diff --git a/sandbox/Sandbox1/sandbox-info.rst b/sandbox/Sandbox1/sandbox-info.rst index 2c190e71a..df2fb7b10 100644 --- a/sandbox/Sandbox1/sandbox-info.rst +++ b/sandbox/Sandbox1/sandbox-info.rst @@ -49,11 +49,11 @@ Example pre-configured Netris services: .. code-block:: shell-session - srv01-nyc: ssh demo@166.88.17.24 -p 30061 - srv02-nyc: ssh demo@166.88.17.24 -p 30062 - srv03-nyc: ssh demo@166.88.17.24 -p 30063 - srv04-nyc: ssh demo@166.88.17.24 -p 30064 - srv05-nyc: ssh demo@166.88.17.24 -p 30065 + srv01-nyc: ssh demo@216.172.128.201 -p 30061 + srv02-nyc: ssh demo@216.172.128.201 -p 30062 + srv03-nyc: ssh demo@216.172.128.201 -p 30063 + srv04-nyc: ssh demo@216.172.128.201 -p 30064 + srv05-nyc: ssh demo@216.172.128.201 -p 30065 Kubernetes cluster