docs: removing references to imn, tcl, tk, tlv, and .core, removed unused icons

This commit is contained in:
Blake Harnden 2022-03-08 11:30:03 -08:00
parent f545726ed5
commit 3eed1a09fb
83 changed files with 196 additions and 987 deletions

View file

@ -10,17 +10,14 @@
* Nodes are created using Linux namespaces
* Links are created using Linux bridges and virtual ethernet peers
* Packets sent over links are manipulated using traffic control
* Controlled via the CORE GUI
* Provides both a custom TLV API and gRPC API
* Python program that leverages a small C binary for node creation
* Provides gRPC API
* core-gui
* GUI and daemon communicate over the custom TLV API
* GUI and daemon communicate over gRPC API
* Drag and drop creation for nodes and links
* Can launch terminals for emulated nodes in running sessions
* Can save/open scenario files to recreate previous sessions
* TCL/TK program
* coresendmsg
* Command line utility for sending TLV API messages to the core-daemon
* vnoded
* Command line utility for creating CORE node namespaces
* vcmd
* Command line utility for sending shell commands to nodes
@ -55,21 +52,10 @@ Nftables provides Ethernet frame filtering on Linux bridges. Wireless networks a
emulated by controlling which interfaces can send and receive with nftables
rules.
## Prior Work
The Tcl/Tk CORE GUI was originally derived from the open source
[IMUNES](http://imunes.net) project from the University of Zagreb as a custom
project within Boeing Research and Technology's Network Technology research
group in 2004. Since then they have developed the CORE framework to use Linux
namespacing, have developed a Python framework, and made numerous user and
kernel-space developments, such as support for wireless networks, IPsec,
distribute emulation, simulation integration, and more. The IMUNES project
also consists of userspace and kernel components.
## Open Source Project and Resources
CORE has been released by Boeing to the open source community under the BSD
license. If you find CORE useful for your work, please contribute back to the
project. Contributions can be as simple as reporting a bug, dropping a line of
encouragement or technical suggestions to the mailing lists, or can also
include submitting patches or maintaining aspects of the tool.
encouragement, or can also include submitting patches or maintaining aspects
of the tool.