afonso/core-extra
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

fix links

Browse source
This commit is contained in:
Huy Pham 2019-09-16 16:13:49 -07:00
parent b333859d86
commit 7c1f197774
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/emane.md
View file

@ -9,8 +9,8 @@ The Extendable Mobile Ad-hoc Network Emulator (EMANE) allows heterogeneous netwo
EMANE is developed by U.S. Naval Research Labs (NRL) Code 5522 and Adjacent Link LLC, who maintain these websites: EMANE is developed by U.S. Naval Research Labs (NRL) Code 5522 and Adjacent Link LLC, who maintain these websites:
* http://www.nrl.navy.mil/itd/ncs/products/emane * <http://www.nrl.navy.mil/itd/ncs/products/emane>
* http://www.adjacentlink.com/ * <http://www.adjacentlink.com/>
Instead of building Linux Ethernet bridging networks with CORE, higher-fidelity wireless networks can be emulated using EMANE bound to virtual devices. CORE emulates layers 3 and above (network, session, application) with its virtual network stacks and process space for protocols and applications, while EMANE emulates layers 1 and 2 (physical and data link) using its pluggable PHY and MAC models. Instead of building Linux Ethernet bridging networks with CORE, higher-fidelity wireless networks can be emulated using EMANE bound to virtual devices. CORE emulates layers 3 and above (network, session, application) with its virtual network stacks and process space for protocols and applications, while EMANE emulates layers 1 and 2 (physical and data link) using its pluggable PHY and MAC models.
@ -68,7 +68,7 @@ sudo ln -s /usr/local/share/emane /usr/share/emane
CORE supports custom developed EMANE models by way of dynamically loading user created python files that represent the model. Custom EMANE models should be placed within the path defined by **emane_models_dir** in the CORE configuration file. This path cannot end in **/emane**. CORE supports custom developed EMANE models by way of dynamically loading user created python files that represent the model. Custom EMANE models should be placed within the path defined by **emane_models_dir** in the CORE configuration file. This path cannot end in **/emane**.
Here is an example model with documentation describing functionality: Here is an example model with documentation describing functionality:
[Example Model](/daemon/examples/myemane/examplemodel.py) [Example Model](../daemon/examples/myemane/examplemodel.py)
## Single PC with EMANE ## Single PC with EMANE

2
docs/services.md
View file

@ -135,7 +135,7 @@ ideas for a service before adding a new service type.
### Creating New Service ### Creating New Service
1. Modify the [Example Service File](/daemon/examples/myservices/sample.py) 1. Modify the [Example Service File](../daemon/examples/myservices/sample.py)
to do what you want. It could generate config/script files, mount per-node to do what you want. It could generate config/script files, mount per-node
directories, start processes/scripts, etc. sample.py is a Python file that directories, start processes/scripts, etc. sample.py is a Python file that
defines one or more classes to be imported. You can create multiple Python defines one or more classes to be imported. You can create multiple Python