wiki:ConnectivityHome

Version 9 (modified by jwilliams@bbn.com, 9 years ago) (diff)

adapting ranges to account for Wisconsins IP address with Stanford's Point-to-Point VLAN

GENI Site Connectivity Cookbook

NOTE: This information is subject to change, but is actively maintained. Please email us with updates and corrections.

This site includes how-tos, background, and recommendations to help you set up GENI connections and experiments. It also lists detailed connection information about particular GENI sites that support OpenFlow, as a common reference for researchers to explore. Please feel free to add more information about your campus GENI connections and links to other related pages.

  • ConnectivityOverview - A high-level summary of what site connectivity looks like.
  • ConnectivityOptions - A matrix highlighting what connectivity options can be used to reach various campuses.
  • ConnectivityGuidelines - A cookbook-style how-to guideline for establishing end-to-end connectivity between two campuses.
  • ConnectivityTesting - A outline of test tools and procedures used when testing connectivity.

Site Listing

Site IP Ranges by Subnet

For initial Connectivity testing, a typical nomenclature is to use a 10.X.X.0/24 net with a VLAN ID encoded into the IP address. To save time allocating IP addresses the following range-by-subnet scheme can be used for initial connectivity and "path-finding" experiments and configurations.

Campus VLAN 3705 (example) First Host IP Last Host
Stanford 10.37.5.0/28 10.37.5.1 10.37.5.15
Clemson 10.37.5.16/28 10.37.5.17 10.37.5.31
Georgia Tech 10.37.5.32/28 10.37.5.33 10.37.5.47
Indiana U. 10.37.5.48/28 10.37.5.49 10.37.5.63
Princeton 10.37.5.64/28 10.37.5.65 10.37.5.79
Washington U. 10.37.5.80/28 10.37.5.81 10.37.5.95
BBN 10.37.5.96/28 10.37.5.97 10.37.5.111
--- 10.37.5.112/28 10.37.5.113 10.37.5.127
Wisconsin U. 10.37.5.128/28 10.37.5.129 10.37.5.143

Note that these IP addresses are allocated in blocks of /28 for consistency, this is not a subnet, all hosts in the /24 net should be able to ping one another by default. For example, a host at Clemson (10.37.5.17) should be able to ping a host at Washington (10.37.5.81).

This IP network (which corresponds to the VLAN itself) is meant for monitoring and testing of the connection, though host addresses within this IP network may be used in "small" experiments. Other IP networks following the same nomenclature maybe also be used on a given VLAN. Specific experiments may also designate other IP networks over time. This scheme lays the groundwork for initial connectivity only, it is expected other IP networks (as well as NON ip networks) will be devised in the future.

Campuses may assign other sites IPs from their range. This range-by-subnet scheme also allows for campuses to subnet the IP addresses not used for connectivity monitoring for additional traffic isolation. NOTE: More sites to be added soon.


Email us with questions and feedback on this page!