Metadata-Version: 2.1
Name: rettij
Version: 1.2.0
Summary: rettij is an easy-to-use, scalable and co-simulation-capable ICT network simulator based on Kubernetes. It is designed for use with [Mosaik](https://mosaik.offis.de/) but can also be used standalone as a plain ICT network simulator.
Home-page: https://frihsb.gitlab.io/rettij/
Author: Forschungsgruppe Rechnernetze und Informationssicherheit
Author-email: fri@hs-bremen.de
License: MIT
Project-URL: Source Code, https://gitlab.com/frihsb/rettij
Project-URL: Documentation, https://frihsb.gitlab.io/rettij
Project-URL: Changelog, https://gitlab.com/frihsb/rettij/-/releases
Project-URL: Issue Tracker, https://gitlab.com/frihsb/rettij/-/issues
Platform: UNKNOWN
Classifier: Programming Language :: Python :: 3.8
Classifier: Development Status :: 5 - Production/Stable
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: POSIX :: Linux
Classifier: Operating System :: MacOS :: MacOS X
Classifier: Environment :: Console
Classifier: Intended Audience :: Science/Research
Classifier: Intended Audience :: Information Technology
Classifier: Intended Audience :: Education
Requires-Python: >=3.8
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: kubernetes (~=17.17.0)
Requires-Dist: PyYAML (~=5.4.1)
Requires-Dist: requests (~=2.25.1)
Requires-Dist: jsonschema (~=3.2.0)
Requires-Dist: jsonref (~=0.2)
Requires-Dist: urllib3 (~=1.26.1)
Requires-Dist: influxdb (~=5.3.1)
Requires-Dist: mosaik-api (~=3.0.0)

rettij Network Simulator
======

**Content**

<!-- TOC START min:1 max:2 link:true asterisk:false update:true -->
- [What is rettij?](#what-is-rettij)
  - [Use cases](#use-cases)
  - [Features](#features)
- [Tutorial](#tutorial)
  - [Getting Started](#getting-started)
  - [Working with rettij](#working-with-rettij)
  - [Troubleshooting](#troubleshooting)
- [Contributing to rettij](#contributing-to-rettij)
<!-- TOC END -->

## What is rettij?

The network simulator rettij is developed by the *[Forschungsgruppe Rechnernetze und Informationssicherheit](https://www.fri.hs-bremen.de/)* at the [Bremen University of Applied Sciences](https://hs-bremen.de/en).
After testing and evaluating various frameworks, we came to the conclusion that the existing network simulators do a great job at what they aim to do, but we never felt like they were the right tool for our purposes.
Therefore, we finally decided to implement our own network simulation framework.

### Use cases

#### Standalone (manual usage)
* Prototyping and pen-testing Docker images
* Learning environment

#### Embedded (usage inside other applications)
* Scripted controls
* Co-simulation

### Features

#### Native co-simulation capabilities
* Can be used in event-based co-simulation environment
* APIs are based on co-simulation requirements

#### Realistic network behavior
* Uses the actual unix network stack, allowing simulation of realistic cyber-attack scenarios
* Isolates simulation traffic via VXLAN tunneling, meaning no noise from Docker, Kubernetes in packet captures

#### Use real and proprietary software
* Usage of containers and VMs allows running real-world applications, including proprietary software you could replicate fully and legally
* Can be used to verify real-world behavior

#### No in-depth programming knowledge needed
* Easy-to-understand-and-write description language for network topologies
* Standalone mode requiring no further programmatic interaction
* Self-explanatory APIs for easy integration (i.e. for co-simulation scenarios) as well as full code documentation [here](https://frihsb.gitlab.io/rettij).

#### Scalability
* Efficient emulation due to the use of Docker containers (as opposed to VMs)
* Can be used in a Kubernetes cluster to have access to a large pool of computing resources

## Tutorial

The tutorial consists of multiple chapters introducing you to the rettij usage and development step-by-step.
Even if you want to develop for rettij, you should always start with the first chapter as it covers some basics like the setup process.

### Getting Started
Here you will learn how to set up a simple simulation environment with a basic initial configuration.

[-> GO TO "Getting Started"](https://gitlab.com/frihsb/rettij/-/blob/master/docs/getting-started.md)

### Working with rettij
You need to understand the basics of rettij to build your own network-topologies, create custom components and define simulation sequences.

[-> GO TO "Working with rettij"](https://gitlab.com/frihsb/rettij/-/blob/master/docs/working-with-rettij.md)

### Troubleshooting
Some suggestions for fixing commonly encountered roadblocks when working with rettij, Python as well as Kubernetes.

[-> GO TO "Troubleshooting"](https://gitlab.com/frihsb/rettij/-/blob/master/docs/troubleshooting.md)

## Contributing to rettij

Please refer to the [CONTRIBUTING](https://gitlab.com/frihsb/rettij/-/blob/master/CONTRIBUTING.md) file for information on how to contribute to rettij.

## Contributors

Initial development was done by primarily the following members of the *[Forschungsgruppe Rechnernetze und Informationssicherheit](https://fri.hs-bremen.de)* at the [Bremen University of Applied Sciences](https://www.hs-bremen.de):
* Fabian Niehaus
* Torben Woltjen
* Giacomo Gritzan
* Philipp Kathmann
* Bastian Fraune


