Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SBs Public IP Modification #216

Merged
merged 17 commits into from
Apr 23, 2024
Merged

SBs Public IP Modification #216

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
17 commits
Select commit Hold shift + click to select a range
1ee4d30
SB01 Public IP Modify
Vahan-Koloyan-Netris Apr 19, 2024
2cec359
SB02 Public IP Modify
Vahan-Koloyan-Netris Apr 19, 2024
772cbe6
SB04 Public IP Modify
Vahan-Koloyan-Netris Apr 19, 2024
8031484
SB05 Public IP Modify
Vahan-Koloyan-Netris Apr 19, 2024
9aa3d58
SB06 Public IP Modify
Vahan-Koloyan-Netris Apr 19, 2024
c8590be
SB07 Public IP Modify
Vahan-Koloyan-Netris Apr 19, 2024
ecf98f5
Fix Spaceing
Vahan-Koloyan-Netris Apr 19, 2024
3af67df
SB08 Public IP Modify
Vahan-Koloyan-Netris Apr 19, 2024
13dfef2
SB09 Public IP Modify
Vahan-Koloyan-Netris Apr 19, 2024
976e4cf
SB10 Public IP Modify
Vahan-Koloyan-Netris Apr 19, 2024
db82325
SB11 Public IP Modify
Vahan-Koloyan-Netris Apr 19, 2024
41ce0f1
SB12 Update Docs
Vahan-Koloyan-Netris Apr 22, 2024
61d342a
SB13 Public IP Modify
Vahan-Koloyan-Netris Apr 22, 2024
1880879
Fix Spaceing
Vahan-Koloyan-Netris Apr 22, 2024
d7ec89b
SB14 Public IP Modify
Vahan-Koloyan-Netris Apr 22, 2024
5ae718e
SB15 Public IP Modify
Vahan-Koloyan-Netris Apr 22, 2024
418165f
SB03 Public IP Modify
Vahan-Koloyan-Netris Apr 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion sandbox/Sandbox1/configurations.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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``

Expand Down
6 changes: 3 additions & 3 deletions sandbox/Sandbox1/creating-services.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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``
Expand Down Expand Up @@ -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.
Expand Down Expand Up @@ -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**".
Expand Down
2 changes: 1 addition & 1 deletion sandbox/Sandbox1/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
10 changes: 5 additions & 5 deletions sandbox/Sandbox1/sandbox-info.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion sandbox/Sandbox10/configurations.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,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.19 -p 30064``.
1. SSH to server **srv04-nyc**: ``ssh demo@216.172.128.210 -p 30064``.
2. Enter the password provided in the introductory e-mail.
3. Start a ping session: ``ping4 1.1.1.1``

Expand Down
6 changes: 3 additions & 3 deletions sandbox/Sandbox10/creating-services.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,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.19 -p 30065``.
1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.210 -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``
Expand Down Expand Up @@ -86,7 +86,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.19 -p 30065``.
1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.210 -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.
Expand Down Expand Up @@ -168,7 +168,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.19 -p 30065``.
1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.210 -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**".
Expand Down
2 changes: 1 addition & 1 deletion sandbox/Sandbox10/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
------------------------------------------------------------------------------------------------
Sandbox10 # Sandbox name Uppercase(case sensitive)
sandbox10 # Sandbox name Lowercase
166.88.17.19 # Hypervisor PUBLIC IP
216.172.128.210 # 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
Expand Down
10 changes: 5 additions & 5 deletions sandbox/Sandbox10/sandbox-info.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,11 +46,11 @@ Example pre-configured Netris services:

.. code-block:: shell-session

srv01-nyc: ssh demo@166.88.17.19 -p 30061
srv02-nyc: ssh demo@166.88.17.19 -p 30062
srv03-nyc: ssh demo@166.88.17.19 -p 30063
srv04-nyc: ssh demo@166.88.17.19 -p 30064
srv05-nyc: ssh demo@166.88.17.19 -p 30065
srv01-nyc: ssh demo@216.172.128.210 -p 30061
srv02-nyc: ssh demo@216.172.128.210 -p 30062
srv03-nyc: ssh demo@216.172.128.210 -p 30063
srv04-nyc: ssh demo@216.172.128.210 -p 30064
srv05-nyc: ssh demo@216.172.128.210 -p 30065


Kubernetes cluster
Expand Down
2 changes: 1 addition & 1 deletion sandbox/Sandbox11/configurations.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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@50.117.27.82 -p 30064``.
1. SSH to server **srv04-nyc**: ``ssh demo@216.172.128.211 -p 30064``.
2. Enter the password provided in the introductory e-mail.
3. Start a ping session: ``ping4 1.1.1.1``

Expand Down
6 changes: 3 additions & 3 deletions sandbox/Sandbox11/creating-services.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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@50.117.27.82 -p 30065``.
1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.211 -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``
Expand Down Expand Up @@ -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@50.117.27.82 -p 30065``.
1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.211 -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.
Expand Down Expand Up @@ -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@50.117.27.82 -p 30065``.
1. SSH to server **srv05-nyc**: ``ssh demo@216.172.128.211 -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**".
Expand Down
2 changes: 1 addition & 1 deletion sandbox/Sandbox11/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
------------------------------------------------------------------------------------------------
Sandbox11 # Sandbox name Uppercase(case sensitive)
sandbox11 # Sandbox name Lowercase
50.117.27.82 # Hypervisor PUBLIC IP
216.172.128.211 # 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
Expand Down
10 changes: 5 additions & 5 deletions sandbox/Sandbox11/sandbox-info.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,11 +49,11 @@ Example pre-configured Netris services:

.. code-block:: shell-session

srv01-nyc: ssh demo@50.117.27.82 -p 30061
srv02-nyc: ssh demo@50.117.27.82 -p 30062
srv03-nyc: ssh demo@50.117.27.82 -p 30063
srv04-nyc: ssh demo@50.117.27.82 -p 30064
srv05-nyc: ssh demo@50.117.27.82 -p 30065
srv01-nyc: ssh demo@216.172.128.211 -p 30061
srv02-nyc: ssh demo@216.172.128.211 -p 30062
srv03-nyc: ssh demo@216.172.128.211 -p 30063
srv04-nyc: ssh demo@216.172.128.211 -p 30064
srv05-nyc: ssh demo@216.172.128.211 -p 30065


Kubernetes cluster
Expand Down
Loading