This project demonstrates dynamic routing in a Mininet-based software-defined network (SDN) environment. It also simulates a DoS attack using hping3 and adapts the routing to mitigate the attack's impact by dynamically switching paths. When the attack stops, the network restores all paths.
Table of Contents
Features
Prerequisites
Installation
Usage
Architecture
Project Structure
Acknowledgement
## Getting started
Features
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Implements dynamic path switching between three predefined routes.
Detects DoS attacks based on signals from an attacker script.
Switches to unaffected paths during an attack.
Restores all paths when the attack stops.
Uses hping3 for realistic DoS simulation.
Real-time logging for path switching and attack status.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
Prerequisites
## Add your files
Python 3.x
Mininet (pre-installed in the Mininet VM)
hping3 (for DoS attack simulation)
pip for Python package installation (optional)
-[ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-[ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-[ ] [Set up project integrations](https://git.ece.iastate.edu/tanibose/cybsc-5300-project-sayontani-saqib/-/settings/integrations)
Download the repository as a zip format and unzip it in your local machine. Ensure below requirements are installed first then download all the files into mininet folder after installing mininet.
## Collaborate with your team
Ensure Mininet is Installed: Mininet comes pre-installed on its official virtual machine (VM). If you're using a custom setup, follow the Mininet Installation Guide.
-[ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-[ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-[ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
Use the built-in continuous integration in GitLab.
Ensure Python Dependencies: No external dependencies are required for this project.
-[ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-[ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-[ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-[ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-[ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
Usage
1. Start the Main Script
***
The main script (run_topology.py) initializes the network topology, enables IP forwarding, and listens for DoS attack signals.
# Editing this README
sudo python3 run_topology.py
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
You should see:
## Suggestions for a good README
[INFO] Listening for DoS signals on 127.0.0.1:65432...
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
2. Simulate a DoS Attack
## Name
Choose a self-explaining name for your project.
Run the attacker script (attacker.py) to simulate a DoS attack using hping3.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
sudo python3 attacker.py
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
Start Attack: The attacker script sends a 1 signal to the main script and starts flooding the target with ICMP packets using hping3.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
Example logs from the main script:
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
[ALERT] DOS Attack detected! Switching to remaining paths: [...]
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
Stop Attack: Press CTRL+C in the attacker script to send a 0 signal, indicating the attack has stopped.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
Example logs from the main script:
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
[ALERT] Attack stopped. Restoring all paths.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
Architecture
Topology
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
The network consists of:
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
2 hosts (host1, host2)
5 routers (r1, r2, r3, r4, r5)
3 dynamic paths:
host1 -> r1 -> r2 -> r5 -> host2
host1 -> r1 -> r3 -> r5 -> host2
host1 -> r1 -> r4 -> r5 -> host2
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
DoS Attack Detection
## License
For open source projects, say how it is licensed.
Start Attack: Attacker script sends a 1 signal.
Stop Attack: Attacker script sends a 0 signal.
Response:
When an attack is detected, the main script avoids the affected path and switches to the remaining two.
Once the attack stops, all three paths are restored.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
Project Structure
cybsc-5300 project-sayontani-saqib/
│
├── run_topology.py # Main script for dynamic routing and DoS handling
├── attacker.py # Script for simulating DoS attacks using hping3
├── README.md # Project documentation
How It Works
Dynamic Routing:
The run_topology.py script continuously random switches between three paths at 0.1 seconds intervals.
When a signal from the attacker script indicates an attack, the script excludes the attacked path and switches between the remaining paths.
DoS Attack Simulation:
The attacker.py script uses hping3 to simulate an ICMP flood attack.
The script communicates with the main script via a TCP socket, sending signals (1 for attack, 0 to stop).
Acknowledgments
Mininet - Virtual Network Emulator
hping3 - Packet Generator for DoS Simulation
Open-source contributors for making this project possible!
