Common Open Research Emulator
Find a file
2018-03-16 13:00:03 -07:00
daemon removed udp server due to the hackiness of its interactions with trying to re-use tcp code 2018-03-16 13:00:03 -07:00
doc added a convenience target for generating all documentation based on existing google code example, fixed a few issues with doc strings 2018-03-15 14:31:07 -07:00
gui updated links in core gui, fixed broken user list, all updated to https 2018-03-15 10:40:27 -07:00
netns updates to try and resync make dist to include current files 2018-03-14 10:43:25 -07:00
ns3 updates to try and resync make dist to include current files 2018-03-14 10:43:25 -07:00
scripts more corrections for daemon/scripts renaming 2018-03-15 11:56:30 -07:00
.editorconfig removed pip check, updated make files for using DESTDIR, removed usage of pip during make install 2017-08-21 12:55:51 -07:00
.gitignore fixed bad ignore for Makefiles under the kernel directory 2018-03-05 11:54:23 -08:00
ASSIGNMENT_OF_COPYRIGHT.pdf updated assignment of copyright file name to add to dist file 2017-12-18 09:28:41 -08:00
bootstrap.sh initial pass at removing bsd and code related to using bsd nodes 2018-03-07 12:54:19 -08:00
Changelog fix #137 2018-01-15 02:20:11 -08:00
configure.ac added a convenience target for generating all documentation based on existing google code example, fixed a few issues with doc strings 2018-03-15 14:31:07 -07:00
LICENSE updates to simplify tracking the copyright and an update to 2018, still room for improvement 2018-03-15 10:36:54 -07:00
Makefile.am added a convenience target for generating all documentation based on existing google code example, fixed a few issues with doc strings 2018-03-15 14:31:07 -07:00
README.md moved daemon/sbin to daemon/scripts 2018-03-15 11:30:11 -07:00
sonar-project.properties removed deprecated sonarqube setting to try and leverage new branch settings 2018-03-02 09:47:28 -08:00

CORE

CORE: Common Open Research Emulator

Copyright (c)2005-2018 the Boeing Company.

See the LICENSE file included in this distribution.

About

CORE is a tool for emulating networks using a GUI or Python scripts. The CORE project site (1) is a good source of introductory information, with a manual, screenshots, and demos about this software. The GitHub project (2) hosts the source repos, wiki, and bug tracker. There is a deprecated Google Code page (3) with the old wiki, blog, bug tracker, and quickstart guide.

  1. http://www.nrl.navy.mil/itd/ncs/products/core
  2. https://github.com/coreemu/core
  3. http://code.google.com/p/coreemu/
  4. Official Documentation

Building CORE

To build this software you should use:

./bootstrap.sh
./configure
make
sudo make install

Note: You may need to pass the proxy settings to sudo make install: sudo make install HTTP_PROXY=

Here is what is installed with 'make install':

/usr/local/bin/core-gui
/usr/local/bin/core-daemon
/usr/local/bin/[vcmd, vnoded, coresendmsg, core-cleanup]
/usr/local/lib/core/*
/usr/local/share/core/*
/usr/local/lib/python2.6/dist-packages/core/*
/usr/local/lib/python2.6/dist-packages/[netns,vcmd].so
/etc/core/*
/etc/init.d/core

See the manual for the software required for building CORE.

Building Documentation

Being able to build documentation depends on help2man being installed.

Once that has been done you can run the following commands:

./bootstrap.sh
./configure
make html

Building Packages

Install fpm

http://fpm.readthedocs.io/en/latest/installing.html

Build package commands, DESTDIR is used for gui packaging only

./bootstrap.sh
./configure
make
mkdir /tmp/core-gui
make fpm DESTDIR=/tmp/core-gui

This will produce:

  • CORE GUI rpm/deb files
  • CORE ns3 rpm/deb files
  • CORE python rpm/deb files for SysV and systemd service types

Running CORE

First start the CORE services:

sudo /etc/init.d/core-daemon start

This automatically runs the core-daemon program. Assuming the GUI is in your PATH, run the CORE GUI by typing the following:

core-gui

This launches the CORE GUI. You do not need to run the GUI as root.

Support

If you have questions, comments, or trouble, please use the CORE mailing lists:

  • core-users for general comments and questions
  • core-dev for bugs, compile errors, and other development issues