| This project assumes you are familiar with how to access GENI, design, deploy, login to, and test a topology of your own. Please refer to this tutorial if you need a refresher. |
|---|
Table of Contents
| Table of Contents | ||
|---|---|---|
|
...
As an example, suppose ethV is 20.0.1.1/24, ethW is 20.0.2.1/24, ethX is 20.0.1.2/24, and ethY is 20.0.1.2/24. If this is the case, then we can see that due to the /24 (i.e. 255.255.255.0) subnets, we have two distinct networks 20.0.1/24 and 20.0.2/24. Since ethV at 20.0.1.1 and ethX at 20.0.1.2 are on the same subnet, they must be the interfaces of the link between host-1 and switch. Likewise, because ethW at 20.0.2.1 and ethY at 20.0.2.2 are on the same subnet, they must be the interfaces of the link between host-2 and switch. By mapping the network interfaces and subnets, we can deduce the links between the VMs. It is important we do this now before we modify the network interfaces in the steps below.
 | You might have seen in Jacks where you can specify link IP addresses for each VM. We could have pre-assigned our IP addresses in Jacks to avoid having to figure out what network interfaces belong to what links. However, it's a good exercise to do it manually for simple topologies like ours. |
|---|
Setup Resources
On our host-1 and host-2, we will need to install iperf, which is the tool we will use to generate packets.
...