Changes between Version 11 and Version 12 of DesktopExoGeni


Ignore:
Timestamp:
Mar 12, 2014 12:57:18 PM (6 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DesktopExoGeni

    v11 v12  
    257257Start up fedd.py on Node0 as before and run the same {{{fedd_create.py}}} command on DETER.
    258258
     259In addition to being able to contact Node0 directly, nodes in the DETER experiment now see a route to the 10.16.0.0/24 network:
     260
     261{{{
     262a:~$ ip route
     263default via 192.168.1.254 dev eth4
     26410.0.0.0/24 dev eth2  proto kernel  scope link  src 10.0.0.2
     26510.0.1.0/24 via 10.0.4.2 dev eth1  proto zebra  metric 20
     26610.0.2.0/24 via 10.0.4.2 dev eth1  proto zebra  metric 20
     26710.0.3.0/24 dev eth0  proto kernel  scope link  src 10.0.3.1
     26810.0.4.0/24 dev eth1  proto kernel  scope link  src 10.0.4.1
     26910.16.0.0/24 via 10.0.3.2 dev eth0  proto zebra  metric 20
     270192.168.0.0/22 dev eth4  proto kernel  scope link  src 192.168.1.188
     271192.168.252.0/22 via 192.168.1.254 dev eth4  proto zebra
     272}}}
     273
     274That route reaches Node1:
     275
     276{{{
     277a:~$ ping 10.16.0.2
     278PING 10.16.0.2 (10.16.0.2) 56(84) bytes of data.
     27964 bytes from 10.16.0.2: icmp_req=1 ttl=63 time=139 ms
     28064 bytes from 10.16.0.2: icmp_req=2 ttl=63 time=69.9 ms
     28164 bytes from 10.16.0.2: icmp_req=3 ttl=63 time=69.4 ms
     282}}}
     283
     284While some attention needs to be paid to routing if routing protocols are not run in ExoGENI, this facility allows a wide range of connectivity between the testbeds.