update of NRL URLs
This commit is contained in:
ahrenholz@gmail.com
parent
049b8465ab
commit
6c5704e5a9
8 changed files with 18 additions and 18 deletions
|
|
@ -2,7 +2,7 @@
|
||||||
|
|
||||||
= Contributing to CORE =
|
= Contributing to CORE =
|
||||||
|
|
||||||
*Project homepage*: [http://cs.itd.nrl.navy.mil/work/core/index.php]
|
*Project homepage*: [http://www.nrl.navy.mil/itd/ncs/products/core]
|
||||||
|
|
||||||
*Mailing list*: [http://pf.itd.nrl.navy.mil/mailman/listinfo/core-users] You can contribute by participating in discussions on the mailing list. Do you know the answer to a question someone posted there? Feel free to jump in with the answer.
|
*Mailing list*: [http://pf.itd.nrl.navy.mil/mailman/listinfo/core-users] You can contribute by participating in discussions on the mailing list. Do you know the answer to a question someone posted there? Feel free to jump in with the answer.
|
||||||
|
|
||||||
|
|
@ -17,4 +17,4 @@ This is manually synced with a private SVN repo at NRL with public nightly snaps
|
||||||
|
|
||||||
*How to submit patches*: enter a new issue on the [http://code.google.com/p/coreemu/issues/list bug tracker] and attach a patch, or email the [http://pf.itd.nrl.navy.mil/mailman/listinfo/core-dev development mailing list]. All submissions must use the same license as the rest of the project, the [http://www.opensource.org/licenses/bsd-license.php New BSD License]. Also see the below attribution guidelines.
|
*How to submit patches*: enter a new issue on the [http://code.google.com/p/coreemu/issues/list bug tracker] and attach a patch, or email the [http://pf.itd.nrl.navy.mil/mailman/listinfo/core-dev development mailing list]. All submissions must use the same license as the rest of the project, the [http://www.opensource.org/licenses/bsd-license.php New BSD License]. Also see the below attribution guidelines.
|
||||||
|
|
||||||
*Attribution*: for larger patches or rewrites, add your name to the `authors:` list at the top of the source file. Also include the license statement `See the LICENSE file included in this distribution.` and a Copyright (c) statement. Do not use `All rights reserved.` Do not add to the authors list for small modifications.
|
*Attribution*: for larger patches or rewrites, add your name to the `authors:` list at the top of the source file. Also include the license statement `See the LICENSE file included in this distribution.` and a Copyright (c) statement. Do not use `All rights reserved.` Do not add to the authors list for small modifications.
|
||||||
|
|
|
||||||
|
|
@ -6,7 +6,7 @@ EMANE is a mobile ad-hoc network emulation system that can be used in conjunctio
|
||||||
|
|
||||||
EMANE downloads, documentation, and other information:
|
EMANE downloads, documentation, and other information:
|
||||||
|
|
||||||
* http://cs.itd.nrl.navy.mil/work/emane/index.php
|
* http://www.nrl.navy.mil/itd/ncs/products/emane
|
||||||
|
|
||||||
= Scripting =
|
= Scripting =
|
||||||
See the [EEL] page for a description of the main scripting format used by EMANE for generating mobility and pathloss events.
|
See the [EEL] page for a description of the main scripting format used by EMANE for generating mobility and pathloss events.
|
||||||
|
|
@ -86,7 +86,7 @@ sudo ln -s /usr/local/share/emane /usr/share/emane
|
||||||
|
|
||||||
Setting the delay in the RF-PIPE MAC adds a transmission delay, not a propagation delay (as one might consider CORE link delays.) The tx delay is affected by the packet size and transmit rate:
|
Setting the delay in the RF-PIPE MAC adds a transmission delay, not a propagation delay (as one might consider CORE link delays.) The tx delay is affected by the packet size and transmit rate:
|
||||||
|
|
||||||
* *delay*: Defines the delay (usec) that is to be included in the transmission delay. The delay is added to the delay introduced by the bitrate defined above. (from http://labs.cengen.com/emane/doc/0.7.1/html/rfpipe.0.7.1.html)
|
* *delay*: Defines the delay (usec) that is to be included in the transmission delay. The delay is added to the delay introduced by the bitrate defined above. (from http://downloads.pf.itd.nrl.navy.mil/docs/emane/emane.pdf)
|
||||||
|
|
||||||
|
|
||||||
*Event generator*: produces events and is launched by the Event Service XML.<br>
|
*Event generator*: produces events and is launched by the Event Service XML.<br>
|
||||||
|
|
|
||||||
|
|
@ -6,7 +6,7 @@ The Common Open Research Emulator (CORE) is a tool for emulating networks. You c
|
||||||
|
|
||||||
== 2. Who produced CORE? ==
|
== 2. Who produced CORE? ==
|
||||||
|
|
||||||
CORE is derived from the [http://www.tel.fer.hr/imunes/ Integrated Multiprotocol Network Emulator/Simulator] (IMUNES) emulator. CORE was developed primarily by [mailto:jeffrey.m.ahrenholz@boeing.com Jeff Ahrenholz] from Boeing Research & Technology. Boeing Research & Technology has contributed CORE as an open source project, and the [http://cs.itd.nrl.navy.mil/products/ Naval Research Laboratory] (NRL) has graciously agreed to host CORE source code and mailing lists as part of a broader Mobile Network Modeling effort.
|
CORE is derived from the [http://www.tel.fer.hr/imunes/ Integrated Multiprotocol Network Emulator/Simulator] (IMUNES) emulator. CORE was developed primarily by [mailto:jeffrey.m.ahrenholz@boeing.com Jeff Ahrenholz] from Boeing Research & Technology. Boeing Research & Technology has contributed CORE as an open source project, and the [http://www.nrl.navy.mil/itd/ncs/products/ Naval Research Laboratory] (NRL) has graciously agreed to host CORE source code and mailing lists as part of a broader Mobile Network Modeling effort.
|
||||||
|
|
||||||
See the [http://downloads.pf.itd.nrl.navy.mil/docs/core/core-html/intro.html#prior-work Prior Work] and [http://downloads.pf.itd.nrl.navy.mil/docs/core/core-html/credits.html Acknowledgements] section in the CORE manual for more details.
|
See the [http://downloads.pf.itd.nrl.navy.mil/docs/core/core-html/intro.html#prior-work Prior Work] and [http://downloads.pf.itd.nrl.navy.mil/docs/core/core-html/credits.html Acknowledgements] section in the CORE manual for more details.
|
||||||
|
|
||||||
|
|
@ -36,4 +36,4 @@ CORE is open source; if you find CORE useful for your work, please contribute ba
|
||||||
|
|
||||||
== 8. Why doesn't ping work? ==
|
== 8. Why doesn't ping work? ==
|
||||||
|
|
||||||
There are a variety of reasons why one node in CORE cannot ping another. First start with the sample imn configs if you have a new CORE installation. Make sure that you have installed Quagga for routing as mentioned in the [Quickstart]. For new installations, check that iptables is not blocking traffic on the host bridges (`iptables -L`). For MDR wireless routers, you'll need to install OSPF MDR as described in the manual. It may be helpful to `tcpdump` along the expected path to determine connectivity and routing information.
|
There are a variety of reasons why one node in CORE cannot ping another. First start with the sample imn configs if you have a new CORE installation. Make sure that you have installed Quagga for routing as mentioned in the [Quickstart]. For new installations, check that iptables is not blocking traffic on the host bridges (`iptables -L`). For MDR wireless routers, you'll need to install OSPF MDR as described in the manual. It may be helpful to `tcpdump` along the expected path to determine connectivity and routing information.
|
||||||
|
|
|
||||||
|
|
@ -59,7 +59,7 @@ rm /vz/private/101/etc/resolv.conf
|
||||||
echo 127.0.0.1 localhost localhost.localdomain > /vz/private/101/etc/hosts
|
echo 127.0.0.1 localhost localhost.localdomain > /vz/private/101/etc/hosts
|
||||||
}}}
|
}}}
|
||||||
* CORE may be particular about which version of Quagga you use. The Quagga included with the CORE release is from [http://www.quagga.net Quagga.net] with the [http://hipserver.mct.phantomworks.org/ietf/ospf/ OSPFv3 MANET patch]. CORE uses the OSPFv3 MANET feature for wireless networks. If you only want wired networks or use custom configurations, you can use another version of Quagga. An RPM package for Quagga-manetmdr is installed in the `core-root` by default.
|
* CORE may be particular about which version of Quagga you use. The Quagga included with the CORE release is from [http://www.quagga.net Quagga.net] with the [http://hipserver.mct.phantomworks.org/ietf/ospf/ OSPFv3 MANET patch]. CORE uses the OSPFv3 MANET feature for wireless networks. If you only want wired networks or use custom configurations, you can use another version of Quagga. An RPM package for Quagga-manetmdr is installed in the `core-root` by default.
|
||||||
* [http://cs.itd.nrl.navy.mil/products/ NRL]'s protolib, nrlsmf, and mgen are installed in `core-root` by default
|
* NRL's protolib, nrlsmf, and mgen are installed in `core-root` by default
|
||||||
# move the staging area to core-root and create symlinks
|
# move the staging area to core-root and create symlinks
|
||||||
{{{
|
{{{
|
||||||
cd /vz/private
|
cd /vz/private
|
||||||
|
|
@ -117,4 +117,4 @@ The core-root RPM is maintained separately from the CORE program RPM, due to its
|
||||||
{{{
|
{{{
|
||||||
make core-root-rpm
|
make core-root-rpm
|
||||||
}}}
|
}}}
|
||||||
# the successful rpmbuild should result in `/usr/src/redhat/RPMS/core-root-n.n-1.i386.rpm`
|
# the successful rpmbuild should result in `/usr/src/redhat/RPMS/core-root-n.n-1.i386.rpm`
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,6 @@
|
||||||
#summary how to get MGEN running in CORE
|
#summary how to get MGEN running in CORE
|
||||||
|
|
||||||
MGEN is an open source traffic generator developed by NRL, available here: [http://cs.itd.nrl.navy.mil/work/mgen/ MGEN page at NRL]. You can use MGEN to easily create many different types of unicast or multicast IPv4/IPv6 traffic flows. Here is the [http://pf.itd.nrl.navy.mil/mgen/mgen.html MGEN Manual] for usage details.
|
MGEN is an open source traffic generator developed by NRL, available here: [http://www.nrl.navy.mil/itd/ncs/products/mgen MGEN page at NRL]. You can use MGEN to easily create many different types of unicast or multicast IPv4/IPv6 traffic flows. Here is the [http://downloads.pf.itd.nrl.navy.mil/docs/mgen/mgen.html MGEN Manual] for usage details.
|
||||||
|
|
||||||
= Installation =
|
= Installation =
|
||||||
|
|
||||||
|
|
@ -35,4 +35,4 @@ MGEN is an open source traffic generator developed by NRL, available here: [http
|
||||||
|
|
||||||
= Sample Scenario =
|
= Sample Scenario =
|
||||||
|
|
||||||
There is a `sample5-mgen.imn` scenario file included with CORE that demonstrates how to start a traffic flow from one node to another upon startup. You can find this file in the directory `core/gui/configs/sample5-mgen.imn` from the latest SVN snapshot tarball [http://downloads.pf.itd.nrl.navy.mil/core/source/nightly_snapshots/core-svnsnap.tgz here].
|
There is a `sample5-mgen.imn` scenario file included with CORE that demonstrates how to start a traffic flow from one node to another upon startup. You can find this file in the directory `core/gui/configs/sample5-mgen.imn` from the latest SVN snapshot tarball [http://downloads.pf.itd.nrl.navy.mil/core/source/nightly_snapshots/core-svnsnap.tgz here].
|
||||||
|
|
|
||||||
|
|
@ -22,7 +22,7 @@ Use your package manager to automatically install dependencies:<br>
|
||||||
yum localinstall core-gui-4.6-1.fc19.noarch.rpm
|
yum localinstall core-gui-4.6-1.fc19.noarch.rpm
|
||||||
}}}
|
}}}
|
||||||
|
|
||||||
Virtual networks usually require routing software. CORE automatically builds configs for the [http://www.quagga.net Quagga] routing suite. For wireless networks, CORE will generate OSPF MDR configs, for a modified version of Quagga available from [http://cs.itd.nrl.navy.mil/work/ospf-manet/ here].
|
Virtual networks usually require routing software. CORE automatically builds configs for the [http://www.quagga.net Quagga] routing suite. For wireless networks, CORE will generate OSPF MDR configs, for a modified version of Quagga available from [http://www.nrl.navy.mil/itd/ncs/products/ospf-manet here].
|
||||||
{{{
|
{{{
|
||||||
# Ubuntu - vanilla Quagga
|
# Ubuntu - vanilla Quagga
|
||||||
sudo apt-get install quagga
|
sudo apt-get install quagga
|
||||||
|
|
@ -77,7 +77,7 @@ Fedora:
|
||||||
This package list comes from
|
This package list comes from
|
||||||
[http://pf.itd.nrl.navy.mil/core/core-html/install.html here].
|
[http://pf.itd.nrl.navy.mil/core/core-html/install.html here].
|
||||||
|
|
||||||
You should also install Quagga for routing (`sudo apt-get install quagga` or `yum install quagga`), or some other routing package. For wireless MANET networks, CORE can build configs for [http://cs.itd.nrl.navy.mil/work/ospf-manet/ OSPF MDR].
|
You should also install Quagga for routing (`sudo apt-get install quagga` or `yum install quagga`), or some other routing package. For wireless MANET networks, CORE can build configs for [http://www.nrl.navy.mil/itd/ncs/products/ospf-manet OSPF MDR].
|
||||||
|
|
||||||
*Fedora users:* check the full [http://pf.itd.nrl.navy.mil/core/core-html/install.html#installing-from-packages-on-fedora-centos installation instructions], you need to also disable (or configure) SELINUX, sandbox, and iptables.
|
*Fedora users:* check the full [http://pf.itd.nrl.navy.mil/core/core-html/install.html#installing-from-packages-on-fedora-centos installation instructions], you need to also disable (or configure) SELINUX, sandbox, and iptables.
|
||||||
|
|
||||||
|
|
@ -133,4 +133,4 @@ core-gui
|
||||||
|
|
||||||
* *Do I need a custom kernel?* Not usually. Some disro's stock kernels may have issues, see [Linux] and [NamespaceKernels]. Some specific networking stack features may not support network namespaces, see [CustomKernels].
|
* *Do I need a custom kernel?* Not usually. Some disro's stock kernels may have issues, see [Linux] and [NamespaceKernels]. Some specific networking stack features may not support network namespaces, see [CustomKernels].
|
||||||
|
|
||||||
* *VMware image*<br>*Pros:* everything is already set up for you; one file to download. *Cons:* poor performance; for quick evaluation only.<br>[http://downloads.pf.itd.nrl.navy.mil/core/vmware-image/]<br>You can run CORE from within this pre-built VMware virtual machine with minimal setup. See the included vcore-`*`-README.txt in the zipfile for login information. _Note that you may experience decreased performance and timer issues, and there is the added confusion of virtualization within virtualization. If you decide to run in this mode, we suggest using SSH with X11 forwarding into the VCORE virtual machine, to mitigate the decreased performance of the virtual display._
|
* *VMware image*<br>*Pros:* everything is already set up for you; one file to download. *Cons:* poor performance; for quick evaluation only.<br>[http://downloads.pf.itd.nrl.navy.mil/core/vmware-image/]<br>You can run CORE from within this pre-built VMware virtual machine with minimal setup. See the included vcore-`*`-README.txt in the zipfile for login information. _Note that you may experience decreased performance and timer issues, and there is the added confusion of virtualization within virtualization. If you decide to run in this mode, we suggest using SSH with X11 forwarding into the VCORE virtual machine, to mitigate the decreased performance of the virtual display._
|
||||||
|
|
|
||||||
|
|
@ -4,7 +4,7 @@ _*Note:* this page is somewhat outdated, especially the latest release column!_
|
||||||
|
|
||||||
= Related Work used in CORE =
|
= Related Work used in CORE =
|
||||||
|| *URL* || *Name* || *Description* || *Latest release* ||
|
|| *URL* || *Name* || *Description* || *Latest release* ||
|
||||||
|| [http://labs.cengen.com/emane/ EMANE]<br> [http://cs.itd.nrl.navy.mil/work/emane/index.php EMANE at NRL] || EMANE || Extendable Mobile Ad-hoc Network Emulator can be used with CORE to provide higher-fidelity radio models || 2011 ||
|
|| [http://www.nrl.navy.mil/itd/ncs/products/emane/ EMANE] || EMANE || Extendable Mobile Ad-hoc Network Emulator can be used with CORE to provide higher-fidelity radio models || 2011 ||
|
||||||
||[http://www.tel.fer.hr/imunes/ IMUNES]<br>[http://imunes.net IMUNES 2nd page] || Integrated MUltiprotocol Emulator/Simulator || Tcl/Tk GUI drives FreeBSD virtual network stacks. The CORE GUI is based on this open source project from the University of Zagreb. || 10-07-2007 ||
|
||[http://www.tel.fer.hr/imunes/ IMUNES]<br>[http://imunes.net IMUNES 2nd page] || Integrated MUltiprotocol Emulator/Simulator || Tcl/Tk GUI drives FreeBSD virtual network stacks. The CORE GUI is based on this open source project from the University of Zagreb. || 10-07-2007 ||
|
||||||
|| [http://www.openvz.org OpenVZ] || OpenVZ (Virtuozzo) || Container-based virtualization for Linux. This is the open source offering of Parallels Virtuozzo Containers. CORE uses this software for networking emulation under Linux. || 2-10-2009 ||
|
|| [http://www.openvz.org OpenVZ] || OpenVZ (Virtuozzo) || Container-based virtualization for Linux. This is the open source offering of Parallels Virtuozzo Containers. CORE uses this software for networking emulation under Linux. || 2-10-2009 ||
|
||||||
|| [http://imunes.tel.fer.hr/virtnet/ VirtNet] || VirtNet (aka Vimage) || Project to virtualize FreeBSD 4.11/7.x/8.x network stacks. || 3-18-2009 ||
|
|| [http://imunes.tel.fer.hr/virtnet/ VirtNet] || VirtNet (aka Vimage) || Project to virtualize FreeBSD 4.11/7.x/8.x network stacks. || 3-18-2009 ||
|
||||||
|
|
@ -16,8 +16,8 @@ _*Note:* this page is somewhat outdated, especially the latest release column!_
|
||||||
==Network Emulators ==
|
==Network Emulators ==
|
||||||
|| *URL* || *Name* || *Description* || *Latest release* ||
|
|| *URL* || *Name* || *Description* || *Latest release* ||
|
||||||
||[http://www.opnet.com/news/press_releases/pr_2005/SITL_pr.html OPNET SITL] || OPNET System in the Loop || Emulation using the commercial OPNET simulator. || N/A ||
|
||[http://www.opnet.com/news/press_releases/pr_2005/SITL_pr.html OPNET SITL] || OPNET System in the Loop || Emulation using the commercial OPNET simulator. || N/A ||
|
||||||
||[http://cs.itd.nrl.navy.mil/work/mane/ MANE]|| Mobile Ad-hoc Network Emulator||NRL MANE is a mobile ad hoc network emulator that provides the ability to emulate dynamic link connectivity between emulated mobile nodes in a laboratory testbed. MANE runs on a network of servers, each of which hosts a number of client test nodes (TNs). The servers LAN approach support emulation scalability. ||1-30-2006 ||
|
||[http://www.nrl.navy.mil/itd/ncs/products/mane MANE]|| Mobile Ad-hoc Network Emulator||NRL MANE is a mobile ad hoc network emulator that provides the ability to emulate dynamic link connectivity between emulated mobile nodes in a laboratory testbed. MANE runs on a network of servers, each of which hosts a number of client test nodes (TNs). The servers LAN approach support emulation scalability. ||1-30-2006 ||
|
||||||
||[http://cs.itd.nrl.navy.mil/work/proteantools/mne.php MNE]||Mobile Network Emulator || The Mobile Network Emulator (MNE) is a simple, light-weight mobile network emulator that runs under Linux. The MNE works in a distributed manner, with each node controlling its own virtual position and blocking packets from other nodes as necessary.||9-12-2008 ||
|
||[http://www.nrl.navy.mil/itd/ncs/products/protean_tools/mne MNE]||Mobile Network Emulator || The Mobile Network Emulator (MNE) is a simple, light-weight mobile network emulator that runs under Linux. The MNE works in a distributed manner, with each node controlling its own virtual position and blocking packets from other nodes as necessary.||9-12-2008 ||
|
||||||
||[http://nsl.csie.nctu.edu.tw/nctuns.html NCTUNs] || NCTUNs Network Simulator and Emulator || A network simulator and emulator developed by National Chiao Tung University (NCTU) Taiwan and SimReal Inc., part open source? and partially commercially licensed|| ||
|
||[http://nsl.csie.nctu.edu.tw/nctuns.html NCTUNs] || NCTUNs Network Simulator and Emulator || A network simulator and emulator developed by National Chiao Tung University (NCTU) Taiwan and SimReal Inc., part open source? and partially commercially licensed|| ||
|
||||||
||[http://www.openchannelsoftware.org/projects/NetEmulator/ NetEmulator] || MiTRE NetEmulator||The NetEmulator is a Linux based collection of Open Source software programs that enable a PC, or a cluster of PC's, to emulate a wireless network in which links have limited capacity and packets get lost and delayed. ||2004 ||
|
||[http://www.openchannelsoftware.org/projects/NetEmulator/ NetEmulator] || MiTRE NetEmulator||The NetEmulator is a Linux based collection of Open Source software programs that enable a PC, or a cluster of PC's, to emulate a wireless network in which links have limited capacity and packets get lost and delayed. ||2004 ||
|
||||||
||[http://www.darkcornersoftware.com/nettion.html Nettion]||NETwork TestIng and Operational eNvironment ||Nettion is a suite of software tools for developing and executing network performance tests. Designed with an emphasis on testing mobile ad-hoc networks, Nettion can utilize either a local setup network, the test network, or compact flash memory. ||3-14-2006 ||
|
||[http://www.darkcornersoftware.com/nettion.html Nettion]||NETwork TestIng and Operational eNvironment ||Nettion is a suite of software tools for developing and executing network performance tests. Designed with an emphasis on testing mobile ad-hoc networks, Nettion can utilize either a local setup network, the test network, or compact flash memory. ||3-14-2006 ||
|
||||||
|
|
|
||||||
|
|
@ -3,7 +3,7 @@
|
||||||
= CORE and SDT3D =
|
= CORE and SDT3D =
|
||||||
|
|
||||||
SDT3D is a three-dimensional virtual globe GUI developed by NRL, based on NASA's [http://worldwind.arc.nasa.gov/java/ WorldWind Java SDK]. The primary SDT3D website is:
|
SDT3D is a three-dimensional virtual globe GUI developed by NRL, based on NASA's [http://worldwind.arc.nasa.gov/java/ WorldWind Java SDK]. The primary SDT3D website is:
|
||||||
* http://cs.itd.nrl.navy.mil/work/sdt/index.php
|
* http://www.nrl.navy.mil/itd/ncs/products/sdt
|
||||||
|
|
||||||
CORE can export its nodes and links so they appear in the 3D space. The Canvas Size and Scale dialog governs the origin latitude/longitude/altitude for the 2D canvas. Although the 2D canvas has a fixed altitude, EMANE-based mobility script could be used to move nodes around in three dimensions.
|
CORE can export its nodes and links so they appear in the 3D space. The Canvas Size and Scale dialog governs the origin latitude/longitude/altitude for the 2D canvas. Although the 2D canvas has a fixed altitude, EMANE-based mobility script could be used to move nodes around in three dimensions.
|
||||||
|
|
||||||
|
|
@ -93,4 +93,4 @@ cd ~/sdt3d
|
||||||
cd /home/$USER
|
cd /home/$USER
|
||||||
/opt/sdt/sdt3d.sh
|
/opt/sdt/sdt3d.sh
|
||||||
}}}
|
}}}
|
||||||
* you can copy the WorldWind map cache between systems (helpful if you do not always have an Internet connection), look in `~/var/cache/WorldWindData`
|
* you can copy the WorldWind map cache between systems (helpful if you do not always have an Internet connection), look in `~/var/cache/WorldWindData`
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue