61 | | '''system:topo:mf-groupX''' represents the group of 4 nodes and '''mf-groupX''' has to be replaced by the group id assigned to you. |
62 | | |
63 | | For example, '''mf-group1''' will load the image on nodes 'node1-1,node1-2,node2-1,node2-2' |
| 61 | ''system:topo:mf-groupX'' represents the group of 4 nodes and ''mf-groupX'' has to be replaced by the group id assigned to you. |
| 62 | |
| 63 | For example, ''mf-group1'' will load the image on nodes 'node1-1,node1-2,node2-1,node2-2' |
134 | | As seen above, the router is configured with both 'core' and 'edge' interfaces. The core interfaces connect routers towards the core of the network, while the edge interface enables hosts to connect and access the MobilityFirst network. |
135 | | |
136 | | Also seen above is the GNRS service related arguments that specify which server (IP and port) the router should use for in-network name resolution purpose, both for sending requests and to receive responses. By default it will listen on all interfaces and port 10001. |
| 136 | A few considerations on the defined applications: |
| 137 | |
| 138 | * As seen above, the router is configured with both 'core' and 'edge' interfaces. Different router configurations are available depending on the required functionality. In this case we use what we call a MobilityFirst Access Router, which has the particularity of having the core interfaces connected towards the core of the network, while the edge interface enables hosts to connect and access the MobilityFirst network. |
| 139 | |
| 140 | * For this basic setup, the GNRS has been configured to be running as a single instance, but in a larger experiment, it is designed to be a distributed system deployed at different locations. |
| 141 | |
| 142 | * Most of the client settings are located in a configuration file pre-loaded on the Orbit image. |