docs: updated formatting on tutorial files
This commit is contained in:
parent
81230edac3
commit
cbc35b74f8
13 changed files with 73 additions and 39 deletions
|
@ -11,7 +11,7 @@ send a simple message and the server will log receipt of the message.
|
|||
Below is the list of files used for this tutorial.
|
||||
|
||||
* scenario.xml - 3 node CORE xml scenario file (wireless)
|
||||
* scenario.py - 3 node CORE gRPC python script (wireless)
|
||||
* scenario.py - 3 node CORE gRPC python script (wireless)
|
||||
|
||||
## Running with the XML Scenario File
|
||||
|
||||
|
|
|
@ -11,13 +11,13 @@ Below is the list of files used for this tutorial.
|
|||
|
||||
* movements1.txt - a NS2 mobility input file
|
||||
* scenario.xml - 3 node CORE xml scenario file (wireless)
|
||||
* scenario.py - 3 node CORE gRPC python script (wireless)
|
||||
* scenario.py - 3 node CORE gRPC python script (wireless)
|
||||
* printout.py - event listener
|
||||
|
||||
## Running with XML file using NS2 Movement
|
||||
|
||||
This section will cover running this sample tutorial using the XML scenario
|
||||
file, leveraging an NS2 file for mobility.
|
||||
file, leveraging an NS2 file for mobility.
|
||||
|
||||
* Make sure the **core-daemon** is running a terminal
|
||||
```shell
|
||||
|
@ -67,7 +67,8 @@ This section will cover running this sample tutorial using the XML scenario
|
|||
* You can now click play to start the session
|
||||
* Select the play button on the Mobility Player to start mobility
|
||||
* Observe movement of the nodes
|
||||
* Note that OSPF routing protocol is included in the scenario to build routing table so that routes to other nodes are known and when the routes are discovered, ping will work
|
||||
* Note that OSPF routing protocol is included in the scenario to build routing table so that routes to other nodes are
|
||||
known and when the routes are discovered, ping will work
|
||||
|
||||
<p align="center">
|
||||
<img src="/static/tutorial3/motion_from_ns2_file.png" width="80%" >
|
||||
|
|
|
@ -44,7 +44,8 @@ This section covers using the saved **scenario.xml** file to get and up and runn
|
|||
```shell
|
||||
ip route add 192.168.0.0/24 via 10.0.0.20
|
||||
```
|
||||
* On the Windows host using Windows command prompt with administrator privilege, add a route that uses the interface connected to the associated interface assigned to the RJ45 node
|
||||
* On the Windows host using Windows command prompt with administrator privilege, add a route that uses the interface
|
||||
connected to the associated interface assigned to the RJ45 node
|
||||
```shell
|
||||
# if enp0s3 is ssigned 192.168.0.6/24
|
||||
route add 10.0.0.0 mask 255.255.255.0 192.168.0.6
|
||||
|
@ -119,7 +120,8 @@ This section covers leveraging the gRPC script to get up and running.
|
|||
```shell
|
||||
ip route add 192.168.0.0/24 via 10.0.0.20
|
||||
```
|
||||
* On the Windows host using Windows command prompt with administrator privilege, add a route that uses the interface connected to the associated interface assigned to the RJ45 node
|
||||
* On the Windows host using Windows command prompt with administrator privilege, add a route that uses the interface
|
||||
connected to the associated interface assigned to the RJ45 node
|
||||
```shell
|
||||
# if enp0s3 is ssigned 192.168.0.6/24
|
||||
route add 10.0.0.0 mask 255.255.255.0 192.168.0.6
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue