Changes between Version 10 and Version 11 of GENIExperimenter/Tutorials/GENIExperimentEngine/DesignSetup

Timestamp:

03/17/15 11:57:02 (9 years ago)

Author:

acb@cs.princeton.edu

Comment:

--

GENIExperimenter/Tutorials/GENIExperimentEngine/DesignSetup

@@ -38 +38 @@
 }}}
 
-Type '''ifconfig'''.  You should see an eth0 interface with an IP address in the 10.0.0.0/8 range, a ''private'' IP address.  From within a slicelet, you connect to the public Internet via NAT.
+Type '''ifconfig eth0'''.  You should see an eth0 interface with an IP address in the 10.0.0.0/8 range, a ''private'' IP address.  
 
-The nodes in your '''ssh-config''' file are Docker containers running on (virtual) hosts.  These hosts have ''public'' IP addresses that are routable from the commodity Internet, that's why you can login to the Docker containers of your slicelet.  A port on the public IP address (e.g., 49155) is forwarded to the SSH port (22) on the container's private IP address.  The '''ssh-config''' file contains the names of the virtual hosts and the port forwarding information.    
+{{{
+root@slice347:~# ifconfig eth0
+eth0      Link encap:Ethernet  HWaddr a6:24:c1:df:c7:09
+          inet addr:10.20.0.243  Bcast:0.0.0.0  Mask:255.255.0.0
+          inet6 addr: fe80::a424:c1ff:fedf:c709/64 Scope:Link
+          UP BROADCAST RUNNING  MTU:1500  Metric:1
+          RX packets:56555 errors:0 dropped:2 overruns:0 frame:0
+          TX packets:49525 errors:0 dropped:0 overruns:0 carrier:0
+          collisions:0 txqueuelen:1000
+          RX bytes:93890170 (93.8 MB)  TX bytes:8052865 (8.0 MB)
+}}}
 
-When you run a server on a node in your slicelet, it will listen on the private address.  By default it will only be visible to other nodes in your slicelet.  Docker provides facilities for exposing ports to the public Internet, but this topic is outside the scope of this tutorial.  
+This IP address is behind a NAT and not directly reachable from outside (i.e., from the Internet).  However all nodes in your slicelet can contact each other using the private addresses.
 
-''Note that, to complete this lab, you will later need to find both the ''public'' and ''private'' IP addresses for each node in the slicelet.''
+The nodes in your '''ssh-config''' file are Docker containers running on (virtual) hosts.  These hosts have ''public'' IP addresses that are routable from the Internet, that's why you can login to the Docker containers of your slicelet.  A port on the public IP address (e.g., 49155) is forwarded to the SSH port (22) on the container's private IP address.  The '''ssh-config''' file contains the names of the virtual hosts and the port forwarding information.    
+
+When you run a server on a node in your slicelet, it will listen on the private address, because that is the only one it can see.  By default it will only be visible to other nodes in your slicelet.  Docker provides facilities for exposing ports to the public Internet, but this topic is outside the scope of this tutorial.  
+
+''Note that later on you will need to find both the ''public'' and ''private'' IP addresses for each node in the slicelet.''
 
 ----