Changes between Version 17 and Version 18 of CmuLab

Timestamp:

04/24/09 09:37:20 (15 years ago)

Author:

dga@cs.cmu.edu

Comment:

--

CmuLab

@@ -83 +83 @@
   '''IP'''
 
-    The CMU Lab internal cluster and Wireless Emulator are NATted behind 128.2.222.223.  The Lab will connect to the nearest ProtoGENI node on Internet2 via GRE tunnel (unless an economical VLAN strategy can be found).  CMU accesses the Internet via 3ROX operated by PSC using a link with over 500 Mbps spare capacity.  3ROX is not on I2's DCN.
+    The nodes in this project present a number of challenges for connectivity:  The CMU Lab internal cluster and Wireless Emulator are NATted behind 128.2.222.223.  Several of the HomeNet nodes are deployed behind either NATs or firewalls that block most non-TCP communication other than DNS.  As a result, these nodes use OpenVPN tunnels to reach a tunnel endpoint node at CMU.  This tunnel endpoint will have a globally-reachable IP address that can be used for GRE tunnels (and, perhaps an L2 tunnel if an economical L2 VLAN strategy can be found).  The tunnel endpoint and any globally-reachable nodes installed later will connect to the ProtoGENI node on Internet2 using a GRE tunnel.  CMU accesses the Internet via 3ROX operated by PSC using a link with over 500 Mbps spare capacity.  3ROX is not on I2's DCN.
 
     !HomeNet nodes will tunnel (IP-in-IP) to CMU Control using OpenVPN.  The nodes will have addresses assigned by the user's ISP and may be assigned private addresses by !HomeNet.
@@ -89 +89 @@
   '''L2'''
 
-    802.11q tagged VLANS will be used establish QoS-enabled Ethernet VLANs between the CMU emulab cluster and the CMU wireless emulator.  ProtoGENI will provide dynamic VLAN establishment between Utah emulab clusters and CMU Lab.
+    802.11q tagged VLANS will be used to establish QoS-enabled Ethernet VLANs between the CMU emulab cluster and the CMU wireless emulator.  ProtoGENI will provide dynamic VLAN establishment between Utah emulab clusters and CMU Lab.
 
   '''Homenet Nodes'''