Changes between Version 51 and Version 52 of NikySandbox/TridentCommTut
- Timestamp:
- 06/07/12 13:09:26 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NikySandbox/TridentCommTut
v51 v52 180 180 181 181 = 3. Sending IP traffic = 182 For the rest of the tutorial we are going to use the whole topology that has been setup. The topology of your slice should look like: 183 We will start testing our setup by sending IP traffic between our hosts. 182 For the rest of the tutorial we are going to use the whole topology that has been setup. We will start testing our setup by sending IP traffic between our hosts. 184 183 185 184 == 3a. Login to host `R2` == 186 First login to the R2 host. To do that go t he Flack page and see what is the name of the machine185 First login to the R2 host. To do that go to the Flack page and see what is the name of the machine 187 186 188 187 [[Image(hostname.png, 20%)]] … … 215 214 }}} 216 215 217 From R2 you should also be able to ping PC Remote. The IP of PCRemoteis '''"10.1.1.2"'''.216 From R2 you should also be able to ping PC-WashDC. The IP of PC-WashDC is '''"10.1.1.2"'''. 218 217 {{{ 219 218 [inki@r2 ~]$ ping 10.1.1.2 -c 5 … … 225 224 }}} 226 225 227 Now let's try and ping the PC Remotefrom source. Login to source the same way you logged in to R2 and run:226 Now let's try and ping the PC-WashDC from source. Login to source the same way you logged in to R2 and run: 228 227 {{{ 229 228 ping 10.1.1.2 -c 5 -w 5 … … 254 253 = 4. Sending Layer 2 traffic = 255 254 GENI provides the capability of creating diverse, layer two topologies. The topology you have created includes connection at Layer 2. 256 The layer two part of your topology looks like this; the actual info of your topology might be different.257 255 258 256 In this exercise we are going to send layer 2 traffic between the hosts of our topology. 259 257 260 == 4a. Bring Down IP at r2==258 == 4a. Bring Down IP at `R2` == 261 259 First of all lets bring down the IP configuration from our hosts. At the terminal of r2 first run ifconfig to figure out which are the dataplane interfaces. Run : 262 260 {{{ … … 312 310 }}} 313 311 314 The two interface that are connected to source and PC Remoteare eth1 and eth2 respectively. To bring them down run :312 The two interface that are connected to source and PC-WashDC are eth1 and eth2 respectively. To bring them down run : 315 313 {{{ 316 314 sudo /sbin/ifconfig eth1 0.0.0.0 … … 336 334 }}} 337 335 338 == 4c. Enable Layer 2 forwarding at r2==339 If we try to ping PC Remotefrom source, the packets will not get through, since there is no340 router running at r2that will forward the packets along. For this tutorial we have installed341 click router on r2, and we are going to run a simple learning switch module. However you can336 == 4c. Enable Layer 2 forwarding at `R2` == 337 If we try to ping PC-WashDC from source, the packets will not get through, since there is no 338 router running at `R2` that will forward the packets along. For this tutorial we have installed 339 click router on `R2`, and we are going to run a simple learning switch module. However you can 342 340 imagine that you can implement a more complicated routing algorithm. 343 341 344 Lets generate the click configuration file. In the terminal of R2run:342 Lets generate the click configuration file. In the terminal of `R2` run: 345 343 {{{ 346 344 cd … … 352 350 sudo /usr/local/bin/click switch.click 353 351 }}} 354 The MAC address of PC Remoteis 00:02:B3:23:78:E5352 The MAC address of PC-WashDC is 00:02:B3:23:78:E5 355 353 356 354 Then from `source`, try to ping PCRemote … … 381 379 382 380 {{{ 383 omni.py deletesliver -a pg-utah sliceomni##384 omni.py deletesliver -a pg-ky sliceomni##381 omni.py deletesliver -a pg-utah <slicename> 382 omni.py deletesliver -a pg-ky <slicename> 385 383 }}} 386 384